all publishers

6bnbn

@6bnbn source repo

71 published skills

  1. ▌
    Using Superpowers 3 · 6bnbn
    Use when starting any conversation to discover relevant skills and open the right SKILL.md files before responding, including before clarifying questions.
    137 repo stars
  2. ▌
    Playwright 2 · 6bnbn bundle
    ---
    137 repo stars
  3. ▌
    Code Review 3 · 6bnbn
    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.
    137 repo stars
  4. ▌
    Feature Dev 3 · 6bnbn
    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.
    137 repo stars
  5. ▌
    Superpowers 3 · 6bnbn
    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.
    137 repo stars
  6. ▌
    Brainstorming 3 · 6bnbn
    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.
    137 repo stars
  7. ▌
    Writing Plans 3 · 6bnbn
    Use when the user wants a written implementation plan in Cursor before editing code, especially for multi-step tasks or changes touching several files.
    137 repo stars
  8. ▌
    Writing Skills 3 · 6bnbn bundle
    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.
    137 repo stars
  9. ▌
    Executing Plans 3 · 6bnbn
    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.
    137 repo stars
  10. ▌
    Using Superpowers 2 · 6bnbn
    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.
    137 repo stars
  11. ▌
    Using Git Worktrees 3 · 6bnbn
    Use when starting feature work that should be isolated from the current checkout, especially in git repositories where a separate worktree would reduce risk.
    137 repo stars
  12. ▌
    Systematic Debugging 3 · 6bnbn bundle
    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.
    137 repo stars
  13. ▌
    Receiving Code Review 3 · 6bnbn
    Use when acting on code review feedback in Cursor, especially if suggestions seem unclear, debatable, or risky. Helps evaluate feedback technically before changing code.
    137 repo stars
  14. ▌
    Requesting Code Review 3 · 6bnbn
    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.
    137 repo stars
  15. ▌
    Test Driven Development 3 · 6bnbn bundle
    Use when implementing a feature, fixing a bug, or changing behavior in Cursor and you want a disciplined red-green-refactor workflow.
    137 repo stars
  16. ▌
    Dispatching Parallel Agents 3 · 6bnbn
    Use when facing two or more independent tasks in Cursor that can be investigated or executed in parallel without conflicting edits or shared state.
    137 repo stars
  17. ▌
    Subagent Driven Development 3 · 6bnbn
    Use when executing a larger plan in Cursor with parallel or delegated work, while keeping tasks narrowly scoped and reviewed between steps.
    137 repo stars
  18. ▌
    Code Review 4 · 6bnbn bundle
    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.
    137 repo stars
  19. ▌
    Feature Dev 4 · 6bnbn bundle
    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.
    137 repo stars
  20. ▌
    Superpowers 4 · 6bnbn
    Use when starting any conversation to discover relevant skills and open the right SKILL.md files before responding, including before clarifying questions.
    137 repo stars
  21. ▌
    Finishing A Development Branch 3 · 6bnbn
    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.
    137 repo stars
  22. ▌
    Verification Before Completion 3 · 6bnbn
    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.
    137 repo stars
  23. ▌
    Brainstorming 4 · 6bnbn
    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.
    137 repo stars
  24. ▌
    Writing Plans 4 · 6bnbn
    Use when you have a spec or requirements for a multi-step task, before touching code
    137 repo stars
  25. ▌
    Writing Skills 4 · 6bnbn bundle
    Use when creating new skills, editing existing skills, or verifying skills before deployment in Codex CLI.
    137 repo stars
  26. ▌
    Executing Plans 4 · 6bnbn
    Use when you have a written implementation plan to execute in a separate session with review checkpoints
    137 repo stars
  27. ▌
    Frontend Design 2 · 6bnbn
    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.
    137 repo stars
  28. ▌
    Using Git Worktrees 4 · 6bnbn
    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
    137 repo stars
  29. ▌
    Systematic Debugging 4 · 6bnbn bundle
    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
    137 repo stars
  30. ▌
    Receiving Code Review 4 · 6bnbn
    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
    137 repo stars
  31. ▌
    Requesting Code Review 4 · 6bnbn bundle
    Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
    137 repo stars
  32. ▌
    Test Driven Development 4 · 6bnbn bundle
    Use when implementing any feature or bugfix, before writing implementation code
    137 repo stars
  33. ▌
    Dispatching Parallel Agents 4 · 6bnbn
    Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
    137 repo stars
  34. ▌
    Subagent Driven Development 4 · 6bnbn bundle
    Use when executing implementation plans with independent tasks in the current session
    137 repo stars
  35. ▌
    Finishing A Development Branch 4 · 6bnbn
    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
    137 repo stars
  36. ▌
    Verification Before Completion 4 · 6bnbn
    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
    137 repo stars
  37. ▌
    Finishing A Development Branch 2 · 6bnbn
    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
    137 repo stars
  38. ▌
    Verification Before Completion 2 · 6bnbn
    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
    137 repo stars
  39. ▌
    Code Review 2 · 6bnbn bundle
    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.
    137 repo stars
  40. ▌
    Feature Dev 2 · 6bnbn bundle
    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.
    137 repo stars
  41. ▌
    Superpowers 2 · 6bnbn
    Use when starting any conversation to discover relevant skills and open the right SKILL.md files before responding, including before clarifying questions.
    137 repo stars
  42. ▌
    Brainstorming 2 · 6bnbn
    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.
    137 repo stars
  43. ▌
    Writing Plans 2 · 6bnbn
    Use when you have a spec or requirements for a multi-step task, before touching code
    137 repo stars
  44. ▌
    Writing Skills 2 · 6bnbn bundle
    Use when creating new skills, editing existing skills, or verifying skills before deployment in Codex CLI.
    137 repo stars
  45. ▌
    Executing Plans 2 · 6bnbn
    Use when you have a written implementation plan to execute in a separate session with review checkpoints
    137 repo stars
  46. ▌
    Using Git Worktrees 2 · 6bnbn
    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
    137 repo stars
  47. ▌
    Systematic Debugging 2 · 6bnbn bundle
    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
    137 repo stars
  48. ▌
    Receiving Code Review 2 · 6bnbn
    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
    137 repo stars
  49. ▌
    Requesting Code Review 2 · 6bnbn bundle
    Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
    137 repo stars
  50. ▌
    Test Driven Development 2 · 6bnbn bundle
    Use when implementing any feature or bugfix, before writing implementation code
    137 repo stars
  51. ▌
    Dispatching Parallel Agents 2 · 6bnbn
    Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
    137 repo stars
  52. ▌
    Subagent Driven Development 2 · 6bnbn bundle
    Use when executing implementation plans with independent tasks in the current session
    137 repo stars
  53. ▌
    Superpowers · 6bnbn
    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.
    137 repo stars
  54. ▌
    Brainstorming · 6bnbn
    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.
    137 repo stars
  55. ▌
    Writing Plans · 6bnbn
    Use when the user wants a written implementation plan in Cursor before editing code, especially for multi-step tasks or changes touching several files.
    137 repo stars
  56. ▌
    Writing Skills · 6bnbn bundle
    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.
    137 repo stars
  57. ▌
    Executing Plans · 6bnbn
    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.
    137 repo stars
  58. ▌
    Using Superpowers · 6bnbn
    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.
    137 repo stars
  59. ▌
    Using Git Worktrees · 6bnbn
    Use when starting feature work that should be isolated from the current checkout, especially in git repositories where a separate worktree would reduce risk.
    137 repo stars
  60. ▌
    Frontend Design · 6bnbn
    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.
    137 repo stars
  61. ▌
    Systematic Debugging · 6bnbn bundle
    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.
    137 repo stars
  62. ▌
    Receiving Code Review · 6bnbn
    Use when acting on code review feedback in Cursor, especially if suggestions seem unclear, debatable, or risky. Helps evaluate feedback technically before changing code.
    137 repo stars
  63. ▌
    Requesting Code Review · 6bnbn
    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.
    137 repo stars
  64. ▌
    Test Driven Development · 6bnbn bundle
    Use when implementing a feature, fixing a bug, or changing behavior in Cursor and you want a disciplined red-green-refactor workflow.
    137 repo stars
  65. ▌
    Dispatching Parallel Agents · 6bnbn
    Use when facing two or more independent tasks in Cursor that can be investigated or executed in parallel without conflicting edits or shared state.
    137 repo stars
  66. ▌
    Subagent Driven Development · 6bnbn
    Use when executing a larger plan in Cursor with parallel or delegated work, while keeping tasks narrowly scoped and reviewed between steps.
    137 repo stars
  67. ▌
    Finishing A Development Branch · 6bnbn
    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.
    137 repo stars
  68. ▌
    Verification Before Completion · 6bnbn
    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.
    137 repo stars
  69. ▌
    Playwright · 6bnbn bundle
    ---
    137 repo stars
  70. ▌
    Code Review · 6bnbn
    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.
    137 repo stars
  71. ▌
    Feature Dev · 6bnbn
    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.
    137 repo stars