3,106 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Generates an AgenticBrowser Scripting DSL orchestration that implements a feature end-to-end — plan (if needed), TDD implementation, tests, and a lint/style-guide review pass — previews it as docs/scripting-features/feature- .scripting.md, and on user approval runs it via st-eval. Use this whenever the user wants to…
Adds a solid-RED opsx:tdd gate to OpenSpec (between opsx:propose and opsx:apply). Converts a change's tests.md into REAL failing tests (real render, real data-testids, real assertions) that fail only because the implementation is missing. No expect.fail placeholders.
★not rated 6 2mo agoA
tokens not measured
originalMIT
Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
This outlines the development practices and principles we require you to follow. Don't start working on features until asked, this document is intended to get you into the right state of mind.
Complete feature development workflow with code mapping, TDD, task-based implementation, multi-agent review, UI verification, PR management, and state persistence.
★not rated 6 7mo agoA
tokens not measured
originalMIT
Claude Code instructions for sminnee/lsp-mcp, covering claude.md, project overview, development commands, testing practices and test-first development.
AGENTS.md instructions for kamiazya/whiteboard, covering project instructions, test layer selection, required workflow, 1. write the red test first and 2. turn it green locally.
AGENTS.md instructions for alanadson/yard, covering agents.md — how work gets done in this repository, the rule, 0. thirty seconds before you touch anything, 1. the cycle, step by step and red — write the test first.
The only skill you need to build and ship world-class software — from idea to production. Covers the COMPLETE lifecycle: architecture design, domain modeling, service boundaries, data architecture, implementation with TDD, distinctive frontend design (anti-AI-slop), exhaustive QA across all layers, security hardening…
Build a new feature using strict test-driven development — UNDERSTAND → DESIGN → RED → VERIFY RED → GREEN → VERIFY GREEN → REFACTOR → VALIDATE → REPEAT. Use when building a new feature with TDD, when the user says "TDD this", "tests first", "red green refactor", or asks for feature work that needs to be verifiable…
AGENTS.md instructions for mickeyyaya/evolve-loop, covering agents.md — cross-cli canonical instructions, what evolve-loop is, cross-cli invariants (the universal rules), 1. pipeline ordering is non-negotiable and 4. builder writes only inside its worktree.
Use when implementing any feature or bugfix, before writing implementation code. Triggered by keywords: TDD, BDD, test-first, test-driven, write-test-first.
Use when decomposing tasks into parallel sub-tasks or spawning sub-agents. Vendor-agnostic core; load a per-vendor reference for concrete tool names, directory conventions, and invocation syntax.
A test-planning skill that turns a specification's requirements and acceptance conditions into observable results, test scenarios, evidence, and proof obligations. TDD means writing tests or defining expected behavior before implementation.
A debugging workflow that reproduces a problem with a failing test, collects evidence, finds the underlying cause, applies a fix, and runs regression checks. Regression checks verify that the fix does not break behavior that already worked.
Production patterns for Hono v4+ backends with Bun, Drizzle ORM, Better Auth, Stoker, hono-openapi + Zod + Scalar, and TDD with Bun test runner. Use when building features, writing tests, reviewing code, or setting up auth/RBAC in modular monolith Hono projects. Apply whenever you see Hono route definitions…
TDD-focused implementation agent. Enforces strict RED → GREEN → VALIDATE → REFACTOR cycle. Works with or without plan files. Delegates specialized work to subagents.
Apply the SDLC practices from "Software Engineering: Standing on the Shoulders of Giants" to a codebase — either ADOPT them (write TDD, BDD, security, CI and stewardship rules into the project's AGENTS.md or equivalent agent-instructions file, for a new or existing project) or SCORE the repo against them (letter grade…
Instructions for matiasvillaverde/think, covering claude.md, quick reference, hierarchical documentation, development philosophy and test-driven development (tdd).
★not rated 5 6mo agoA1,689 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: