style-guide plugins

by Wondel.ai

Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), Domain-Driven Design (Eric Evans), Working Effectively with Legacy Code (Michael Feathers), and Google's Developer Documentation Style Guide (technical-documentation)

by HashiCorp

Terraform code generation skills for Claude Code, including HCL generation, style guides, and testing.

by Alberto Leal

Extract and document writing styles from source texts into reusable style guides. Use when analyzing an author's voice, creating a style guide from a book or document, capturing writing patterns for replication, or building a writing style rubric.

by Alberto Leal

Write content using stored writing styles from the writing-styles/ collection. Use when the user wants to write in a specific voice, apply a stored style, list available writing styles, or evaluate text against a style rubric.

by riekelt

House-style technical writing: a core style and truth skill plus specialized skills for design docs, decisions, changelogs, runbooks, tracker issues, and prose review

by jabworks

Write code that matches the jabworks house style the first time — TypeScript, React/Next.js, formatting, import order, monorepo boundaries, naming, error handling, CSS/Tailwind.

by Alexander Kurganov

Engineering prose standard for everything an agent writes: user replies, prose, code comments, review comments, commit messages, change descriptions, error messages and agent instructions. Five layers — sentence structure, plain vocabulary, comment hygiene, artifact formats, slop pruning — each stated as a rule a reader can check rather than a preference. The core rules are one file, rules/prose-discipline.md, injected at session start by the hook in hooks/ on hosts that run plugin hooks, and loaded as an always-apply rule by hosts that read plugin rule files; the skill carries the protocol and the depth behind every rule, including the substitution table, the Conventional Comments labels and a calibration corpus. Code blocks, identifiers, commands, URLs and quoted text are never flagged, and established domain terms are kept. No credentials, no MCP servers, no settings files, and no checker script: enforcement is model judgement over rule texts a person can read and argue with.