6bnbn
100 verified skills11,760 total stars
playwright
Use when the task requires automating a real browser from the terminal in Cursor, including navigation, form filling, snapshots, screenshots, data extraction, and UI-flow debugging via `playwright-cli` or the bundled wrapper scripts.
tools128
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.
development128
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.
development128
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.
testing128
writing-plans
Use when the user wants a written implementation plan in Cursor before editing code, especially for multi-step tasks or changes touching several files.
development128
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.
testing128
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.
development128
test-driven-development
Use when implementing a feature, fixing a bug, or changing behavior in Cursor and you want a disciplined red-green-refactor workflow.
development128
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.
development128
using-git-worktrees
Use when starting feature work that should be isolated from the current checkout, especially in git repositories where a separate worktree would reduce risk.
testing128
using-superpowers
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.
testing128
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.
testing128
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.
development128
verification-before-completion
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.
development128
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.
development128
writing-skills
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.
testing128
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.
development128
superpowers
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.
development128
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.
development128
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
tools128
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.
development115
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
testing115
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
testing115
feature-dev
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.
tools115
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.
development115
finishing-a-development-branch
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
development115
finishing-a-development-branch
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
development115
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.
development115
playwright
Use when the task requires automating a real browser from the terminal in Cursor, including navigation, form filling, snapshots, screenshots, data extraction, and UI-flow debugging via `playwright-cli` or the bundled wrapper scripts.
tools115
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
development115
superpowers
Use when starting any conversation to discover relevant skills and open the right SKILL.md files before responding, including before clarifying questions.
tools115
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
development115
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.
development115
test-driven-development
Use when implementing a feature, fixing a bug, or changing behavior in Cursor and you want a disciplined red-green-refactor workflow.
development115
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
tools115
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
tools115
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
tools115
using-git-worktrees
Use when starting feature work that should be isolated from the current checkout, especially in git repositories where a separate worktree would reduce risk.
testing115
using-git-worktrees
Use when starting feature work that should be isolated from the current checkout, especially in git repositories where a separate worktree would reduce risk.
testing115
using-superpowers
Use when starting any conversation to discover relevant skills and open the right SKILL.md files before responding, including before clarifying questions.
tools115
using-superpowers
Use when starting any conversation to discover relevant skills and open the right SKILL.md files before responding, including before clarifying questions.
tools115
verification-before-completion
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.
development115
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
development115
writing-plans
Use when the user wants a written implementation plan in Cursor before editing code, especially for multi-step tasks or changes touching several files.
development115
writing-skills
Use when creating new skills, editing existing skills, or verifying skills before deployment in Codex CLI.
tools115
writing-skills
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.
testing115
brainstorming
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.
development115
code-review
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.
tools115
code-review
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.
tools115
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.
development115
superpowers
Use when starting any conversation to discover relevant skills and open the right SKILL.md files before responding, including before clarifying questions.
tools115
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
development115
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
development115
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.
testing115
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.
testing115
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.
development115
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.
development115
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.
development115
writing-plans
Use when the user wants a written implementation plan in Cursor before editing code, especially for multi-step tasks or changes touching several files.
development115
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
development115
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
tools115
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.
development115
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
tools115
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.
development115
using-superpowers
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.
testing115
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.
development115
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
development115
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
development115
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.
testing115
writing-skills
Use when creating new skills, editing existing skills, or verifying skills before deployment in Codex CLI.
tools115
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.
development115
superpowers
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.
development115
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
testing115
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.
development115
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.
development115
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.
development115
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.
testing115
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.
testing115
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
tools115
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
development115
verification-before-completion
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
data-ai115
feature-dev
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.
tools115
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.
development115
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
development115
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
development115
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
testing115
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
development115
verification-before-completion
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
data-ai115
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.
testing115
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.
development115
using-superpowers
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.
testing115
verification-before-completion
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.
development115
playwright
Use when the task requires automating a real browser from the terminal in Cursor, including navigation, form filling, snapshots, screenshots, data extraction, and UI-flow debugging via `playwright-cli` or the bundled wrapper scripts.
tools115
superpowers
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.
development115
test-driven-development
Use when implementing a feature, fixing a bug, or changing behavior in Cursor and you want a disciplined red-green-refactor workflow.
development115
writing-skills
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.
testing115
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.
tools115
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.
tools115
brainstorming
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.
development115
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.
development115