additive-bias-defense
The default answer to "should we add this?" is no. The burden of proof is on the addition.
Additive Bias Defense
Note (#444): Frontmatter declares
provides.guidance, notprovides.contract. The scrutiny questions are consumed by partner skills (pensive:code-refinement,conserve:unbloat,imbue:scope-guard) that voluntarily embed them; no validator or hook in leyline enforces them directly. If a future contributor adds enforcement, restore thecontractlabel and link the validator path here.
The Problem
LLMs are additive by nature. They reinvent wheels, add unnecessary complexity, hallucinate issues and modify tests to justify them, and deviate from priorities. This contract provides a systemic defense.
More from athola/claude-night-market
project-planning
Turn a specification into a phased implementation plan with dependency ordering.
126code-quality-principles
KISS, YAGNI, and SOLID code quality principles for clean code, reducing complexity and preventing over-engineering.
94project-brainstorming
Guide project ideation via Socratic questioning to generate project briefs.
92doc-generator
Generate or remediate documentation with human-quality writing and style.
81rigorous-reasoning
Anti-sycophancy reasoning checklist.
79project-specification
Transform project briefs into testable specifications with user stories, acceptance criteria, and measurable outcomes.
78