FlowPilot

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when the user asks to review a pull request or diff with a structured Codex CLI workflow using parallel review passes and filtered actionable findings.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when the user asks to build a new feature and wants a structured Codex CLI workflow with discovery, clarifying questions, architecture comparison, implementation, and review.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements.

Use when executing implementation plans with independent tasks in the current session

Use when starting any conversation to discover relevant skills and open the right SKILL.md files before responding, including before clarifying questions.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when starting any conversation to discover relevant skills and open the right SKILL.md files before responding, including before clarifying questions.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills before deployment in Codex CLI.

Use before implementing a new feature, changing behavior, or making design-heavy decisions in Cursor. Helps clarify intent, explore approaches, and get approval before coding.

Use when the user asks for a code review of local files, a workspace, a branch diff, or a pull request. Focus on real bugs, regressions, accessibility issues, and misleading behavior, with findings ordered by severity.

Use when facing two or more independent tasks in Cursor that can be investigated or executed in parallel without conflicting edits or shared state.

Use when a written implementation plan already exists in Cursor and the next step is to execute it in small batches with checkpoints and verification.

Use when building a new feature or substantial behavior change in Cursor and the user wants a structured workflow from discovery through implementation and review.

Use when implementation work is done and you need to decide how to finish it in Cursor, such as keeping the branch, merging locally, creating a pull request, or cleaning up temporary workspaces.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Use when acting on code review feedback in Cursor, especially if suggestions seem unclear, debatable, or risky. Helps evaluate feedback technically before changing code.

Use after completing meaningful implementation work in Cursor and before merging or declaring the change ready, so the result gets a focused review for bugs, regressions, and maintainability risks.

Use when executing a larger plan in Cursor with parallel or delegated work, while keeping tasks narrowly scoped and reviewed between steps.

Use when a task in Cursor may benefit from a structured workflow and one or more companion skills from this pack, such as brainstorming, feature development, design, review, debugging, planning, or verification.

Use when diagnosing a bug, failing test, build issue, or unexpected behavior in Cursor before proposing a fix. Focus on reproducing the issue, tracing the cause, and validating the repair.

Use when implementing a feature, fixing a bug, or changing behavior in Cursor and you want a disciplined red-green-refactor workflow.

Use when starting feature work that should be isolated from the current checkout, especially in git repositories where a separate worktree would reduce risk.

Use when starting a task in Cursor and deciding whether to apply one of the companion skills in this pack before exploring, planning, editing, or reviewing.

Use before claiming work is complete, fixed, or passing in Cursor. Requires fresh verification evidence such as tests, builds, lint output, or direct reproduction checks.

Use when the user wants a written implementation plan in Cursor before editing code, especially for multi-step tasks or changes touching several files.

Use when creating, editing, or validating Cursor custom skills, especially when deciding where they should live, how they should be named, and how to describe when they apply.