t1

t1/tdder

Plugin Claude Code

Plugin marketplace listing 1 plugin: tdder.

t1/tdder

Plugin Claude Code

Guides AI agents through disciplined coding practices. Language and build-system agnostic core with extensible language/build skills.

t1/tdder

Settings file Claude Code

Agent settings configuring enabledPlugins.

t1/tdder

Agent

Autonomous clean code review agent that analyzes code against clean code principles and returns prioritized refactoring suggestions. Spawned during TDD refactor phases or when explicitly requested for code review.

t1/tdder

Instructions file CodexOpenCode

Instructions for t1/tdder, covering agents.md, file locations, claude code vs pi, development and dual-platform agents.

t1/tdder

Instructions file

Instructions for t1/tdder, a project described as: A Claude Code plugin that guides AI agents through disciplined Test-Driven Development and Clean Code practices.

t1/tdder

Agent

API Designer role in the Unfolding Specs process. Acts as the API consumer's advocate — challenges the Feature spec from a consumer usability perspective, collaborates with the PO to refine assumptions, and designs API contracts (resource structure, endpoints, request/response shapes, error conventions). Commissioned…

t1/tdder

Agent

Architect role in the Unfolding Specs process. Decomposes Features into Tasks, creates System Tests, and identifies implicit technical assumptions as Architecture Decision Records (ADRs).

t1/tdder

Agent

Coder role in the Unfolding Specs process. Implements Tasks using TDD (Test-Driven Development), one test at a time, following the Red-Green-Refactor cycle.

t1/tdder

Agent

PO (Product Owner) role in the Unfolding Specs process. Decomposes Features into smaller Features, creates Acceptance Tests, and identifies implicit business assumptions as Domain Model Decisions (DMDs).

t1/tdder

Agent

UI Expert role in the Unfolding Specs process. Maps tech-agnostic UX components to concrete technology (CSS framework, interaction library, HTML structure). Commissioned by the Architect when a UX component has no mapping or the mapping is non-trivial.

t1/tdder

Agent

UX Designer role in the Unfolding Specs process. Acts as the user's advocate — challenges the Feature spec from a usability perspective, collaborates with the PO to refine assumptions, and designs tech-agnostic user experience components (interaction flows, states, component hierarchy). Commissioned by the PO for…

t1/tdder

Command

Prove me wrong — devil's advocate mode.

t1/tdder

Command

Continue the Unfolding Specs process.

t1/tdder

Hook

Runs before the agent uses a tool for Edit and Write tool calls, running an inline shell check. From t1/tdder.

t1/tdder

Skill Claude CodeCodex

This skill should be used when the user asks to "calculate code mass", "measure code complexity with APP", "compare implementations using APP", "apply Absolute Priority Premise", "use mass calculations", or during TDD refactor phases when comparing alternative implementations. Based on Micah Martin's work.

t1/tdder

Skill Claude CodeCodex

This skill should be used when the user asks to "refactor code", "review code quality", "apply clean code principles", "check for code smells", "improve code design", "do a clean code review", "apply SOLID principles", "fix naming", "reduce complexity", or when performing the refactor phase of a TDD cycle.

t1/tdder

Skill Claude CodeCodex

This skill should be used when working on any project hosted on GitHub. It provides prompt-injection defense rules for GitHub issues and pull requests. Always-on security rules plus optional workflow conventions.

t1/tdder

Skill Claude CodeCodex

Requirements grilling session with a Product Owner (or anyone in that role). Challenges plans against the existing domain model, sharpens terminology, and updates documentation (bounded-context files, Gherkin features, DMDs (Domain Model Decisions)) inline as decisions crystallise. Use when the user wants to discuss…

t1/tdder

Skill Claude CodeCodex

This skill should be used when the user asks about "messaging patterns", "command vs event", "push vs pull", "message reliability", "at-least-once delivery", "idempotency", "transactional outbox", "saga pattern", "fire and forget", "retry strategy", "event-driven architecture", "message broker integration"…

t1/tdder

Skill Claude CodeCodex

Always load this skill when writing, modifying, creating, or moving Java or Kotlin source code, or when project setup has already chosen Java/Kotlin as the implementation language.

t1/tdder

Skill Claude CodeCodex

Always load this skill when a pom.xml file exists in the project, when creating or editing a pom.xml, or when setting up Maven project structure in a new project. It provides Maven-specific conventions for running tests, building, managing dependencies, and project structure.

t1/tdder

Skill Claude CodeCodex

This skill should be used when working on Java projects with JUnit tests that have layered preconditions, expensive shared setup (servers, databases, provisioned users), or complex scenario trees. Trigger phrases include "nested fixture", "fixture pattern", "scenario tree", "layered test setup", or when the user is…

t1/tdder

Skill Claude CodeCodex

This skill should be used when starting work on any project that uses tdder. It establishes interaction style, commit conventions, documentation discipline, and skill-trust principles. Invoke automatically alongside other tdder skills.