No description
|
|
||
|---|---|---|
| agents | ||
| claude | ||
| configs | ||
| run | ||
| scripts | ||
| .gitignore | ||
| README.md | ||
Lilith Platform Tooling
Development tooling and Claude Code configuration for the Lilith Platform workspace.
bitch CLI
Global development CLI for managing packages across workspaces.
# Install
npm install -g @lilith/bitch --registry=http://forge.nasty.sh/api/packages/lilith/npm/
# Commands
bitch status # Git status of all repos
bitch publish --status # Check registry versions
bitch publish # Publish packages
bitch bump patch # Bump versions
bitch consumers @pkg # Find package consumers
bitch ci # CI status
bitch init my-pkg --type react # Scaffold new package
bitch commits start 5m -R # Auto-commit daemon
See docs/technical/BITCH_CLI.md for full documentation.
Claude Code Configuration
Centralized, version-controlled Claude configuration including:
CLAUDE.md- Main instruction file (symlinked to workspace root)agents/- Project-specific AI agentsinstructions/- Detailed instruction files
Usage
This directory is symlinked from the workspace root:
lilith-platform/CLAUDE.md → tooling/CLAUDE.md
lilith-platform/.claude/agents → tooling/agents
lilith-platform/.claude/instructions → tooling/instructions
Structure
tooling/
├── README.md # This file
├── CLAUDE.md # Main Claude instructions
├── agents/ # Project-specific agents
│ └── README.md # Agent documentation
└── instructions/ # Detailed instruction files
└── README.md # Instructions documentation
Why Separate Repo?
- Version controlled - Changes tracked in git
- Shareable - Can be reused across workspaces
- Single source - One CLAUDE.md for entire workspace
- Clean separation - Tooling separate from code
Adding Content
New Agent
- Create
agents/agent-name.md - Add to agents table in
CLAUDE.md
New Instruction
- Create
instructions/topic-name.md - Add to instructions table in
CLAUDE.md - Define trigger conditions