RecordsOverview

Records

Records document decisions, feature designs, and rejected ideas - capturing the “why” behind this project.

They start as planning docs and become permanent documentation that survives any context clear.

Records are maintained in the source repository. Links below open on GitHub.

#TitleStatus
000Core WorkflowDone
001Modular ArchitectureDone
002Custom Modules DirectoryDone
003Solo vs Team ModeDone
004Document & Clear WorkflowDone
005E2E TestsDone
006Shell ArchitectureDone
007Coding Standards as SkillsDone
008Content VersioningDone
009ccstatusline IntegrationDone
010Skill Auto-LoadingDone
011Upgrade CommandDone
012Optional HooksRejected
013Skill CreatorDone
014Linux SupportDone
015Install Script RefactoringDone
016Preserve User InstructionsDone
017Rename /clear-session to /wrapupDone
018/todo CommandDone
019Upgrade PermissionsRejected
020Custom Modules VersioningDone
021YouTube Transcript SkillDone
022Docker Matrix TestsPlanned
023Context Quality ImprovementsDone
024Documentation SiteDone
025Private NotesDone
026External PluginsDone

Key Decisions

Workflow

  • No /compact - Auto-compact is unpredictable. Use /wrapup + /clear instead.
  • Two CLAUDE.md files - Global for workflow, project for status.
  • Records for decisions - Permanent docs survive any context clear.

Architecture

  • Monorepo for docs - Code and docs in sync, one PR for both.
  • Skills over prompts - Auto-loading based on tech stack, not manual inclusion.
  • Custom overrides built-in - Team standards take precedence.

Implementation

  • Single install script - No npm/pip install required, just curl and run.
  • ShellCheck compliant - All scripts pass linting.
  • Interactive by default - Users choose what to install.