From 127ed0106485f12723de62b22966987cefbb7ffd Mon Sep 17 00:00:00 2001 From: Lukas Date: Sat, 14 Mar 2026 12:47:54 +0100 Subject: [PATCH] Add self-review checklist to CLAUDE.md Co-Authored-By: Claude Opus 4.6 --- CLAUDE.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 1b4df81..770fe05 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -71,6 +71,14 @@ docs/agents/ RPI skill artifacts (research reports, plans) - **Feature specs** live in `specs/NNN-feature-name/` with spec.md (and optionally plan.md, tasks.md for new work). Specs describe features, not individual changes. The project constitution is at `.specify/memory/constitution.md`. - **Quality gates** are enforced at pre-commit via Lefthook's `pnpm check` — the project's single earliest enforcement point. No gate may exist only as a CI step or manual process. +## Self-Review Checklist + +Before finishing a change, consider: +- Is this the simplest approach that solves the current problem? +- Is there duplication that hurts readability? (But don't abstract prematurely.) +- Are errors handled correctly and communicated sensibly to the user? +- Does the UI follow modern patterns and feel intuitive to interact with? + ## Speckit Workflow Speckit (`/speckit.*` skills) manages the spec-driven development pipeline. Specs are **living documents** that describe features, not individual changes.