strict-validation-setuplisted

One-shot bootstrap of strict-mode tooling per ecosystem plus per-task GOALS.md scaffolding so an agentic loop can self-verify. Writes typechecker/linter/schema-validator config for TS (strict + noUncheckedIndexedAccess + exactOptionalPropertyTypes), Python (Pyright strict, Ruff strict), Rust (Clippy deny-correctness), Go (golangci-lint with staticcheck), OCaml (dune --release); establishes `.agent-tasks/<id>/GOALS.md` per-task convention distinct from project-stable AGENTS.md. C++/Java/Kotlin and framework specifics (Spring Boot, Nest, React-strict) are out of scope. Trigger on new project bootstrap, agentic-task setup, "make this self-verifying", "set the loop's goal", "scaffold goals for this issue". Pairs with `llm-self-loop` runtime.
OutlineDriven/odin-claude-plugin · ★ 27 · AI & Automation · score 85

Install: claude install-skill OutlineDriven/odin-claude-plugin

The skill ships two distinct concerns split by *temporal phase*: - **Project-stable** — strict-mode tooling config + AGENTS.md authoring (defer the AGENTS.md content to `init`; this skill only ensures it exists and references the per-task pattern). - **Task-ephemeral** — `.agent-tasks/<task-id>/GOALS.md` per task plus failing-test scaffolding co-located with it. These never mix. Task goals never go into AGENTS.md (would leak as project policy). Project invariants never go into per-task GOALS.md (would duplicate per task and drift). ## Modality differentiation | Skill | Owns | | --------------------------- | -------------------------------------------------------------------------------- | | **`strict-validation-setup`** | Strict-mode tooling configs + per-task `GOALS.md` convention (this file) | | `init` | AGENTS.md authoring (project-stable) — defer to it for content | | `test-driven` | TDD discipline (RED → GREEN → REFACTOR) — defer for test-writing methodology | | `type-driven` | Refined-type / typestate specs — defer for type-system invariants | | `design-by-contract` | Pre/post conditions, runtime contracts — defer for assertion patterns | | `validation-first` | State-machine specs (typestate / FSM / actor) — defer for FSM modeling | | `tests-adversa