Files
holocron/AGENTS.md
Defame1297 53cf86c243 chore(agents): remove stale structure entries and chunk references
## Why
Structure section listed .claude-plugin/, docs/, scripts/, tests/ —
all either obvious or carrying stale annotations (Chunk 6, sync.sh).
HUMANS.md path updated to docs/wiki/ after the wiki move. sync.sh
key rule removed since the script doesn't exist yet.

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-28 17:51:33 +00:00

2.4 KiB

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

  • plugins/ — installable plugin units; each is self-contained (skills, agents, hooks, MCP servers, bundled assets); install separately via claude plugin install <name>@holocron
  • providers/claude-code/ — Claude Code adapter (deployed to ~/.claude/ via install.sh)

Key documents

Read CONTEXT.md at the start of every session in this repo.

Read these on demand:

  • docs/VISION.md — purpose, goals, and long-term Management Application vision
  • docs/spec/overview.md — current deployed state; what works today
  • docs/spec/architecture.md — current directory structure, install pipeline, provider model
  • docs/ROADMAP.md — chunk status table and open questions; read this to orient on where work stands
  • docs/adr/ — architectural decisions; read before answering design questions or proposing structural changes
  • docs/ai-constitution.md — full governance evidence base; read when a governance decision needs justification
  • docs/research/ai-coding-factory/ai-coding-factory-principles.md — factory design rationale; read when implementing, auditing, or reviewing skills or factory structure
  • docs/notes/factory-integration-decisions.md — decisions from the factory integration grill; read when making skill authoring or factory design decisions
  • docs/wiki/HUMANS.md — human practitioner checklist; applies when working with AI tools in this repo
  • Governance rules are always in effect — core/instructions/governance.md (agent rules); docs/research/governance_principles/CONTROLS.md

Key rules

  • providers/claude-code/CLAUDE.md is the deployed global config — edit it there, not here
  • Governance constraints from core/instructions/governance.md apply when building content in this repo — hard prohibitions on secrets and data, HITL requirements before irreversible actions, sycophancy resistance, and deterministic execution preference are always in effect

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.