STDD (Spec and Test Driven Development) methodology, skills, and templates for Claude Code
Skill Claude CodeCodex
An automated workflow that takes a software task from an issue, document, URL, or plain description through clarification, specifications, planning, coding, testing, review, design updates, and pull-request creation.
Skill Claude CodeCodex
A guide for creating a pull request from the current code branch to the repository's primary branch. A pull request is a proposal to merge reviewed changes into the main line of development.
Skill Claude CodeCodex
A guide for creating and managing PLAN documents: task lists that describe the work planned for one development session. It is part of STDD, or Spec and Test Driven Development.
Skill Claude CodeCodex
A Japanese-language guide and template for writing REQUIREMENTS.md files, which record what a feature must do and why. It follows STDD, meaning Spec and Test Driven Development, and covers business, functional, and non-functional requirements.
Skill Claude CodeCodex
A Japanese-language skill for creating technical design and test-plan documents, plus shared architecture, database-table, API, and design specifications. It follows STDD, or Spec and Test Driven Development, where requirements guide the design and tests.
Skill Claude CodeCodex
A tool that turns written requirements into simple HTML wireframes, or rough screen layouts, showing pages, controls, labels, and common states.
Skill Claude CodeCodex
A guided process for adding STDD, or Spec and Test Driven Development, to an existing working project. It records progress in a plan and moves through documentation, feature analysis, implementation, and review.
Skill Claude CodeCodex
A set of development principles based on Kaizen, the practice of making small continuous improvements. It covers preventing errors, avoiding unnecessary work, reusing proven patterns, and refactoring step by step.
Skill Claude CodeCodex
A process that examines an existing project and creates shared specification documents for its business requirements, architecture, database tables, and APIs, when APIs exist.
Skill Claude CodeCodex
A guide for documenting and testing an existing software feature or page by studying how its code already works. It creates requirement, design, and test documents that describe the current behavior rather than an imagined future version.
Skill Claude CodeCodex
A workflow for reviewing an existing pull request with two specialist agents: one focused on testing and logic, and one focused on code quality and security. A pull request is a proposed code change submitted for review before merging.
Skill Claude CodeCodex
Software design guidelines based on Clean Architecture, which separates code by responsibility, and domain-driven design, which models the business concepts directly. It also recommends a library-first approach and consistent naming.
Skill Claude CodeCodex
A project-specific format for writing software specifications, including requirements, technical design, tests, naming, and document layout. It adapts the STDD (Spec and Test Driven Development) templates to an existing or new project.
Skill Claude CodeCodex
A consistency checker for software specifications, tests, and implementation. It compares stable requirement and feature IDs across those layers to find missing or mismatched parts.
Skill Claude CodeCodex
A guide for building user interfaces, including admin screens, tables, forms, validation, and layouts that adapt to different screen sizes. It tells the agent to follow the project’s requirements and technical design documents.
Skill Claude CodeCodex
A guide for creating, running, and correcting Supabase database migrations. Supabase is a service that provides a hosted database; migrations are tracked SQL changes such as new tables, columns, permissions, and access policies.
Skill Claude CodeCodex
A guide for creating and running Playwright end-to-end tests. Playwright is a tool that drives a browser to test what users see and do.
Skill Claude CodeCodex
A skill for running end-to-end tests inside a development container associated with a Git worktree. End-to-end tests check a complete user flow through the running application.
Skill Claude CodeCodex
A skill for finding and deleting the current numbered Git worktree and its related development container. A worktree is a separate working directory connected to the same Git repository.
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: