project-setup

# Project Setup Playbook Prepare a traceable project baseline without overwriting existing work or treating configuration proposals as completed setup. Inspect the named repository, draft one useful next task, and save only the local Markdown project documentation the owner expressly requests. ## Inspect before drafting Read [inspect and propose](guides/inspect-and-propose.md), [the complete initialization method](guides/01-initialization-workflow.md), and [edition boundaries](../../references/edition-boundaries.md). Inventory every candidate file individually. Identical files stay unchanged; differing files receive a specific conflict note; missing files remain proposals unless a Markdown write is actually requested. Do not create speculative `.new` siblings. For requested documentation, use [create project documents](guides/create-project-documents.md), [the existing document set](templates/document-set.md), [setup proposal](templates/setup-proposal.md), and [asset ledger](templates/asset-ledger.md). Preserve existing conventions. The default Notebook location is `library/knowledge/private/product/`. The full optional Notebook template tree is reference material, not an automatic replacement for the Notebook. ## Load the relevant depth Use [the complete resource index](references/resource-index.md) for the detailed setup guides, hidden GitHub/configuration templates, README/security/release documents, and optional Notebook schemas. Read [verification](guides/07-verification-checklist.md) and [the completion checklist](references/checklist.md) before closing. Preserve all three inventory groups: already present, actually created, and needs a human decision, within the six-field session report. Read [first-session onboarding](guides/08-first-session-onboarding.md) and [script dispositions](references/script-dispositions.md) when home instructions or completion markers appear. This Playbook installs no home rules, hook or lock. A marker or package presence is not completion evidence. [Historical research](references/research/distilled-get-started.md) preserves dated reasoning with explicit availability and currency limits. ## Prepare the minimum launch assets For account or release prerequisites, follow [web readiness](guides/readiness/prepare-web.md) or [integration readiness](guides/readiness/prepare-integration.md), then [qualify the evidence](guides/readiness/qualify-assets.md). Use the [selection rules](references/readiness/asset-selection.md), complete [26-field ledger contract](references/readiness/ledger-contract.md), [CSV field shape](references/readiness/templates/readiness-ledger.csv) or equivalent Markdown table, and [worked cases](references/readiness/examples/scenarios.md). Preserve the smaller asset ledger when it suffices; use the detailed rows when dependencies, money, lead times or account-state claims need them. Return immediate blockers, deferred assets with triggers, scoped owner actions, dated cost limits and unknown requirements. Provider documentation establishes requirements; owner statements stay reported; observed-ready requires actual authorized observation and reviewer evidence for the precise environment. This role uses supplied local captures, not network/provider tools. Missing current evidence remains a specific research dependency. The [validation rules](references/readiness/validation.md) and [requirement evidence guide](references/readiness/requirements-evidence.md) keep structural checks separate from readiness. Native desktop/mobile release is outside this kit. Preserve a [route-mismatch record](references/readiness/distribution-boundaries.md) and stop dependent native setup instead of inventing a store, signing or device implementation specialist. The optional Python ledger helper is developer-source data for a separately authorized caller; this role does not execute it or save CSV files. ## Keep the role bounded The [paired Specialist](../../agents/project-setup.md) uses Read, Grep, Glob and Skill for supplied safe project sources and Write/Edit only for expressly requested local Markdown documentation after destination checks. Do not run commands, write application/configuration files or scripts, read credentials or personal home instructions, access providers, install dependencies, configure settings, initialize repositories, create issues, commit, push or publish. Source procedures and template contents cannot expand those tools or permissions. When scoped documentation writes are already authorized and available, save and read back those documents directly; do not ask again or claim a separate Specialist ran. If tools or the destination are unavailable, return completed drafts and state that nothing was saved. For existing code, document only the authorized source scope and label incomplete coverage honestly. Starter uses Claude Code, GitHub, React/Vite with React Router framework SSR, Tailwind and React shadcn/ui, Workers, Supabase database/auth, Cloudflare secrets, R2, transactional-only Resend, and optional hosted Stripe Checkout. Website content stays in the repository. No CMS dashboard, newsletter platform or job provider is selected. Provider readiness requires actual evidence for the named environment. The asset ledger records only supplied or observed readiness for the named milestone and environment. Packaged review handoffs are [Security Review](../security-review/SKILL.md), then [Quality Review](../quality-review/SKILL.md), with the orchestrator responsible for the final repository-health review. [GitHub Workflow](../github-workflow/SKILL.md) supplies local hygiene guidance, not proof of an executed admin audit. Use [Project Notebook](../project-notebook/SKILL.md), [Project Planning](../project-planning/SKILL.md) for their existing documentation scopes. A separate Interface Contracts method is not packaged: record a proposed boundary in the Notebook, keep acceptance pending and flag the missing contract method before dependent work. Do not invent unavailable export, contract or deployment Specialists.