Guidance for designing stable interfaces between software components, including REST APIs, GraphQL schemas, modules, and UI component properties. An API is the agreed way that one piece of software communicates with another.
A browser-testing skill that checks a website while it is running in a real browser through Chrome DevTools. It can inspect the page structure, styles, console messages, network activity, performance data, and accessibility tree.
A guide for setting up automated checks and deployment pipelines. CI/CD means automatically testing, checking, building, and sometimes releasing software when changes are made.
A code-review checklist that examines changes for correctness, readability, system design, security, and speed. It is meant to be used before merging code, meaning before adding it to the shared main branch.
A guide for deciding which project information a coding agent should see, and when. It organizes persistent rules, architecture documents, relevant source files, test results, errors, and conversation history.
A step-by-step method for finding the root cause of test failures, broken builds, unexpected behavior, bugs, and production incidents. It starts by preserving evidence and reproducing the problem before making a fix.
A guide for retiring old software, APIs, or features and moving users to replacements. Deprecation means formally ending support for something; migration means moving its users or callers to another system.
A guide for recording important engineering decisions and the reasons behind them. An ADR, or architecture decision record, is a short document that explains a major technical choice, its context, and the alternatives considered.
A guide for building and changing production-ready user interfaces. It covers components, layouts, responsive behavior, accessibility, interaction, state management, and visual consistency.
A set of Git practices for saving, organizing, reviewing, and rolling back code changes. Git is a version-control system that records project history through commits and separates work through branches.
An interactive process for turning an early idea into a clear, practical concept. It explores different directions, tests hidden assumptions, and produces a short plan covering the problem, recommended direction, first version, and exclusions.
A way to build and deliver changes in small, complete slices. Each slice is implemented, tested, checked, and saved as a separate Git commit before the next slice begins.
A measurement-led guide for finding and fixing application slowdowns. It covers both web pages and backend services, including Core Web Vitals, which are standard measures of how quickly and steadily a page loads and responds.
A planning guide that turns a clear specification or requirement into small, ordered tasks with clear acceptance checks. It also maps dependencies so work can be done in a sensible order.
A set of secure coding practices for software that handles user input, accounts, sensitive data, or outside services. It treats information from outside the application as potentially unsafe and requires checks at system boundaries.
A production-release checklist and planning guide for putting software in front of users. It covers checks such as tests, security, performance, accessibility, infrastructure, documentation, monitoring, and rollback planning.
A development method that writes a clear specification before any code. The specification records the goal, requirements, project layout, commands, and checks for deciding when the work is complete.
A development method where you write a test that fails, add the smallest amount of code to pass it, and then clean up the code while keeping the test passing. Tests are checks that show whether code behaves as expected.
A guide for finding and using agent skills, which are instructions for common software-development tasks. It maps work such as planning, coding, testing, debugging, reviewing, and releasing to the relevant skill.
6 4mo agoA45 tokens
originalMIT
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: