jamesbuckett
UserClaude Code skill for single-file HTML pages with disciplined design and Playwright validation.
Categories
Indexed Skills (3)
skill-style-guide
Build single-file HTML pages that follow James Buckett's personal style guide — light theme with dark-mode toggle, Noto Sans / Noto Sans Mono typography, Lucide icons inlined as SVG, a disciplined 4/8/12/16/24/32/48/64 spacing scale, exactly one accent color, personal branding links, and Playwright screenshot validation across mobile/tablet/desktop. Use this skill whenever the user asks for a landing page, marketing page, prototype, mockup, single-file HTML page, or to edit an existing index.html in this project, even when they don't explicitly mention the style guide. Skip only if the user explicitly wants a multi-file build (React, Vue, Next, etc.).
skill-build-educational-site
Build a single self-contained HTML explainer page on a technical or regulatory topic. ALWAYS trigger when the user wants a deliverable webpage that explains something — phrasings include "one-pager", "primer", "explainer", "teaching page", "deep-dive page", "self-contained webpage", "single HTML file on X", "page on Y to execs and engineers". Trigger even without "educational site" — "presenting Thursday on X, build me an HTML page", "deep-dive page on Y", "brief my team, make an html page on Z" all qualify. Strong on regulated/security topics (FAPI, PCI-DSS, DORA, SPIFFE, CALM, FIPS, SLSA, SBOM, AI Act, OAuth, zero-trust) but works for any technical concept. Skip ONLY for different artifacts (slide deck, Confluence, README, ADR, dashboard, multi-page docs site) or chat-only answers.
skill-improve-quality
Audit and improve the quality of a single-file HTML explainer page (typically `index.html`) in the current repo without changing its purpose. Use whenever the user wants to QA, audit, fact-check, polish, sharpen, review, critique, validate, tighten, or improve an explainer, primer, one-pager, landing page, deep-dive, or single-file HTML — even when they don't use the exact phrase "improve quality". Triggers include "check this page", "is this accurate", "review the prose", "polish this", "audit this index.html", "fact-check this", "is the content correct", "is this clear enough", "sharpen this writing", "tighten this page", "QA the page", "is this professional", "is this any good", and "/skill-improve-quality". Skip when there is no HTML file to audit, when the user wants new content written rather than checked, or when they want visual-only feedback.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.