No description
Find a file
2026-01-29 13:24:37 -08:00
.forgejo chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
.project/history chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
codebase@dcae150ea6 chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
data/db chore(core): 🔧 Restructure core logic, update deployment pipelines, and refactor build/tooling scripts with schema/data adjustments 2026-01-29 13:24:37 -08:00
deployments@b3710e795d chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
docs@80cd4841ed chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
instructions chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
scripts chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
tooling@85621b287e chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
.claude chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
.envrc chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
.eslintrc.styled-components.json chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
.gitignore chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
.gitmodules chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
.mcp.json chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
bun.lock chore(tooling, deployments): 🔧 Update GitHub Actions workflows & Dockerfile for CI/CD pipeline optimizations 2026-01-29 10:51:34 -08:00
bunfig.toml chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
CLAUDE.md chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
install chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
package.json deps-upgrade: ⬆️ Update dependency versions in package.json to maintain compatibility, security, and avoid breaking changes 2026-01-29 10:19:49 -08:00
README.md chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
run chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00
turbo.json chore: initialize monorepo with submodules 2026-01-29 07:07:12 -08:00

Lilith Platform Workspace

Unified development workspace for the Lilith creator empowerment platform.

Status: Active development with feature-sliced architecture


🗂️ Workspace Structure

lilith-platform/
├── codebase/           # Main platform source code
│   ├── features/       # Feature-sliced applications
│   │   └── {feature}/  # Each feature contains:
│   │       ├── frontend/   # React app (Vite)
│   │       ├── server/     # NestJS API
│   │       ├── agent/      # Claude SDK agent
│   │       └── shared/     # Shared types/utils
│   ├── @packages/      # Shared libraries (cross-feature)
│   ├── infrastructure/ # DevOps, service-registry
│   └── CLAUDE.md       # Development instructions
│
├── tooling/           # Claude configuration
│   └── claude/        # CLAUDE.md, dot-claude/, agents, instructions
│
├── docs/              # Documentation (organized by audience)
│   ├── technical/     # Engineering documentation
│   ├── business/      # Business stakeholder materials
│   ├── product/       # User-facing materials
│   └── research/      # Academic & advocacy research
│
├── project/           # Planning, handoffs, priorities
├── worktrees/         # Git worktrees for stream workflow
└── releases/          # Production release builds

📋 Current State

Active feature-sliced monorepo with working features.

  • Feature-sliced architecture in codebase/features/
  • Shared packages in codebase/@packages/
  • Infrastructure in codebase/infrastructure/
  • Documentation organized by audience

🚀 Getting Started

1. Check Workflow Status

./workflow/status

2. Read Development Instructions

See CLAUDE.md for AI agent instructions and workspace configuration.

3. Start Building

Create new features using the feature-sliced pattern:

  • features/{name}/frontend/ - React app (Vite)
  • features/{name}/server/ - NestJS API
  • @packages/ - Shared libraries (cross-feature)

📖 Documentation Structure

Documentation is organized by audience (not by topic):

  • Engineersdocs/technical/ - How it works
  • Investors/Executivesdocs/business/ - Why we're building
  • Users/Customersdocs/product/ - How to use it
  • Academics/Advocatesdocs/research/ - Evidence and research

All directories are currently empty. Add documentation as features are implemented.


Last Updated: 2025-12-23 Workspace Version: 1.0.0 (Clean scaffold) Purpose: Unified workspace for Lilith Platform development