holocron/CLAUDE.md

Warning

This is the repo meta-config. It tells Claude how to work inside this repository itself — structure, conventions, how to add skills/workflows/providers.

It is NOT the global config deployed to ~/.claude/. That file lives at providers/claude-code/CLAUDE.md. Do not conflate the two.

Working in this repo

This repo is the global AI development configuration repository — the authoritative source for agent definitions, skills, workflows, and prompts across all projects.

Structure

• core/ — provider-agnostic source of truth (plain language, no tool-specific references)
• .agents/skills/ — canonical skills location (Agent Skills standard); populated in Chunk 3
• providers/claude-code/ — Claude Code adapter (deployed to ~/.claude/ via install.sh)
• docs/ — project documentation, PRDs, and issues
• scripts/ — install.sh (sync.sh and init-project.sh come in Chunk 6)
• tests/ — test scripts

Key documents

Read these at the start of every session in this repo:

• CONTEXT.md — domain language and principles; challenge any term that conflicts with it
• docs/VISION.md — purpose, goals, roadmap, and long-term Management Application vision

Key rules

• core/ content must use plain imperative language — no tool names, provider APIs, or format assumptions
• Never edit files deployed by sync.sh directly in a project; put customizations in override files
• providers/claude-code/CLAUDE.md is the deployed global config — edit it there, not here

Chunk development workflow

Each chunk follows this sequence:

1. /grill-with-docs — grill vision/context before writing anything
2. /to-prd — write the PRD from the grilling output
3. /to-issues — break PRD into issues (docs/issues/ until Gitea is set up)
4. /tdd — implement each issue using TDD
5. /improve-codebase-architecture — architecture review after implementation
6. Start a new session before the next chunk

Don't skip /tdd — it's the easy one to forget.

Working context

This repo is built by a junior developer as a homelab tool intended to scale to professional environments. Challenge ideas and reference industry standards rather than validate assumptions. Explain the why behind decisions — assume the user is learning, not just executing. Flag significant actions before taking them.