Plugin Claude Code
A plugin that provides agents, skills, and commands for incremental software development using a two-track AI-agent process, based on an Anthropic paper.
Plugin Claude Code
A plugin that provides agents, skills, and commands for incremental software development using a two-track AI-agent process, based on an Anthropic paper.
Agent
An incremental coding-agent guide written in Chinese for implementing one feature at a time. It requires checking project progress and history, testing changes, updating progress notes, and committing completed work.
Agent
An initialization agent that sets up a new software project from the user's starting request without relying on a template.
Command
An automated development workflow for a long-running coding project. It checks whether the project is new or already has a feature list, then chooses an initialization agent or an agent that continues incremental development.
Skill Claude CodeCodex
Design and create loading pages, loading animations, progress indicators, skeleton screens, and loading spinners. Use this skill whenever the user wants to create a loading page, loading spinner, progress bar, skeleton loader, or any loading state UI. This includes splash screens, brand loading pages, inline loading…
Cursor rule
A set of rules for generating Go model, persistence-object, and converter files from SQL CREATE TABLE statements. A persistence object is the database-facing version of a data structure.
Cursor rule
A set of rules for writing unit tests in Go, the programming language used by the examples. It covers test names, table-driven cases, subtests, mocks, assertions, file placement, and basic test quality principles.
Cursor rule
A set of rules for writing and changing Go code according to Uber's Go style guidelines. It covers formatting, imports, names, declarations, and related code conventions.
Cursor rule
A keyword-based rule set that selects other project instructions when specific words appear in a request.
Cursor rule
A project-structure rule for Go applications using domain-driven design, an approach that organizes code around business concepts. It describes folders for APIs, services, domain models, infrastructure, deployments, documentation, and shared tools.
Cursor rule
A conversation rule for handling complex questions that lack important details. It asks for context such as the role, background, goal, desired output, and ways to verify the answer.
Cursor rule
A set of rules for writing technical solution documents in a project's docs folder. The template covers requirements, purpose, design, diagrams, database and API changes, rollout notes, and task breakdowns.
Cursor rule
A set of rules for turning a product request into a clear, checkable plan. It covers gathering context, splitting work into smaller features, checking technical feasibility, and recording risks and acceptance criteria.
Cursor rule
Rules for breaking a large software request into smaller tasks with clear inputs, outputs, dependencies, status markers, and acceptance criteria. They limit each task's size and require it to be independently verifiable.
Cursor rule
A review procedure for Go code changes. It checks code quality, security risks, performance issues, affected services, release dependencies, and produces a review report.
Cursor rule
A Git commit review and message-formatting procedure. It checks code changes for risks before creating a commit and uses a structured format for the commit message.
Cursor rule
A rule for turning a code change and its chat history into a documented development procedure. It asks for a file tree, a Mermaid dependency diagram, and notes about likely problems and fixes.