実装に着手する前に task 種別(feat / fix / refactor / chore / prototype / writing)を判定し、その種別に対応する agent chain(Plan → Phase 0 → TDD → Review 群 → Doc Sync → Verify)を plan に front-load するための判断表。Use when starting to implement a feature, fix a bug, refactor, or write a document and you need to decide which reviewers and gates apply …
Design and ship a companion JSON-LD knowledge graph (graph.jsonld) next to llms.txt for projects with stable concept-level structure. Encodes domain entities and relationships as schema.org triples for LLM citation. Use when project has matrix / hierarchy / phase-binding structure that prose alone leaves implicit, AND…
Extract a reusable pattern from the current session, judge it Save / Improve then Save / Absorb / Drop against a grounding checklist, and route every Save to a destination something actually reaches — absorbed into an existing skill / rule / doc section, or promoted to a real skill via skill-creator. Use when the user…
Design pattern for LLM-as-judge evaluators — binary checks as evidence, one named holistic verdict, no score aggregation. Use when designing or reviewing any LLM-based quality gate, evaluator, judge prompt, or verdict schema; when a judge's rubric scores fluctuate between runs; when you catch yourself asking an LLM…
A set of rules for making and reviewing claims based on measurements, thresholds, warnings, and experiment results. It focuses on what was observed, how much evidence exists, and whether a check is properly calibrated.
A Japanese-to-English and English-to-Japanese translation tool for human-readable writing such as essays, research documents, READMEs, and architecture decision records.
A writing tool for replies in public technical discussions, such as GitHub issues, pull requests, discussions, Hugging Face threads, and technical forums.
A writing skill for creating or improving a project’s README, the main page people see when they open a repository. It aims to make the project understandable to both people and AI tools.
Audit a project repo's non-code assets — tool configs, CI/GitHub workflows, runbooks, other docs — for assets whose consumer has vanished, and assign Keep/Update/Retire/Merge verdicts. Use when the user says "audit my repo assets", "which configs/workflows/runbooks are dead", "repo asset stocktake"…
A procedure for turning repeatable review checks into scripts, while leaving meaning and judgment to the reviewer. It can use a reviewer's checklist or past review records to find checks that a program can decide.
Scan installed skills to extract principles that belong in the always-loaded rules layer (environment-specific facts, wiring, and traps — not general principles the substrate already applies) and distill them into rules — append to, revise, or create rule files. Use when the user says "distill rules"…
Audit /.claude/rules (always-loaded behavioral rules) for residency cost, staleness, redundancy, broken See-skill pointers, and substrate absorption, assigning Keep/Improve/Update/Merge/Demote-to-skill/Dissolve/Retire verdicts. Use when the user says "audit my rules", "rules stocktake", "which rules should be demoted…
Search npm / PyPI / MCP / GitHub / existing skills before writing code for any new feature, integration, library selection, or utility. Use whenever the user says 'add X functionality', 'implement Y', 'set up Z', 'integrate W', asks 'what library should I use for...', 'is there a package/client/MCP for...', proposes a…
A Japanese-language workflow for examining past Claude Code session files and turning repeated user decisions into reusable skills, rules, or Architecture Decision Records.
Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines.
Scan the skill library for structural technical debt — dangling references where a SKILL.md names a script, bash file, agent, or sibling skill that does not exist on disk ("missing artifacts" debt), plus external skills whose directory is a symlink out of the skills root, where a local fix would be overwritten by the…
Audit installed Claude skills for quality and surface Keep/Improve/Update/Retire/Merge verdicts. Use when the user says "audit my skills", "stocktake", "review my skills", "which skills should I retire or merge", "do a quality pass over my skills", or "/skill-stocktake". NOT for creating or improving a single skill…
A workflow for starting a detached Claude Code Remote Control session for another project. The new session appears in the Claude mobile app and in Herdr's session list; detached means it runs independently of the current session.