setup-projectlisted

# Setup Project Establish the repository's durable operating contract before ordinary implementation begins. Keep the setup idempotent: reuse recorded decisions, ask only for missing or explicitly reopened choices, and update existing files instead of duplicating policy. Own repository policy and its supporting configuration, not product implementation. Do not scaffold application source, features, domain code, UI, fixtures, or a speculative technology stack. If the user also requests product scaffolding, complete and validate setup first, then handle implementation as a separate concern under normal skill-triggering rules. Read [`assets/AGENTS.template.md`](assets/AGENTS.template.md) in full before writing project guidance. Adapt its rules to the project; never leave template placeholders in the target repository. ## Skill routing - Use [`grilling`](../grilling/SKILL.md) to resolve the required one-time project decisions, one decision at a time. Give it the inspected project facts and the unresolved decision set; resume setup only after its completion summary. - Run [`setup-agent-docs`](../setup-agent-docs/SKILL.md) after the root `AGENTS.md` exists. - Use [`research`](../research/SKILL.md) only when a setup decision depends on current external evidence, standards, comparisons, or other primary-source investigation beyond the local repository. - Use [`apple-docs`](../apple-docs/SKILL.md) when Apple platform, Xcode, signing, entitlement, notarization, privacy, or distrib