Updated agent instructions and documentation to reflect the new workspace architecture. Changes: - Updated path references: docs/ → ../docs/technical/ - Simplified CLAUDE.md (removed egirl-platform specific content) - Simplified README.md (reduced from detailed to overview) - Updated .claude/instructions/ files with correct paths - Removed egirl-platform specific examples and references Path Updates: - Platform architecture docs now at ../docs/technical/architecture/ - Feature docs now at ../docs/technical/features/ - Business docs now at ../docs/business/ Documentation Reduction: - CLAUDE.md: Focused on development guidelines (was 644 lines, now ~150) - README.md: Focused on workspace overview (was 113 lines, now ~40) - Removed egirl-platform MCP tool examples - Removed egirl-platform specific routing rules This creates a clean slate for lilith-platform documentation while preserving the instruction system structure. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
3 KiB
Development Guidelines for Lilith Platform
Purpose: Development instructions for AI agents working in the Lilith Platform codebase.
Workspace: This is the codebase/ directory within the unified lilith-platform/ workspace.
Extends: ~/.claude/CLAUDE.md (global configuration applies to ALL projects)
🌍 Global Configuration (Inherited)
This project inherits all global instructions from ~/.claude/CLAUDE.md:
- Collective voice protocol (always active)
- Anti-hallucination verification (always active)
- Git safety rules (triggered by git operations)
- Code standards (SOLID, DRY, SRP principles)
- Agent usage patterns
- Command efficiency
- Testing standards
See: ~/.claude/CLAUDE.md for complete global router and ~/.claude/instructions/ for global instruction files.
📍 Current State
Status: Empty scaffold
- ❌ No packages in
@apps/ - ❌ No packages in
@packages/ - ❌ No services in
@services/ - ❌ No workspace configuration (
package.json,pnpm-workspace.yaml)
This is a clean codebase ready for first development.
🚀 Getting Started
Creating First Package
When ready to start development:
-
Create workspace configuration:
# Initialize package.json for monorepo # Create pnpm-workspace.yaml for workspace packages # Add tsconfig.base.json for shared TypeScript config -
Create your first package:
# Example: Shared library mkdir -p @packages/core cd @packages/core npm init -y -
Install dependencies:
pnpm install
📦 Workspace Structure Philosophy
Organization:
- @apps/ - User-facing applications (web, mobile, admin)
- @packages/ - Shared libraries and utilities
- @services/ - Backend services (APIs, workers, processors)
Current State: All directories empty - create packages as needed.
📖 Documentation
Workspace overview: ../README.md
Current codebase state: README.md
Documentation: ../docs/{technical,business,product,research}/ (all empty)
🔧 Development Workflow
When Building Features
- Create necessary packages in appropriate directories
- Add documentation to
../docs/technical/as you build - Update this file with project-specific patterns as they emerge
Git Workflow
- Main branch: Stable code only
- Feature branches: Create for new development
- Worktrees: Use
../worktrees/for parallel development (when needed)
🎯 Platform Philosophy
Core Principles:
- Creator empowerment - sex workers own their platform relationship
- No deplatforming - protection from payment processor censorship
- Transparent economics - fair revenue sharing
- Jurisdiction strategy - Icelandic registration for speech protection
- GDPR-first privacy architecture
Last Updated: 2025-12-23 Status: Empty scaffold - ready for first code Purpose: Development router for Lilith Platform codebase