Agent Cursor
Draft GitHub issue titles and bodies aligned with ISSUETEMPLATE. Use proactively when opening a feature request or new issue. Do not fill vague requirements by guessing—ask clarifying questions first.
2 yesterday A 43 tokens
Agent Cursor
Build PR title and body from an approved plan and git diff, then run gh pr create. Use proactively after implementation is done and the branch is pushed. Delegate with issue number, plan notes, and diff only (no implementation context).
2 yesterday A 52 tokens
Agent Cursor
Read-only PR review when a pull request is opened. Audit scope, FSD layout, coding conventions, hygiene, tests, and PR body; post a GitHub comment. Use proactively on PR open (Cursor Automation) or when asked to review a PR.
2 yesterday A 57 tokens
self-review
04Agent Cursor
Pre-commit / pre-push self-review. Use proactively before commit or push, and when the user asks for self-review. Audit debug leftovers, TODO/FIXME, unnecessary ?., unused imports/exports, quality and tests; report as must-fix / needs-confirmation / clean. Delegate with diff and file list only (no implementation…
2 yesterday A 74 tokens
ai-workflow
05Cursor rule Cursor
Behavioral rules for the AI-led development workflow.
2 yesterday A 902 tokens
Cursor rule Cursor
Policy for autonomous improvement of rules and skills.
2 yesterday A 281 tokens
Cursor rule Cursor
Index of project standards and what enforces each (lint, architecture, agent, advisory).
2 yesterday A 733 tokens
Cursor rule Cursor
One canonical place per fact; indexes and comments link, they do not restate.
2 yesterday A 138 tokens
Skill Claude CodeCodexCursor
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.
2 yesterday A 61 tokens
coding-guide
10Skill Claude CodeCodexCursor
Project coding conventions and architecture constraints. Use when implementing, creating, or modifying components and modules (e.g. "create a component", "implement this feature").
2 yesterday A 35 tokens
Skill Claude CodeCodexCursor
Draft GitHub issue titles and bodies for this repository using .github/ISSUETEMPLATE form definitions. Use when opening or preparing a GitHub issue or feature request (e.g. "open an issue", "機能要望").
2 yesterday A 54 tokens
Skill Claude CodeCodexCursor
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.
2 yesterday A 48 tokens
Skill Claude CodeCodexCursor
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".
2 yesterday A 48 tokens
Skill Claude CodeCodexCursor
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…
2 yesterday A 70 tokens
Skill Claude CodeCodexCursor
Periodic code health checkup for design drift not caught by CI. Use at version bumps or when asked for a code health check / 健康診断 / 健診. Audits logged advisory deviations and runs a deepen-modules pass.
2 yesterday A 53 tokens
Skill Claude CodeCodexCursor
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").
2 yesterday A 54 tokens
Skill Claude CodeCodexCursor
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").
2 yesterday A 59 tokens
Skill Claude CodeCodexCursor
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.
2 yesterday A 54 tokens
Skill Claude CodeCodexCursor
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…
2 yesterday A 80 tokens
tune-prompt
20Skill Claude CodeCodexCursor
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…
2 yesterday A 84 tokens
version-up
21Skill Claude CodeCodexCursor
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.
2 yesterday A 50 tokens