A set of Claude Code skills for real-world software engineering, including requirements questioning, specifications and tickets, test-driven development, code review, and domain modeling. Test-driven development means writing tests before the implementation they check.
A collection of coding-agent skills for practical software engineering, including TDD, which means writing tests before or alongside code, and domain modeling, which means representing a business area clearly in software. It also covers requirements, debugging, code review, architecture, research, and implementation.
Project instructions for a Chinese translation of Matt Pocock's skills collection, using natural Chinese and established technical terms. The project is kept in daily sync with the original collection.
Repository instructions for maintaining a Chinese translation of a collection of coding skills, organized into folders and published as a Claude Code plugin.
A Chinese-language guide that helps choose the right skill or workflow for a coding task. It maps work from idea and planning through implementation and review.
A two-part code review process that compares your current changes with a chosen commit, branch, tag, or merge point. One review checks repository conventions, while the other checks the original requirements.
A design vocabulary and set of principles for organizing software modules, meaning pieces of code with an interface and an implementation. It focuses on small interfaces that hide substantial behavior, clear points for changing behavior, and code that is easier to test.
A structured process for finding the cause of difficult bugs and performance slowdowns. It builds a repeatable check that turns the reported problem into a clear pass-or-fail signal.
A skill for building and maintaining a shared model of the important concepts in a software project. It records precise terms, relationships, and architectural decisions in files such as CONTEXT.md and architecture decision records.
A small instruction that calls two other skills with the inputs “grilling” and “domain-modeling.” The available description does not explain what those skills do.
A coding workflow for implementing a specification or a set of work tickets. It includes regular type checks and tests, followed by code review and a commit.
A codebase review process that looks for architecture changes—ways to organize code—that could make future work easier. It presents possible improvements in an HTML report and examines the options you choose.
A disposable code prototype for answering a specific design question, such as whether a logic model works or which user interface feels right. It is meant to be tried briefly and then removed or kept only as a record of the decision.
A research workflow for investigating a question using first-party sources, such as official documentation, source code, standards, or an original API.
A procedure for resolving conflicts during an active Git merge or rebase. It traces the purpose of both changes, resolves each conflict, runs the project's checks, and completes the operation.
A setup skill that configures engineering skills for a repository, including its issue tracker, labels, and documentation layout. A repository is the project folder managed by version control.
Guidance for test-driven development (TDD), a method where you write a failing test, make it pass with a small change, and then improve the code. It focuses on tests that check user-visible behavior through public interfaces.
A method for turning the current conversation and codebase understanding into a detailed software specification, then publishing it as an issue in the project’s issue tracker. An issue tracker is a tool for recording and managing development work.
A method for turning a plan, specification, or conversation into small work tickets that each deliver a complete, testable slice of functionality. Each ticket records which other tickets must be finished first.
A structured issue-triage process that moves issues and, where configured, pull requests through classification and status steps. Triage means deciding what a report is, whether more information is needed, and who should handle it.
A planning method for large or unclear work that maps the decisions needed between the current situation and a defined destination. It records the map and decision tickets in an issue tracker.
A skill for creating temporary Bash scripts that guide a person through manual setup, credential, infrastructure, or migration steps. Bash is a command-line scripting language; the guide can open links, ask for values, and save them in approved places.
A workflow for implementing a complete technical specification across related tickets. A ticket is a tracked unit of work, and the workflow treats tickets as a dependency graph so available work can be handled in parallel.