Plugin Claude Code
A suite of cross-referenced skills for end-to-end story writing and revision powered by markdown.
Plugin Claude Code
A suite of cross-referenced skills for end-to-end story writing and revision powered by markdown.
MCP server Claude CodeCodexCursor +2
MCP server for managing todos in markdown files. Runs locally from the @danjdewhurst/todo-md-mcp npm package.
Skill Claude CodeCodex
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
Skill Claude Code
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
Skill Claude Code
Explain a body of work plainly so a person actually understands it. Runs the how and why skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
Skill Claude Code
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
Skill Claude Code
Cut AI tells from any writing. Must always apply.
Skill Claude Code
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics…
Plugin Claude Code
Hetzner Cloud CLI plugin for Claude Code — skills, commands, and safety hooks.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: