Cursor rule Cursor
A set of rules for designing APIs that remain clear and compatible as they change. API means the contract through which software systems exchange requests, responses, errors, and events.
Cursor rule Cursor
A set of rules for building reliable backend services, including stable API contracts, access control, safe concurrent writes and useful error information. Backend services handle requests and data behind an application.
Cursor rule Cursor
A code-review method that checks software changes for correctness, security, performance, maintainability and adequate tests. Its instructions are written in Chinese.
Cursor rule Cursor
A debugging method that uses reproducible evidence to find the root cause of a software problem, then proposes the smallest fix and a way to verify it. Its instructions are written in Chinese.
Cursor rule Cursor
Rules for implementing reliable, accessible, consistent, and fast user interfaces as a frontend engineer.
Cursor rule Cursor
A prompt library for coordinating coding roles such as planning, implementation, testing, review, verification, pull-request writing, and release management.
Cursor rule Cursor
A planning process that turns a significant software change into small, verifiable, reversible tasks written in an IMPLEMENTATION_PLAN.md file.
Cursor rule Cursor
A set of rules for turning an implementation plan and code changes into a clear pull request description. A pull request is a proposed code change submitted for review before merging.
Cursor rule Cursor
A set of concrete manual tests and regression checks for a software change. Regression checks confirm that existing behavior still works after an update.
Cursor rule Cursor
A set of rules for restructuring code while keeping its outward behavior unchanged. It requires tests or other checks before making small, reversible changes.
Cursor rule Cursor
A release checklist and rollout plan for putting code changes into production safely, including migrations, feature switches, monitoring, and rollback.
Cursor rule Cursor
A set of rules for performing a focused security review of software changes. It checks areas such as access control, input validation, sensitive data, dependencies, and common web vulnerabilities.
Cursor rule Cursor
A project rule for choosing and running the smallest useful set of tests after code changes, then explaining what the results mean. Tests are checks that help show whether software still works.
Cursor rule Cursor
A project rule for reviewing how a user interface works, including its wording, feedback, errors, forms, consistency, and accessibility. Accessibility means making the interface usable with tools such as keyboards and screen readers.
Cursor rule Cursor
A project rule for checking each planned acceptance requirement against the actual code changes and test evidence. Acceptance criteria are specific conditions that must be met for work to count as complete.
Cursor rule Cursor
Always-on pointer to planner→ACT→implementer workflow and AGENTS.md.
Skill Claude CodeCodexCursor
Create a GitHub pull request with gh: push branch if needed, draft title/body from IMPLEMENTATIONPLAN.md and recent commits (pr-author style), and open the PR. Use when the user asks to open/create a PR, “开 PR”, or finalize shipping.
Skill Claude CodeCodexCursor
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports (1) auto-detecting type and scope from changes, (2) generating conventional commit messages from diff, (3) interactive…
Skill Claude CodeCodexCursor
A scanner that measures technical debt and code smells—patterns that make software harder to understand or change—in a code repository. It supports Python, Go, Java, Rust, C and C++, JavaScript, TypeScript, and SQL.
Instructions file CodexOpenCode
Instructions for ymhhh/cursor-implements, covering agents.md — cursor-implements workflow, mainline, role raci (quick), skills and hooks (pipeline gates).