ReddRadar
Topic: cursor
7,943 skills in this topic.
-
systematic-debugging
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.
6BNBN/FlowPilot 127
-
subagent-driven-development
Use when executing a larger plan in Cursor with parallel or delegated work, while keeping tasks narrowly scoped and reviewed between steps.
6BNBN/FlowPilot 127
-
receiving-code-review
Use when acting on code review feedback in Cursor, especially if suggestions seem unclear, debatable, or risky. Helps evaluate feedback technically before changing code.
6BNBN/FlowPilot 127
-
playwright
6BNBN/FlowPilot 127
-
frontend-design
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.
6BNBN/FlowPilot 127
-
finishing-a-development-branch
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.
6BNBN/FlowPilot 127
-
feature-dev
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.
6BNBN/FlowPilot 127
-
executing-plans
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.
6BNBN/FlowPilot 127
-
dispatching-parallel-agents
Use when facing two or more independent tasks in Cursor that can be investigated or executed in parallel without conflicting edits or shared state.
6BNBN/FlowPilot 127
-
code-review
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.
6BNBN/FlowPilot 127
-
subagent-driven-development
Use when executing a larger plan in Cursor with parallel or delegated work, while keeping tasks narrowly scoped and reviewed between steps.
6BNBN/FlowPilot 127
-
requesting-code-review
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.
6BNBN/FlowPilot 127
-
receiving-code-review
Use when acting on code review feedback in Cursor, especially if suggestions seem unclear, debatable, or risky. Helps evaluate feedback technically before changing code.
6BNBN/FlowPilot 127
-
playwright
6BNBN/FlowPilot 127
-
frontend-design
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.
6BNBN/FlowPilot 127
-
finishing-a-development-branch
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.
6BNBN/FlowPilot 127
-
feature-dev
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.
6BNBN/FlowPilot 127
-
executing-plans
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.
6BNBN/FlowPilot 127
-
dispatching-parallel-agents
Use when facing two or more independent tasks in Cursor that can be investigated or executed in parallel without conflicting edits or shared state.
6BNBN/FlowPilot 127
-
code-review
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.
6BNBN/FlowPilot 127
-
brainstorming
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.
6BNBN/FlowPilot 127
-
using-git-worktrees
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
6BNBN/FlowPilot 127
-
receiving-code-review
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
6BNBN/FlowPilot 127
-
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
6BNBN/FlowPilot 127