claude

ALWAYS invoke this skill when auditing ADRs for Python or after writing an ADR. NEVER implement from an unaudited ADR.

ALWAYS invoke this skill when auditing code for Python or after writing code. NEVER modify a spec to match code without auditing the code first.

ALWAYS invoke this skill when auditing tests for Python or after writing tests. NEVER use auditing-python for test code.

Python ADR conventions enforced across architect and auditor skills. Loaded by other skills, not invoked directly.

ALWAYS invoke this skill when auditing PDRs or after writing a PDR. NEVER audit PDRs without this skill.

ALWAYS invoke this skill when auditing test evidence quality, after writing tests for a spec node, or before closing an outcome.

ALWAYS invoke this skill when auditing ADRs for TypeScript or after writing an ADR. NEVER implement from an unaudited ADR.

ALWAYS invoke this skill when auditing code for TypeScript or after writing code. NEVER modify a spec to match code without auditing the code first.

ALWAYS invoke this skill when auditing tests for TypeScript or after writing tests. NEVER use auditing-typescript for test code.

ALWAYS invoke this skill when writing or fixing implementation code for TypeScript.

TypeScript ADR conventions enforced across architect and auditor skills. Loaded by other skills, not invoked directly.

ALWAYS invoke this skill before implementing any spec-tree work item. NEVER write code for a spec-tree node without this skill.

ALWAYS invoke this skill when setting up a new spec tree or when /authoring detects an empty spx/ directory. NEVER create a spec tree from scratch without this skill.

ALWAYS invoke this skill before any spec-tree work to load methodology. NEVER create, read, or modify spec tree files without loading this foundation first.

ALWAYS invoke this skill when creating, editing, or improving SKILL.md files. NEVER create or modify skills without this skill.

ALWAYS invoke this skill before writing tests or when learning the testing approach.

ALWAYS invoke this skill when writing ADRs for Python.

ALWAYS invoke this skill when writing or fixing implementation code for Python.

ALWAYS invoke this skill when writing or fixing tests for Python.

ALWAYS invoke this skill when reviewing, auditing, or checking spec file conformance. NEVER check spec conformance without this skill.

ALWAYS invoke this skill when adding, defining, or creating specs, decisions, or nodes. NEVER author spec tree artifacts without this skill.

ALWAYS invoke this skill when asking about status, progress, or what exists in the spec tree. NEVER work on any part of the spec tree without loading context through this skill first.

ALWAYS invoke this skill before writing tests or when learning the testing approach.

ALWAYS invoke this skill when writing ADRs for TypeScript.

ALWAYS invoke this skill when writing or fixing tests for TypeScript.

Python testing standards enforced across all skills. Loaded by other skills, not invoked directly.

Foundational test review methodology. Loaded by /auditing-python-tests and /auditing-typescript-tests, not invoked directly.

Python code standards enforced across all skills. Loaded by other skills, not invoked directly.

TypeScript code standards enforced across all skills. Loaded by other skills, not invoked directly.

ALWAYS invoke this skill when reviewing SystemVerilog or Verilog code for idiomatic style, synthesizability, or best practices. NEVER review SystemVerilog or Verilog without this skill.

ALWAYS invoke this skill when reviewing VHDL code for idiomatic style, synthesizability, or best practices. NEVER review VHDL without this skill.

ALWAYS invoke this skill when creating Excalidraw diagrams, visualizing workflows, architectures, or concepts. NEVER generate Excalidraw JSON without this skill.

ALWAYS invoke this skill when committing changes or when user says "commit". NEVER run git commit without this skill.

ALWAYS invoke this skill when reviewing, editing, or improving prose for quality. NEVER review prose without this skill.

Prose anti-patterns enforced across all skills. Loaded by other skills, not invoked directly.

ALWAYS invoke this skill when generating articles, documentation, blog posts, specs, or any long-form text. NEVER write long-form text without this skill.

ALWAYS invoke this skill when committing changes or when user says "commit". NEVER run git commit without this skill.

ALWAYS invoke this skill when breaking down, splitting, scoping, or structuring spec tree nodes. NEVER decompose specs without this skill.

ALWAYS invoke this skill when moving nodes, re-scoping content, or extracting shared enablers. NEVER restructure the spec tree without this skill.

ALWAYS invoke this skill when creating, editing, or configuring subagents. NEVER create subagents without this skill.