temper

Quick Start: /plugin marketplace add galando/temper then /temper "add password reset" — one command for the full pipeline.

The Problem

AI writes code fast. But "fast" without "right" creates bugs, technical debt, and features that miss the point. AI-generated code has structural failure patterns:

Pattern	What Goes Wrong
Missing behaviors	Happy path works, edge cases never implemented
Wrong problem solved	Feature works perfectly, but nobody asked for it
Over-engineering	Factories and strategies for something used once
Hallucinated APIs	Methods called that don't exist
Missing wiring	Code correct, integration missing

Most AI tools check if code compiles. Temper checks if it solves the right problem, handles edge cases, and is safe to ship.

The Catch

The rate-limiting bug that vanilla AI always misses:

Scenario: Rate limiting on reset requests
  Given a user has requested 3 resets in 10 minutes
  When they request another reset
  Then the request is rejected with 429

AI built password reset. All tests pass. But Temper's scenario coverage gate caught the gap: no test for rate limiting. Build wrote the test. Test failed. Build implemented rate limiting. Test passed. Without the coverage gate, rate limiting would never have been implemented.

More: Evidence Gallery

How It Works

Three methodologies, one contract file (intent.md):

intent.md
|
+-- Intent (IDD)           WHY are we building this?
|   Problem, success criteria, constraints
|
+-- Scenarios (BDD)        WHAT should it do?
|   Gherkin Given/When/Then, derived BEFORE architecture
|
+-- /temper:build (TDD)    HOW do we build it?
    Tests from scenarios, RED → GREEN → REFACTOR

Key insight: Scenarios are derived before architecture. The file plan follows from what the system must do, not the other way around. This prevents over-engineering structurally.

Full methodology: docs/methodology.md

Commands

Command	Purpose
/temper	Full pipeline: plan → design? → build → review → check
/temper:plan	Blast radius + BDD scenarios + architecture
/temper:design	System design (complex/medium features)
/temper:build	Scenario-driven TDD + coverage gate
/temper:review	Intent validation + confidence scoring
/temper:check	Stack-aware validation pipeline
/temper:fix	Root cause analysis + regression test
/temper:pack	Manage quality packs
/temper:status	Quality metrics + observability dashboard

Quality Packs

Rule sets enforced during code generation and review. Three-tier resolution: project-local → global → built-in.

Pack	What It Enforces
quality	Method length, DRY, naming, complexity
tdd	RED-GREEN-REFACTOR, coverage
security	OWASP Top 10, no secrets in code
performance	N+1 detection, pagination, Core Web Vitals
api-design	Additive extension, idempotency, consistent naming
architecture-depth	Module depth: seams, adapters, locality, leverage

Create custom packs with /temper:pack or add a rules.md to .claude/packs/your-pack/.

Installation

Claude Code

/plugin marketplace add galando/temper
/plugin install temper

Cursor IDE

# Into a Temper repo checkout (regenerates .cursor/ from .claude/ sources):
./scripts/install-cursor.sh

# Into an arbitrary project (downloads a static snapshot):
bash <(curl -fsSL https://raw.githubusercontent.com/galando/temper/main/scripts/install-cursor.sh)