goddtriffin

Use when contributing to the json-schema-rs crate (adding features, fixing bugs, understanding code layout, researching specs and competitors). For user-facing information (what the crate supports, how to use it), see the [README](README.md). For design and…

Sets up synthetic tests for jsonschemars codegen by creating a dummy Rust crate, generating Rust from JSON Schema definitions, analyzing compilation issues, and documenting findings in todo.txt with minimal viable examples. Use when running codegen analysis…

Performs a deep-dive analysis of a single JSON Schema to codegen library from a locally cloned repo and produces a structured research report. Use when analyzing a competitor library (path to clone provided), or when generating or updating a competitor…

Generates Git release descriptions for json-schema-rs by summarizing commits between tags. Use when the user asks for release notes, a release summary, what changed in a version, or to summarize a tag; or when preparing release text for a new version.

Use when writing, reviewing, or refactoring a reusable mock implementation of a dependency-injected interface/trait — one with both a production implementation and a mock implementation — or when deciding how a mock should seed responses, record calls, or…

Use when reviewing, refactoring, or standardizing a repo's agent-facing documentation — CLAUDE.md, README.md, vendored Claude skills (SKILL.md and reference files), or a skill-index table — or when deciding whether a skill has grown too broad and should be…

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".