No description
AGENT_PLAN.md outlines: - Phase 1: platform-architect, stream-workflow, infrastructure - Phase 2: testing-specialist, frontend-specialist - Phase 3: payment, content-moderation, legal specialists - Optional: character agents (venus-lilith, venus-quinn) Recommendation: Start with platform-architect + infrastructure for service-registry deployment. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| agents | ||
| instructions | ||
| CLAUDE.md | ||
| README.md | ||
Lilith Platform Tooling
Claude Code configuration for the Lilith Platform workspace.
Purpose
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