Setup Project

Setup project

Drives the setup flows in flows user.mmd: workflow setup first, tech stack second.

Setup skills are just-in-time: npx github:timschoch/skilly add <skill>, then READ the installed SKILL.md and follow it directly (the session's skill list only loads at startup — no reload exists), then npx github:timschoch/skilly remove <skill>. This applies to EVERY skill named below — never invoke a copy installed elsewhere on the machine. Setup skills live in NO synced bundle: they would sit unused and pollute the context window.

Workflow setup

Ask which parts apply, then run the chosen skills in this order, finishing one before the next:

1. Husky + lint-staged + Prettier pre-commit? → setup-pre-commit; the repo's own stack → skip (nothing automated for it yet — add a sibling skill when one earns its place).
2. GitHub scaffolding (conventional commits/branches)? → setup-repo — GitHub settings, commit/branch rules wired into the hooks just chosen, CLAUDE.md scaffold.
3. Release automation? → setup-release-please — plus merge settings.
4. Wayfinder? → setup-matt-pocock-skills — issue tracker, triage labels, domain-doc layout.

Remove the used setup skills, commit conventionally, push, and make sure a PR exists.

Tech stack

1. Propose Bundles from the catalog, let the user confirm:
   • every repo: workflow
   • a project-<x> bundle when one exists (it already includes its tech bundles)
   • otherwise the tech-* bundles matching the stack (check package.json / lockfiles)
   • marketing only where the repo produces marketing content
2. npx github:timschoch/skilly add <bundle...> — installs, rules, commit, PR.
3. Stack setup skills where the stack needs them (e.g. trigger-setup): add, follow, remove.
4. npx github:timschoch/skilly update — ends with its own commit.

Validate

After the PR merges: gh workflow run skilly-sync.yml, then gh run watch until green. Local auth tests on this Mac lie (the machine SSH key bypasses $HOME isolation).