Apply the "US Graphics aesthetic" — an engineering-documentation HTML design system: white paper sheet on gray, true-black ink, system-ui sans (mono only for code), hairline/dotted rules, bordered tables with gray header rows, tab-strip nav with a red active dot, blue links, amber primary + green "go" buttons, square corners, one flat shadow. Dense, flat, explicit — a technical spec sheet, not an editorial page. Use WHENEVER building or restyling a self-contained HTML page, spec sheet, changelog, status board, data table, catalog, README, one-pager, or prototype that should read like precise engineering documentation — even if the user doesn't name the system. Triggers: "make this look technical / like a spec sheet", "apply the US Graphics / usgraphics style", "clean technical documentation page", or any standalone HTML artifact you'd otherwise hand-roll ad-hoc CSS for in that register. Do NOT use for in-app product UI on its own component library, or for an airy editorial serif look (use claude-aesthetic ins
Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch or WebSearch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page. Do NOT use for URLs ending in .md — those are already markdown, use WebFetch directly.
Use this skill when reviewing, writing, or refactoring code for cleanliness and maintainability following Robert C. Martin's (Uncle Bob) Clean Code principles. Triggers on code review, refactoring, naming improvements, function decomposition, applying SOLID principles, writing clean tests with TDD, identifying code smells, or improving error handling. Covers Clean Code, SOLID, and test-driven development.