Why Trellis?

| Feature | Problem Solved | | --- | --- | | Auto-Injection | Required specs and workflows auto-inject into every conversation. Write once, apply forever | | Auto-updated Spec Library | Best practices live in auto-updated spec files. The more you use it, the better it gets | | Parallel Sessions | Run multiple agents in tandem - each in its own worktree | | Team Sync | Share specs across your team. One person's best practice benefits everyone | | Session Persistence | Work traces persist in your repo. AI remembers project context across sessions |

Quick Start

# 1. Install globally
npm install -g @mindfoldhq/trellis@latest

# 2. Initialize in your project directory
trellis init -u your-name

# 3. Start Claude Code and begin working

your-name becomes your identifier and creates a personal workspace at .trellis/workspace/your-name/

Use Cases

Educating Your AI

Write your specs in Markdown. Trellis injects them into every AI session — no more repeating yourself.

Define your component guidelines, file structure rules, and patterns once. AI automatically applies them when creating new code — using TypeScript with Props interface, following PascalCase naming, building functional components with hooks.

Ship in Parallel

Spawn multiple Claude sessions in isolated worktrees with /trellis:parallel. Work on several features at once, merge when ready.

While coding, each worker runs in its own worktree (physically isolated directory), no blocking, no interference. Review and merge completed features while others are still in progress.

Custom Workflows

Define custom skills & commands that prepare Claude for specific tasks and contexts.

Create commands like /trellis:before-frontend-dev that load component guidelines, check recent changes, pull in test patterns, and review shared hooks—all with a single slash.

How It Works

Project Structure

.trellis/
├── workflow.md              # Workflow guide (auto-injected on start)
├── worktree.yaml            # Multi-agent config (for /trellis:parallel)
├── spec/                    # Spec library
│   ├── frontend/            #   Frontend specs
│   ├── backend/             #   Backend specs
│   └── guides/              #   Decision & analysis frameworks
├── workspace/{name}/        # Personal journal
├── tasks/                   # Task management (progress tracking & more)
└── scripts/                 # Utilities

.claude/
├── settings.json            # Hook configuration
├── agents/                  # Agent definitions
│   ├── dispatch.md          #   Dispatch Agent (pure routing, doesn't read specs)
│   ├── implement.md         #   Implement Agent
│   ├── check.md             #   Check Agent
│   └── research.md          #   Research Agent
├── commands/                # Slash commands
└── hooks/                   # Hook scripts
    ├── session-start.py     #   Inject context on startup
    ├── inject-subagent-context.py  #   Inject specs to subagents
    └── ralph-loop.py               #   Quality control loop

Workflow Diagram

Roadmap

• [ ] Better Code Review — More thorough automated review workflow
• [ ] Skill Packs — Pre-built workflow packs, plug and play
• [ ] Broader Tool Support — Cursor, OpenCode, Codex integration
• [ ] Stronger Session Continuity — Autosave session-wide history
• [ ] Visual Parallel Sessions — Real-time progress for each agent

FAQ

Skills are optional — AI may skip them, leading to inconsistent quality. Trellis enforces specs via Hook injection: not "can use" but "always applied". This turns randomness into determinism, so quality doesn't degrade over time.

Most of the time, AI handles it — just say "We use Zustand, no Redux" and it creates the spec file automatically. But when you have architectural insights AI can't figure out on its own, that's where you step in. Teaching AI your team's hard-won lessons — that's why you won't lose your job to AI.

Those are all-in-one files — AI reads everything every time. Trellis uses layered architecture with context compression: only loads relevant specs for current task. Engineering standards should be elegantly layered, not monolithic.

No. Each person has their own space at .trellis/workspace/{name}/.

Use /trellis:record-session at the end of each conversation. AI writes a session summary to .trellis/workspace/{name}/journal-N.md and indexes it in index.md. Next time you /trellis:start, AI automatically reads recent journals and git info to restore context. In theory, you could just submit your daily journal files as your work report 🤣.

Star History

Community

• Discord — Join the conversation
• GitHub Issues — Report bugs & request features