Claude Skills by AHepi

Rules for writing, editing, and retiring skill and workflow files for LLM agents. Use when creating a SKILL.md or workflow document, reviewing one, adding a rule after an incident, or deciding whether a skill should exist at all.

Entry point for any DeepReason problem. Routes work to exactly one subskill at a time and enforces the scope contract. Use when asked to manage, diagnose, or fix anything in DeepReason.

Question discipline for working DeepReason - route every question to the cheapest authority (record, then framework, then operator), translate the operator's shorthand into typed obligations, and frame uncertainty as falsifiable forks. Load whenever an operator message is ambiguous or short, whenever any workflow phase says "stop and ask", whenever evidence contradicts your expectation, and at the start of any session run by a model that has not worked this repo before.

Audit dimension - find broken code by running every committed verification instrument and tabling deltas against the recorded baselines. Invoked by dr-audit-orchestrator when broken.md is missing.

Audit dimension - find code that is no longer used, via a reference census over every top-level symbol, one package per invocation. Invoked by dr-audit-orchestrator when dead.md is missing or has pending package rows.

Audit dimension - find where documentation deviates from code, using the executable doc checks plus a staleness and unchecked-claims census. Invoked by dr-audit-orchestrator when docs-drift.md is missing.

Audit dimension - verify every ledgered operator design law is actually enforced somewhere in code or gates, so stated goals and shipped behavior cannot silently diverge. Invoked by dr-audit-orchestrator when goal-trace.md is missing.

Router for the code-audit family. Runs five read-only audit dimensions (broken, dead, docs-drift, spec-drift, goal-trace) over the repo and produces AUDIT_REPORT.md plus ready-to-send fix prompts. Use when the operator asks for an audit, a sweep, or "what is broken / unused / out of date". Findings only — fixes happen in later tranches.

Audit dimension - find where the code deviates from the spec series and where shipped surface is spec-silent, by a two-direction term census. Invoked by dr-audit-orchestrator when spec-drift.md is missing.

Record an operator's suggested change verbatim and split it into numbered requirements (REQUEST.md). First phase of every change tranche; no interpretation, no code reading.

Entry point for implementing an operator-suggested change to DeepReason. Routes through capture, spec, plan, stepwise execution, validation, and delivery — one phase at a time, with a verbatim request ledger nothing may drift from. Use when the operator says "add", "change", "make it", "I want", or suggests any modification.

Close a validated change tranche — final commit and push, requirement-by-requirement reconciliation against the operator's verbatim words, and the delivery report (DELIVERY.md). Use only after VALIDATION.md says PASS.

Locate the cause of a DeepReason defect from the typed record, not from code reading. Produces DIAGNOSIS.md naming one primary cause with evidence pointers. Use only after GOAL.md exists.

The driving manual for DeepReason - how to run the harness properly (session preflight, the public CLI lifecycle, live-run ladders) and where to look before modifying anything or when diagnosing a problem. An index over the owning authorities (CLAUDE.md, docs/map, the workflow skills), not a replacement for them. Load at the start of any session that will run, modify, or diagnose the harness, especially a first session in this repo.

Execute exactly one unchecked step from CHECKLIST.md, prove its done-criterion, record the output, and stop. The only skill in the change workflow allowed to modify the tree. Invoke repeatedly, once per step.

Apply an approved FIX.md to DeepReason with regression tests and the full gate. The only skill allowed to modify production code. Use after FIX.md passes its approval gate.

Convert an approved SPEC.md into an ordered, checkable step list (CHECKLIST.md) where each step has one done-criterion. Use after SPEC.md, and again (partial re-plan) after a validation failure.

Design the smallest correct DeepReason fix for a reproduced cause, as FIX.md. No code changes yet. Use after REPRO.md confirms the diagnosis.

Demonstrate a diagnosed DeepReason cause with the smallest offline artifact — a failing test or a minimal script against the committed record. Use after DIAGNOSIS.md, before any fix.

Turn a vague DeepReason problem statement into one bounded, falsifiable tranche goal (GOAL.md). Use at the start of every tranche, before any diagnosis or code reading.

Translate a captured request into a concrete, bounded change specification (SPEC.md) with per-requirement acceptance checks and recorded assumptions. Use after REQUEST.md exists or gains amendments.

Prove the completed change against every acceptance check in SPEC.md and the full DeepReason gate, producing VALIDATION.md. Use when every CHECKLIST.md step is checked. Validates only; never patches.

Prove a DeepReason fix against its GOAL.md success criterion, optionally with one guarded live run, and record the honest outcome in VERIFY.md. Use after dr-implement-fix.

Orchestrate a Steven Pinker-grounded workflow for teaching, explanatory writing, or material that must do both. Use when the user explicitly asks for a Pinker approach, invokes this skill, asks how Pinker's work bears on teaching or writing, or needs one coherent workflow that first secures understanding and then improves prose. Do not use merely to imitate Pinker's personal voice or to import his political and historical views.

Design, deliver, or audit explanations and lessons with a Pinker-informed focus on phenomena, the curse of knowledge, concrete models, active reasoning, feedback, and revision. Use when the user explicitly requests Pinker's approach to teaching, invokes this skill, wants a difficult idea explained to a specified audience, or asks for a lesson, tutoring sequence, course segment, or teaching audit grounded in his work. Describe this as Pinker-informed teaching, not as a validated pedagogy creat...

Draft, revise, teach, or audit expository prose using Pinker's cognitive approach to style: classic presentation, reader modeling, curse-of-knowledge repair, coherent information order, deliberate syntax, evidence-based usage, feedback, and revision. Use when the user explicitly requests Pinker's writing approach, invokes this skill, or asks for a Pinker-grounded draft, edit, style lesson, or prose diagnosis. Apply principles without imitating Steven Pinker's distinctive voice.