setup-rules

Assemble, never author. Conventions live verbatim in assets/conventions/; concatenate selected files byte-for-byte in the fixed order. Merge sensitive-file restrictions into native Agent configuration without replacing unrelated settings.

Modes: setup-rules → Workflow; setup-rules update → Update.

Workflow requires an interactive interview: ask, wait, clarify, and confirm the final manifest before writing. Never infer optional selections from project evidence or defaults. Ask at most four focused questions per round; leave ambiguous items pending.

Category	Source	Target	Condition
Conventions	`assets/conventions/*.md`	`CLAUDE.local.md`	core required; others independently selectable
Subagents	`assets/adapters/<tool>/agents/`	`.<tool>/agents/`	per tool/workflow
Cursor adapter	`assets/adapters/cursor/rules/`, `assets/adapters/cursor/hooks/`, `assets/adapters/cursor/hooks.json`	`.cursor/rules/`, `.cursor/hooks/`, `.cursor/hooks.json`	independently selectable
Antigravity adapter	`assets/adapters/antigravity/gemini.md`	`GEMINI.md`	independently selectable
skillsw	`assets/skillsw`	`skillsw` (project root, executable)	independently selectable
Sensitive-file restrictions	`references/sensitive-file-access.md`	native Agent configuration	default set plus optional extras

Convention order is fixed: core → design → vibecoding → ponytail → karpathy → devops → gsd → matt → superpowers. Skip unselected files.