6bnbn
- 35 skills
- 0 followers
- 4 hours ago last updated
- ▌ Finishing A Development Branch 2 · 6bnbnUse 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
- ▌ Verification Before Completion 2 · 6bnbnUse 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
- ▌ Code Review 2 · 6bnbn bundleUse 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.
- ▌ Feature Dev 2 · 6bnbn bundleUse 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.
- ▌ Superpowers 2 · 6bnbnUse when starting any conversation to discover relevant skills and open the right SKILL.md files before responding, including before clarifying questions.
- ▌ Brainstorming 2 · 6bnbnYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- ▌ Writing Plans 2 · 6bnbnUse when you have a spec or requirements for a multi-step task, before touching code
- ▌ Writing Skills 2 · 6bnbn bundleUse when creating new skills, editing existing skills, or verifying skills before deployment in Codex CLI.
- ▌ Executing Plans 2 · 6bnbnUse when you have a written implementation plan to execute in a separate session with review checkpoints
- ▌ Using Git Worktrees 2 · 6bnbnUse 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
- ▌ Systematic Debugging 2 · 6bnbn bundleUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- ▌ Receiving Code Review 2 · 6bnbnUse 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
- ▌ Requesting Code Review 2 · 6bnbn bundleUse when completing tasks, implementing major features, or before merging to verify work meets requirements.
- ▌ Test Driven Development 2 · 6bnbn bundleUse when implementing any feature or bugfix, before writing implementation code
- ▌ Dispatching Parallel Agents 2 · 6bnbnUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
- ▌ Subagent Driven Development 2 · 6bnbn bundleUse when executing implementation plans with independent tasks in the current session
- ▌ Superpowers · 6bnbnUse 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.
- ▌ Brainstorming · 6bnbnUse before implementing a new feature, changing behavior, or making design-heavy decisions in Cursor. Helps clarify intent, explore approaches, and get approval before coding.
- ▌ Writing Plans · 6bnbnUse when the user wants a written implementation plan in Cursor before editing code, especially for multi-step tasks or changes touching several files.
- ▌ Writing Skills · 6bnbn bundleUse 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.
- ▌ Executing Plans · 6bnbnUse when a written implementation plan already exists in Cursor and the next step is to execute it in small batches with checkpoints and verification.
- ▌ Using Superpowers · 6bnbnUse 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.
- ▌ Using Git Worktrees · 6bnbnUse when starting feature work that should be isolated from the current checkout, especially in git repositories where a separate worktree would reduce risk.
- ▌ Frontend Design · 6bnbnCreate 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.
- ▌ Systematic Debugging · 6bnbn bundleUse 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.
- ▌ Receiving Code Review · 6bnbnUse when acting on code review feedback in Cursor, especially if suggestions seem unclear, debatable, or risky. Helps evaluate feedback technically before changing code.
- ▌ Requesting Code Review · 6bnbnUse 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.
- ▌ Test Driven Development · 6bnbn bundleUse when implementing a feature, fixing a bug, or changing behavior in Cursor and you want a disciplined red-green-refactor workflow.
- ▌ Dispatching Parallel Agents · 6bnbnUse when facing two or more independent tasks in Cursor that can be investigated or executed in parallel without conflicting edits or shared state.
- ▌ Subagent Driven Development · 6bnbnUse when executing a larger plan in Cursor with parallel or delegated work, while keeping tasks narrowly scoped and reviewed between steps.
- ▌ Finishing A Development Branch · 6bnbnUse 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.
- ▌ Verification Before Completion · 6bnbnUse before claiming work is complete, fixed, or passing in Cursor. Requires fresh verification evidence such as tests, builds, lint output, or direct reproduction checks.
- ▌
- ▌ Code Review · 6bnbnUse 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.
- ▌ Feature Dev · 6bnbnUse when building a new feature or substantial behavior change in Cursor and the user wants a structured workflow from discovery through implementation and review.