Setup Tooling
Orchestrator: encodes my tastes into a project. Drive intent first —
the interview decides which modules apply; never install anything
before it.
1. Drive intent
Ask up front (AskUserQuestion works well); don't guess:
- Ecosystem — JS/TS is the only ecosystem with stack modules today.
For anything else, say so, apply only the ecosystem-agnostic modules
below, and offer to draft a
setup-<lang>-stack module as a follow-up.
- Platform — web, mobile (Expo/React Native), or both. Web →
setup-js-stack; mobile → setup-expo-stack; both → compose the two
(a web+mobile monorepo).
- Project type — for web: full-stack app, SPA, backend/API, library,
CLI; for mobile: an Expo app (± API routes/backend). The stack module
maps type → scaffold.
- Frontend? — decides design tooling and which design tool
(Pencil or Figma). Mobile apps always have one.
- Database? — decides the DB portion of the stack module (on mobile,
the backend-per-project decision).
- On-chain contracts? — a web frontend that reads and writes EVM
contracts through the user's wallet takes
setup-evm-stack as a layer
over the web stack.
- Existing code? — never re-scaffold over existing work; layer the
missing pieces instead.
2. Compose modules
In order, skipping what intent ruled out:
- The stack module for the platform —
setup-js-stack
(web) and/or setup-expo-stack (mobile); both for a
web+mobile monorepo. Framework, package-manager baseline, database, CI.
JS/TS only.
lint-guardrails — every project, any ecosystem.setup-evm-stack — on-chain web projects only; it
adds exemptions to the guardrails config, so it lands on top of one.design-tooling — frontend projects only, with the
design tool from intent.agent-rules — every project.- If
setup-matt-pocock-skills appears in the available-skills list
(any scope, possibly namespaced), invoke it to layer the
agent-workflow conventions (issue tracker, triage labels, domain
docs) on top of the fresh tooling. If not, skip silently — don't
hunt for it.
3. Report
Summarize what landed — scaffold, scripts, rule files, hooks, CI,
design files — and what was skipped and why.
1---2name: setup-tooling3description: Bootstrap a project with my preferred tooling. Drives an intent interview first, then composes the matching modules — a per-platform stack (JS/TS web via setup-js-stack, Expo/React Native mobile via setup-expo-stack), lint-guardrails, setup-evm-stack for on-chain web projects, design-tooling, and agent-rules. Use when the user says "setup tooling" or "bootstrap this project", sets up a mobile/expo app, or starts a fresh repo.4---56# Setup Tooling78Orchestrator: encodes my tastes into a project. **Drive intent first** —9the interview decides which modules apply; never install anything10before it.1112## 1. Drive intent1314Ask up front (AskUserQuestion works well); don't guess:15161. **Ecosystem** — JS/TS is the only ecosystem with stack modules today.17 For anything else, say so, apply only the ecosystem-agnostic modules18 below, and offer to draft a `setup-<lang>-stack` module as a follow-up.192. **Platform** — web, mobile (Expo/React Native), or both. Web →20 `setup-js-stack`; mobile → `setup-expo-stack`; both → compose the two21 (a web+mobile monorepo).223. **Project type** — for web: full-stack app, SPA, backend/API, library,23 CLI; for mobile: an Expo app (± API routes/backend). The stack module24 maps type → scaffold.254. **Frontend?** — decides design tooling and which **design tool**26 (Pencil or Figma). Mobile apps always have one.275. **Database?** — decides the DB portion of the stack module (on mobile,28 the backend-per-project decision).296. **On-chain contracts?** — a web frontend that reads and writes EVM30 contracts through the user's wallet takes `setup-evm-stack` as a layer31 over the web stack.327. **Existing code?** — never re-scaffold over existing work; layer the33 missing pieces instead.3435## 2. Compose modules3637In order, skipping what intent ruled out:38391. The stack module for the platform — `setup-js-stack`40 (web) and/or `setup-expo-stack` (mobile); both for a41 web+mobile monorepo. Framework, package-manager baseline, database, CI.42 JS/TS only.432. `lint-guardrails` — every project, any ecosystem.443. `setup-evm-stack` — on-chain web projects only; it45 adds exemptions to the guardrails config, so it lands on top of one.464. `design-tooling` — frontend projects only, with the47 design tool from intent.485. `agent-rules` — every project.496. If `setup-matt-pocock-skills` appears in the available-skills list50 (any scope, possibly namespaced), invoke it to layer the51 agent-workflow conventions (issue tracker, triage labels, domain52 docs) on top of the fresh tooling. If not, skip silently — don't53 hunt for it.5455## 3. Report5657Summarize what landed — scaffold, scripts, rule files, hooks, CI,58design files — and what was skipped and why.
JCaraballo113