davidbirchall/squad-skills-workflows
End-to-end recipe skills that sequence the other plugins for common jobs: ship a web feature, add a chat capability, build a game feature, and cut a game build.
Recipe for adding a capability to a conversational AI application, such as a new connector, a project feature, or a new model behaviour - user-visible behaviour, data model change, context assembly impact, backend orchestration and streaming events, frontend rendering and stream handling, evaluation set and regression tests, cost and latency budget, security, and observability. Names the skills to apply at each step, the exit check, and the handoff. Load when extending chat features end to end or planning a change to how the assistant behaves.
Recipe for taking a Unity game feature from concept to playable - the design question, mechanic and system design, balance placeholders, architecture fit, a vertical slice, input, camera and UI hooks, save impact, tests, profiling, playtest and iteration, and asset integration. Names the skills to apply at each step, the exit check, and what to hand forward. Load when asked to build, prototype, or add a gameplay feature in Unity and see it playable.
Recipe for producing a Unity release candidate and shipping it - scope freeze, content and asset audit, build configuration and automation, test pass, profiling on target hardware, save compatibility check, release checklist, versioning and changelog, provider-neutral store or distribution upload, post-release monitoring with a hotfix path, and retrospective. Names the skills to apply at each step, the exit check, and what to hand forward. Load when preparing a Unity build for testers, a demo, or a public release.
Recipe for fixing a defect without guessing - reproduce first with a failing test or minimal repro, isolate the failing area, find the root cause rather than the symptom, make the smallest fix, add a regression test, check related call sites, verify end to end, and record the cause in the commit message or notes. Names the skills to apply at each step, the exit check, and what to hand forward. Load when asked to fix a bug, investigate unexpected behaviour, or resolve a failing test or error report.
Recipe for restructuring code without changing behaviour - establish a behavioural safety net first, write characterisation tests where coverage is thin, work in small reversible steps, keep one kind of change per commit, keep tests green at every step, never mix behaviour changes into a refactor, measure when performance is the motive, apply stop criteria, and know how to roll back. Names the skills to apply at each step, the exit check, and what to hand forward. Load when asked to refactor, restructure, rename, extract, simplify, or clean up existing code.
Recipe for taking a web feature from idea to production on a Nuxt 3 frontend and NestJS backend - discovery and scope, technical design, contract-first API, schema and migration, backend implementation and tests, frontend implementation with states, accessibility and tests, security and performance check, CI and flagged deployment, observation, and retrospective. Names the skills to apply at each step, the exit check, and what to hand forward. Load when asked to build, ship, or deliver a full-stack feature end to end.
Recipe for starting a project from an empty directory - clarify the goal and constraints with minimal questions, choose the stack from sensible defaults, scaffold, set up lint, format, type-check, and tests, add a CI baseline, handle environment variables and secrets safely, write a repo notes file for future sessions, build a first vertical slice, define done, and deliberately defer everything else. Names the skills to apply at each step, the exit check, and what to hand forward. Load when asked to create, scaffold, bootstrap, or start a new application, service, library, or tool.
Recipe for getting oriented in an unfamiliar repository fast - read the README, manifests, and entry points, map the structure, find conventions, trace one request or feature end to end, run the build and tests to learn how things really work, record findings in a notes file for future sessions, identify risks and unknowns, use sub-agents for parallel exploration when it pays off, and stop once the intended change can be made with confidence. Names the skills to apply at each step, the exit check, and what to hand forward. Load when asked to explore, onboard to, audit, or explain a codebase, or before changing code you have not seen.
Recipe for upgrading packages safely - inventory outdated and vulnerable dependencies, read changelogs, upgrade one at a time or grouped by ecosystem, keep the pnpm lockfile disciplined, work through a breaking-change checklist, run build, tests, and type-check, smoke test the runtime, triage security advisories, pin and plan rollback, plan major-version migrations, and record decisions. Names the skills to apply at each step, the exit check, and what to hand forward. Load when asked to update, bump, or upgrade dependencies, resolve audit findings, or migrate to a new major version.