Defame1297
a3bb708bff
Establishes the global AI development config repo from scratch: - Chunk 1: repo skeleton, install.sh, statusline, deploy manifest - Chunk 2: core instructions (coding/git/testing), CLAUDE.md rewrite (always-on + content index two-tier model), docs restructure, 6 ADRs, ROADMAP.md, .gitkeep placeholders - Bootstrap skills in .claude/skills/ (to be catalogued and migrated to .agents/skills/ in Chunk 3) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2.0 KiB
0004 — Rewrite providers/claude-code/CLAUDE.md and retire global.md ✅
What to build
Replace the sparse content in providers/claude-code/CLAUDE.md with a complete always-on section covering communication style and behavior rules, plus a content index that tells the agent when to load each topic instruction file. Delete core/instructions/global.md, which is a placeholder stub with no content — the content index update makes it obsolete.
The always-on communication rules define how the agent responds: answer directly first, challenge bad ideas explicitly rather than validating them, explain the why behind decisions, and never soften disagreement into a suggestion.
The always-on behavior rules define when the agent asks permission: reads and exploration proceed freely; writes, edits, and git operations state intent before acting; irreversible or shared-state operations (push, drop, publish) require explicit confirmation every time.
The content index provides inline load triggers so the agent knows when to read each on-demand instruction file without requiring frontmatter in those files.
Acceptance criteria
providers/claude-code/CLAUDE.mdcontains an always-on communication section with all seven rules from the PRDproviders/claude-code/CLAUDE.mdcontains an always-on behavior section covering reads, writes, and irreversible operations- Content index includes load triggers for: coding conventions, git conventions, testing conventions, and workflows/agents/prompts
core/instructions/global.mdis deleted- In a new session, ask an exploratory design question — agent responds with one recommendation and one tradeoff in 2–3 sentences
- In a new session, propose a clearly overengineered approach — agent names the problem rather than implementing it
- In a new session, ask the agent to edit a file — agent states what it is about to do before proceeding
- In a new session, ask the agent to push a commit — agent requires explicit confirmation
Blocked by
None — can start immediately