* chore(repo): remove one-shot reports and stale docs approved by owner * chore(repo): untrack _references and superpowers planning artifacts * fix(repo): repair .gitignore anchors and un-ignore published CLI entrypoint * feat(ci): extend check:tracked-artifacts never-allowed classes * docs(agents): add Hard Rule 23 (_tasks append-only) and sync scripts/ layout * feat(ci): generic never-track rule for every root underscore path (_*) --------- Co-authored-by: backryun <bakryun0718@proton.me>
3.3 KiB
CLAUDE.md
@AGENTS.md
All project rules live in AGENTS.md — the single source of truth for every AI
assistant (architecture, conventions, testing, quality gates, git workflow, the 23 Hard Rules,
PII learnings). Read it in full; do not re-add project rules here. Everything below applies ONLY
to Claude Code — operational refinements of rules already defined in AGENTS.md.
Worktree isolation — Claude Code specifics
The full mandatory worktree protocol (base-branch confirmation, .claude/worktrees/ canonical
path, cp -al node_modules, teardown rules) is in AGENTS.md → Git Workflow → "Worktree
isolation". Claude-Code-specific points:
- Confirm the base branch with the operator via
AskUserQuestion(Hard Rule #19) unless they already told you. - Prefer the native
EnterWorktreetool — it already creates worktrees under.claude/worktrees/(the canonical path). Create the worktree with the documentedgit worktree addcommand, then callEnterWorktreewith itspath.
Cross-session safety — Claude Code specifics
Hard Rules #19/#21/#22 (in AGENTS.md) govern parallel sessions. Operational reminders for this
harness:
- Replicate the
git stashban verbatim in the prompt of every subagent that touches git (Agent tool / Workflow scripts) — subagents do not inherit this file, and the recorded recurrence of the stash incident came through a subagent. - Before merging or pushing to any PR you did not create this session, run
git worktree listand re-checkgh pr view <N> --json state,headRefOid(Hard Rule #22b). - End every session with the main checkout on the branch it started on.
Superpowers / planning artifacts — path overrides
The _tasks/ convention is defined in AGENTS.md → "Planning & Research Artifacts". The
superpowers skills ship with defaults that point at docs/… — those defaults are overridden
here. When a superpowers skill announces a path like "saved to docs/superpowers/plans/…",
rewrite it to the _tasks/… equivalent before writing:
| Artifact (skill) | Default (do NOT use) | Save here instead |
|---|---|---|
Plans (writing-plans) |
docs/superpowers/plans/ |
_tasks/superpowers/plans/YYYY-MM-DD-<feature>.md |
Specs / design (brainstorming) |
docs/superpowers/specs/ |
_tasks/superpowers/specs/YYYY-MM-DD-<topic>-design.md |
Research (deep-research, ad-hoc) |
docs/research/ |
_tasks/research/… |
Hand-offs (/handoff) |
— | _tasks/hands-off/<YYYY-MM-DD>_<branch>_v<versão>_sess-<id>/ |
Commit those artifacts inside the _tasks/ repo (git -C _tasks …), never in the main repo.
Base-green before opening PRs
Before cutting a branch or opening a PR, run the base-green check (AGENTS.md → Git Workflow →
"Base-green check"; project skills reference it as .agents/skills/_shared/base-green.md). A PR
opened while the base tip is red must carry ⚠️ base-red inherited: #<issue> in its body. To
drain an accumulated red state (base tip + red PRs), use the /sweep-reds skill.