vellum-editorial
SolidScaffold editorial documentation sites with the Vellum design system — OKLCH palette, Bodoni Moda / Source Serif 4 / Inconsolata typography, warm or dark space theme, 35 semantic components (state cards, parity matrices, entity dossiers, stat stacks, utterance blocks, editorial notes, entity flows, fact blocks, sub-navigation, source lists, debugger panels, ring visualizations, phase timelines, glossaries, subject-intro, stat-bar, hero-image with lightbox, gallery/masonry grid, audio player with Web Audio API). Static HTML, zero build step. Use when building competitive intelligence pages, personal archives, internal documentation, roadmaps, or multi-page static sites that need a designed, non-generic aesthetic.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- tdimino
- Repository
- tdimino/claude-code-minoan
- Created
- 7 months ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
editorial
Use when building or styling a UI in the Editorial aesthetic — A magazine-grade design system that makes typography the hero, pairing structured grids with generous whitespace and confident headlines. For Claude Code, Cursor, and Codex.
scaffold-pagesmith-docs
Stand up a brand-new Pagesmith documentation site from nothing — @pagesmith/docs wired to diagramkit, sample content, package skills installed, ending on a running preview. Triggers on "scaffold / bootstrap / stand up / start / create a new docs site", "new Pagesmith docs from scratch", "set up a docs site with diagrams". Writes to disk and runs local tooling (npm install, skills install, site build, dev server) — it configures a deploy target but NEVER deploys, pushes, or opens a PR; it prints the deploy command for a human to run. Confirms before touching an existing pagesmith.config. This is the greenfield counterpart to /adk:pagesmith (use that for an EXISTING site) and hands diagram-only work to /adk:diagramkit. It restates no package config schema, no engine flags, no palette — every version-sensitive authoring detail is delegated to the consumer's installed skills under node_modules.
dark-terminal-doc
Use when the user wants a polished, shareable single-file HTML technical document with a dark developer / terminal aesthetic — including comparison tables (A vs B), reference sheets, cheatsheets, changelogs, release notes, feature breakdowns, and API docs. Trigger phrases: "make a comparison table", "write a reference doc", "create a feature breakdown", "styled HTML doc", "dark terminal doc", "developer-facing HTML", "comparison cheatsheet", "technical reference page", "release notes HTML", "offline HTML doc", "single-file HTML page", "API cheatsheet", "git cheatsheet", "vs comparison".