weka/linter-driven-development

testing

Use when creating leaf types, after refactoring, during implementation, or when testing advice is needed. Automatically invoked to write tests for new types, or use as testing expert advisor. Covers the composition ladder from rung-0 unit tests to…

원문 언어: 영어

documentation

The repo-brain author/maintainer: writes behavior-focused documentation and wires it into the documentation network defined by rules/R9-repo-brain.md. FEATURE mode (default): after feature implementation or bug fixes — invoked by @linter-driven-development…

원문 언어: 영어

pre-commit-review

ADVISORY pre-commit review that orchestrates four parallel rule-family hunters, an over-abstraction skeptic, and a comment critic against the diff. Spawns read-only agents (rule-hunter, overabstraction-skeptic, comment-critic); NEVER edits code. Invoked by…

원문 언어: 영어

documentation

The repo-brain author/maintainer: writes behavior-focused documentation and wires it into the documentation network defined by rules/R9-repo-brain.md. FEATURE mode (default): after feature implementation or bug fixes — invoked by @linter-driven-development…

원문 언어: 영어

pre-commit-review

ADVISORY pre-commit review that orchestrates four parallel rule-family hunters, an over-abstraction skeptic, and a comment critic against the diff. Spawns read-only agents (rule-hunter, overabstraction-skeptic, comment-critic); NEVER edits code. Invoked by…

원문 언어: 영어

documentation

The repo-brain author/maintainer: writes behavior-focused documentation and wires it into the documentation network defined by rules/R9-repo-brain.md. FEATURE mode (default): after feature implementation or bug fixes — invoked by @linter-driven-development…

원문 언어: 영어

pre-commit-review

ADVISORY pre-commit review that orchestrates four parallel rule-family hunters, an over-abstraction skeptic, and a comment critic against the diff. Spawns read-only agents (rule-hunter, overabstraction-skeptic, comment-critic); NEVER edits code. Invoked by…

원문 언어: 영어

documentation

The repo-brain author/maintainer: writes behavior-focused documentation and wires it into the documentation network defined by rules/R9-repo-brain.md. FEATURE mode (default): after feature implementation or bug fixes — invoked by @linter-driven-development…

원문 언어: 영어

pre-commit-review

ADVISORY pre-commit review that orchestrates four parallel rule-family hunters, an over-abstraction skeptic, and a comment critic against the diff. Spawns read-only agents (rule-hunter, overabstraction-skeptic, comment-critic); NEVER edits code. Invoked by…

원문 언어: 영어

documentation

The repo-brain author/maintainer: writes behavior-focused documentation and wires it into the documentation network defined by rules/R9-repo-brain.md. FEATURE mode (default): after feature implementation or bug fixes — invoked by @linter-driven-development…

원문 언어: 영어

pre-commit-review

ADVISORY pre-commit review that orchestrates four parallel rule-family hunters, an over-abstraction skeptic, and a comment critic against the diff. Spawns read-only agents (rule-hunter, overabstraction-skeptic, comment-critic); NEVER edits code. Invoked by…

원문 언어: 영어

lint-setup

Compares the Go linter setup of this repository with the LDD recommended setup, and agrees a tighter setup with the user before any edit. WHEN: the user asks to compare, align or set up the Go linter config with the LDD recommended setup, or runs…

원문 언어: 영어

linter-driven-development

META ORCHESTRATOR for any Go code change that should end in a commit (features, bug fixes, refactors). WHEN: User requests Go code work (implement, fix, add, refactor), mentions "@ldd"/"ldd", or runs a /go-ldd-* command in a Go project. Runs the five-phase…

원문 언어: 영어

lint-setup

Compares the linter setup of this repository with the LDD recommended setup, and agrees a tighter setup with the user before any edit. Applies to the languages that no installed language-specific linter-driven-development plugin covers. WHEN: the user asks to…

원문 언어: 영어

linter-driven-development

META ORCHESTRATOR for any code change that should end in a commit (features, bug fixes, refactors), when no language-specific linter-driven-development plugin covers the repository's language. WHEN: User requests code work (implement, fix, add, refactor),…

원문 언어: 영어

lint-setup

Compares the Python linter setup of this repository with the LDD recommended setup, and agrees a tighter setup with the user before any edit. WHEN: the user asks to compare, align or set up the Python linter config with the LDD recommended setup, or runs…

원문 언어: 영어

linter-driven-development

META ORCHESTRATOR for any Python code change that should end in a commit (features, bug fixes, refactors). WHEN: User requests Python code work (implement, fix, add, refactor), mentions "@ldd"/"ldd", or runs a /py-ldd-* command in a Python project. Runs the…

원문 언어: 영어

lint-setup

Compares the TypeScript + React linter setup of this repository with the LDD recommended setup, and agrees a tighter setup with the user before any edit. WHEN: the user asks to compare, align or set up the TypeScript + React linter config with the LDD…

원문 언어: 영어

linter-driven-development

META ORCHESTRATOR for any TypeScript + React code change that should end in a commit (features, bug fixes, refactors). WHEN: User requests TypeScript + React code work (implement, fix, add, refactor), mentions "@ldd"/"ldd", or runs a /tsr-ldd-* command in a…

원문 언어: 영어

refactoring

BACKWARD view over rules/ — routes linter and review failures to the rule whose Fix pattern owns the repair. Use when linter fails with complexity issues (cyclomatic, cognitive, maintainability) or when code feels hard to read/maintain. Also the skill for…

원문 언어: 영어

code-designing

FORWARD view over rules/ — domain type design and architectural planning for Go code BEFORE it exists. Use when planning new features, designing self-validating types, preventing primitive obsession, or when refactoring reveals need for new types. Dispatches…

원문 언어: 영어

refactoring

BACKWARD view over rules/ — routes linter and review failures to the rule whose Fix pattern owns the repair. Use when linter fails with complexity issues (cyclomatic, cognitive, maintainability) or when code feels hard to read/maintain. Also the skill for…

원문 언어: 영어

refactoring

BACKWARD view over rules/ — routes linter and review failures to the rule whose Fix pattern owns the repair. Use when linter fails with complexity issues (cyclomatic, cognitive, maintainability) or when code feels hard to read/maintain. Also the skill for…

원문 언어: 영어

code-designing

FORWARD view over rules/ — domain type design and architectural planning for Python code BEFORE it exists. Use when planning new features, designing self-validating types, preventing primitive obsession, or when refactoring reveals need for new types.…

원문 언어: 영어

refactoring

BACKWARD view over rules/ — routes linter and review failures to the rule whose Fix pattern owns the repair. Use when linter fails with complexity issues (cyclomatic, cognitive, maintainability) or when code feels hard to read/maintain. Also the skill for…

원문 언어: 영어

code-designing

FORWARD view over rules/ — domain type design and architectural planning for TypeScript + React code BEFORE it exists. Use when planning new features, designing self-validating types, preventing primitive obsession, or when refactoring reveals need for new…

원문 언어: 영어

refactoring

BACKWARD view over rules/ — routes linter and review failures to the rule whose Fix pattern owns the repair. Use when linter fails with complexity issues (cyclomatic, cognitive, maintainability) or when code feels hard to read/maintain. Also the skill for…

원문 언어: 영어

testing

Use when creating leaf types, after refactoring, during implementation, or when testing advice is needed. Automatically invoked to write tests for new types, or use as testing expert advisor. Covers the composition ladder from rung-0 unit tests to…

원문 언어: 영어

code-designing

FORWARD view over rules/ — domain type design and architectural planning for code BEFORE it exists, in whatever language the repository uses. Use when planning new features, designing self-validating types, preventing primitive obsession, or when refactoring…

원문 언어: 영어

testing

Use when creating leaf types, after refactoring, during implementation, or when testing advice is needed. Automatically invoked to write tests for new types, or use as testing expert advisor. Covers the composition ladder from rung-0 unit tests to…

원문 언어: 영어

testing

Use when creating leaf types, after refactoring, during implementation, or when testing advice is needed. Automatically invoked to write tests for new types, or use as testing expert advisor. Covers the composition ladder from rung-0 unit tests to…

원문 언어: 영어

testing

Use when creating leaf types, after refactoring, during implementation, or when testing advice is needed. Automatically invoked to write tests for new types, or use as testing expert advisor. Covers the composition ladder from rung-0 unit tests to…

원문 언어: 영어