flow-skills

# flow-skills

> 37 portable, agent-agnostic Agent Skills for software work: plan, build, test, review, verify, orchestrate and ship.
> Install with `npx skills add emiliodominguez/flow-skills`. Each skill is a SKILL.md folder under skills/.

## Skills

- [flow-a11y](skills/flow-a11y/SKILL.md): Accessibility audit and fixes to WCAG 2.2 AA. Use when checking keyboard, screen reader, contrast, zoom or reduced-motion compliance, or before releasing UI. Hands off to `flow-ui` or `flow-styles`, then `flow-review`.
- [flow-adversarial-review](skills/flow-adversarial-review/SKILL.md): Security and abuse review that traces attacker input to reachable impact. Use when a change touches auth, untrusted input, secrets, permissions or isolation, or a security review is requested. Hands off to `flow-work` or `flow-review`.
- [flow-animate](skills/flow-animate/SKILL.md): Interface motion design, tuning and critique. Use when adding transitions or micro-interactions, or when motion feels janky, slow or distracting. Hands off to `flow-styles` or `flow-review`.
- [flow-api](skills/flow-api/SKILL.md): API and interface contract design for HTTP, RPC, events, SDKs or module boundaries. Use when adding or changing an endpoint, schema, error model or public interface. Hands off to `flow-plan` or `flow-work`.
- [flow-benchmark](skills/flow-benchmark/SKILL.md): Performance measurement with a reproducible baseline and stated uncertainty. Use before optimizing, or to compare alternatives on speed, memory or size. Feeds `flow-work` or `flow-refactor` with evidence.
- [flow-brainstorm](skills/flow-brainstorm/SKILL.md): Collaborative idea exploration that ends in a design sketch. Use when the outcome or approach is still open, requirements are vague, or options need comparing. Hands off to `flow-prototype` or `flow-plan`.
- [flow-commit](skills/flow-commit/SKILL.md): Conventional commit messages and atomic commits. Use when asked only for a commit message or a commit; message-only requests never touch Git. Hands off to `flow-ship` when a push or review request was asked for.
- [flow-data-migrate](skills/flow-data-migrate/SKILL.md): Database schema and data migrations. Use when changing stored data, adding constraints or running a live backfill. Hands off to `flow-review` or `flow-orchestrate`.
- [flow-deps](skills/flow-deps/SKILL.md): Dependency updates with verified installs. Use for version bumps, security advisories, outdated packages, automated update requests or a framework version upgrade. Hands off to `flow-review` or `flow-migrate`.
- [flow-design](skills/flow-design/SKILL.md): Visual direction and design system: tokens plus a DESIGN.md. Use before building a new product, page or rebrand, or when a new surface has no design system yet. Hands off to `flow-ui` or `flow-prototype`.
- [flow-diagnose](skills/flow-diagnose/SKILL.md): Root-cause investigation for hard failures. Use when a bug, regression or crash in the product has no obvious cause, or a first fix did not hold. Hands off to `flow-work` or `flow-triage`.
- [flow-docs](skills/flow-docs/SKILL.md): Human-facing documentation grounded in current code. Use when writing or updating a README, contributing guide, usage docs, API reference or architecture docs. Feeds `flow-review` or `flow-ship`.
- [flow-git-fix](skills/flow-git-fix/SKILL.md): Git repair that preserves unrelated work. Use for merge or rebase conflicts, interrupted operations, broken stacks, lost commits or authorized branch cleanup. Hands back to `flow-work` or `flow-ship`.
- [flow-handoff](skills/flow-handoff/SKILL.md): Resumable handoff record for another session. Use when pausing or ending a session mid-task, or saving an interrupted plan or run. Routes to `flow-orchestrate`, `flow-work` or the named specialist.
- [flow-migrate](skills/flow-migrate/SKILL.md): Repository-wide code transformation with a full site inventory. Use for codemods, replacing a deprecated API, or renames touching many files. Hands off to `flow-review` or `flow-orchestrate`.
- [flow-observe](skills/flow-observe/SKILL.md): Observability for a service or feature: structured logs, metrics, traces and alerts tied to user impact. Use when adding telemetry or alerts, before a launch, or after an incident lacked signal. Feeds `flow-triage` and `flow-diagnose`.
- [flow-onboard](skills/flow-onboard/SKILL.md): First tour of an unfamiliar repository. Use when asked to explain how a codebase is organized, how a request flows through it, or where to start in a new repo. Hands off to `flow-plan`, `flow-diagnose` or `flow-repo-brief`.
- [flow-orchestrate](skills/flow-orchestrate/SKILL.md): Multi-worker execution of a plan with independent acceptance gates. Use for cross-system features or long refactors with dependent phases. Routes to `flow-plan`, `flow-verify`, `flow-review` or `flow-handoff`.
- [flow-plan](skills/flow-plan/SKILL.md): Source-grounded implementation plan with acceptance criteria. Use to sequence multi-change or multi-session work, or before a risky change; small edits go to `flow-work`. Hands off to `flow-work` or `flow-orchestrate`.
- [flow-pr-fix](skills/flow-pr-fix/SKILL.md): Review feedback and failing checks on a pull or merge request. Use when a PR or MR has review comments or red CI; push, replies and thread resolution stay within what the user authorized. Hands back to `flow-review` or `flow-ship`.
- [flow-prototype](skills/flow-prototype/SKILL.md): Throwaway experiment that answers one technical or UX question. Use for spikes, proofs of concept or comparing visual alternatives before production work. Hands off to `flow-brainstorm` or `flow-plan`.
- [flow-prune-agent-setup](skills/flow-prune-agent-setup/SKILL.md): Audit and tidy a coding agent's configuration: instructions, memory, settings, hooks, MCP servers and plugins. Use when that setup has grown noisy, conflicting or stale. Feeds `flow-handoff`.
- [flow-redesign](skills/flow-redesign/SKILL.md): Measured upgrade of an existing interface. Use to modernize or polish shipped UI that looks dated or inconsistent without breaking URLs, content or behavior. Hands off to `flow-design`, `flow-ui` or `flow-a11y`.
- [flow-refactor](skills/flow-refactor/SKILL.md): Behavior-preserving structural change. Use to untangle dependencies, redraw module boundaries, extract responsibilities or reduce coupling; behavior changes belong in `flow-work`. Hands off to `flow-review` or `flow-migrate`.
- [flow-release](skills/flow-release/SKILL.md): Versioned software releases and publication recovery. Use when preparing a version, publishing artifacts or resuming a partial release. Hands off to `flow-ship` or `flow-triage`.
- [flow-repo-brief](skills/flow-repo-brief/SKILL.md): Maintained, source-cited brief for a subsystem that agents reuse across sessions. Use when agents keep rediscovering conventions and commands, or agent notes on a subsystem need refreshing against source. Feeds `flow-plan` and `flow-specialize`.
- [flow-review](skills/flow-review/SKILL.md): Code review with evidence-backed correctness and maintainability findings. Use before shipping, on a PR, MR or diff, or when asked to review; gates belong in `flow-verify`. Routes to `flow-work`, `flow-adversarial-review` or `flow-ship`.
- [flow-ship](skills/flow-ship/SKILL.md): Delivery through the requested Git or review stage: commit, push, pull or merge request, ready or merge. Use when asked to push, commit and push, open or update a PR or MR, or merge. Routes to `flow-commit`, `flow-pr-fix`, `flow-git-fix` or `flow-release`.
- [flow-simplify](skills/flow-simplify/SKILL.md): Targeted cleanup of provably dead code and accidental complexity. Use for dead paths, needless indirection or generated slop, not redesign. Hands off to `flow-review` or `flow-refactor`.
- [flow-specialize](skills/flow-specialize/SKILL.md): Repository-specific worker and verifier briefs. Use when delegating tasks to agents that need local architecture, lint rules or domain contracts. Feeds `flow-orchestrate` or `flow-work`.
- [flow-styles](skills/flow-styles/SKILL.md): CSS within the repo's styling architecture, verified in the browser. Use for layout, responsive, cascade or theming bugs in existing components. Hands off to `flow-animate` or `flow-review`.
- [flow-test](skills/flow-test/SKILL.md): Behavior-focused tests. Use when adding coverage, writing a regression test first, or fixing flaky tests that fail randomly or intermittently. Hands off to `flow-work` for implementation or `flow-verify` for an acceptance gate.
- [flow-triage](skills/flow-triage/SKILL.md): Incident and bug-report triage: severity, blast radius, containment and routing. Use for production incidents, firing alerts or unclear reports. Routes to `flow-diagnose`, `flow-work` or `flow-plan`.
- [flow-ui](skills/flow-ui/SKILL.md): Production UI built in a render, compare and fix loop. Use for new pages, screens or components, or to match a mockup or screenshot. Hands off to `flow-a11y` or `flow-review`.
- [flow-verify](skills/flow-verify/SKILL.md): Independent ACCEPT, REJECT or BLOCKED verdict against explicit acceptance criteria. Use as a phase gate or to check that claimed work is actually done. Hands back to `flow-orchestrate`.
- [flow-work](skills/flow-work/SKILL.md): Implementation of a bounded change in verified slices. Use for most coding requests: features, changes, bug fixes or a plan task; multi-worker gated runs go to `flow-orchestrate`. Hands off to `flow-review`, or `flow-verify` via the coordinator.
- [flow-write-skill](skills/flow-write-skill/SKILL.md): Write or fix an agent skill. Use when an agent ignores, misapplies or fails to load a skill, or to create a SKILL.md with a trigger description, lean body and evals. Hands off to `flow-review`.

## Docs

- [Workflow](docs/OVERVIEW.md): choosing a flow, contracts and evidence
- [Orchestration](docs/ORCHESTRATION.md): a gated, resumable multi-step run
- [Skill graph](docs/SKILL-MAP.md): which skill hands off to which
- [Authoring](docs/AUTHORING.md): how skills in this suite are written