Skill Cursor
Triage GitHub PR review feedback (top-level, inline, threads); implement agreed items; escalate disagreements or questions. Includes lint/test checks, per-thread replies with commit SHA, and a chat summary. Use when fixing review feedback on an open PR—not for greenfield implementation only.
Skill Cursor
Project coding conventions and architecture constraints. Use when implementing, creating, or modifying components and modules (e.g. "create a component", "implement this feature").
Skill Cursor
A skill for preparing GitHub issue titles and descriptions using this repository's issue-template definitions. GitHub issues are records used to report bugs, request features, or track work.
Skill Cursor
Create a PR aligned with the AI-led workflow: summary, design (when relevant), impact and risks. Use when creating a pull request, opening a PR, pushing for review, or completing implementation of an issue.
Skill Cursor
Explore the codebase for chances to turn shallow modules into deep modules per A Philosophy of Software Design. Use when improving architecture, finding refactoring opportunities, looking for shallow modules, or the user mentions "deepen".
Skill Cursor
When designing a module or API, run parallel subagents to produce fundamentally different options and compare them. The first idea is rarely best—practice "Design It Twice" from A Philosophy of Software Design. Use when designing an API, exploring interface shapes, or the user mentions "design it twice" or "interface…
Skill Cursor
A scheduled review of a codebase for design changes and structural problems that normal automated checks may miss.
Skill Cursor
Read a GitHub Issue and run branch creation through implementation, commit, and PR. Use when the user asks to implement, work on, or execute a GitHub issue (e.g. "implement #123", "work on Issue #42").
Skill Cursor
Feature-Sliced Design (FSD) project layout: layer dependencies, slice structure, and naming conventions. Use when creating directories, moving files between layers, or deciding where to place modules (e.g. "where does this component go?", "explain the directory structure").
Skill Cursor
Read-only review of an open pull request: scope, FSD layout, coding conventions, hygiene, tests, and PR body. Post findings as a GitHub PR comment. Use when a PR is opened or when asked to review a PR.
Skill Cursor
Propose codifying reusable lessons from trial-and-error or explicit user requests into lint, rules, or skills. Use near task completion after failed first attempts, or when the user asks to "make it a rule" or "leave a lesson". NOT for empirically testing instructions on fresh agents (tune-prompt) or drafting a new…
Skill Cursor
Empirically test skills, rules, or prompts on fresh agents with scored checklists; edit one theme per cycle until instructions land. Use after creating or heavily revising agent instructions, when agents misbehave on those instructions, or when validating that a skill is followed correctly. NOT for codifying runtime…
Skill Cursor
Explain or override the automated release path. Versions normally bump on each merge to main from the PR's semver: label. Use when asked to "version up", to recover a failed auto-release, or for an exceptional manual bump.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: