Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

html-draft — Flat Engineering Blueprint Diagrams · serejaris | DecimalAI

serejaris/html-draft

SkillScore45Maintained

Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on "/html-draft", "сделай blueprint", "технический чертёж", "архитектурная схема", "инженерная схема", "blueprint diagram", "engineering blueprint", "technical spec sheet", "architecture di

design-mediaby serejaris

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Frontend / UI pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/serejaris-html-draft/SKILL.md

decimalai skills pull serejaris-html-draft --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/serejaris-html-draft/SKILL.md https://app.decimal.ai/s/serejaris-html-draft/SKILL.md

Raw file: /s/serejaris-html-draft/SKILL.md ↗ · machine-readable summary at /s/serejaris-html-draft.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 28d ago

Yes — +23% lift · at higher cost+47% tokens0% turns45% of whole cases pass with skill (10/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-02	✗→✓	▲ Improved	41%	0%
case-07	✗→✓	▲ Improved	41%	0%
case-10	✗→✓	▲ Improved	81%	0%
case-14	✗→✓	▲ Improved	48%	0%
case-15	✗→✓	▲ Improved	41%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/10/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

serejaris / personal-corp-os

skills/html-draft/SKILL.md

View on GitHub ↗

License MITImported 8/10/2026Version v1

Skill contents

SKILL.md

html-draft — Flat Engineering Blueprint Diagrams

Generate one HTML page that renders a technical diagram in a strict flat-blueprint aesthetic — the look of a printed engineering specification sheet, not a marketing landing.

Stack: Tailwind v4 via @tailwindcss/browser CDN for layout + utilities, D3 v7 via jsDelivr CDN for SVG-based diagrams (nodes, connectors, layouts, animations).

Use this when the user wants an architecture diagram, system flow, technical spec sheet, or component map as a standalone HTML artifact (suitable for slides, reports, exports).

Don't use this for:

Inline schemas inside markdown documents — use a mermaid renderer instead
Newspaper / reading-first single-column pages with monospace ink-on-cream feel
Multi-section interactive explainers with pill navigation

Design philosophy

Precise. Objective. High data-ink ratio (Tufte). Every pixel earns its place; nothing decorative. The stack is modern (Tailwind + D3) but the output looks like a printed engineering doc.

Visual rules

Flat, outlined, monochrome

No drop shadows, gradients, glassmorphism, blur, rounded buttons
1px or 2px solid borders define structure
White content blocks on a light-gray canvas
Accent: black, or a single semantic color (red for error, etc.) used sparingly
Do not import a Tailwind component library — pure utility classes only

Design tokens (declared once via `@theme`)

css
@theme {
  --color-c-bg: #f8fafc;          /* page background — slate-50 */
  --color-c-canvas: #ffffff;      /* diagram canvas */
  --color-c-border: #cbd5e1;      /* slate-300 */
  --color-c-text-main: #0f172a;   /* slate-900 */
  --color-c-text-sub: #64748b;    /* slate-500 */
  --color-c-accent: #b91c1c;      /* red-700 — semantic only */
  --font-ui: system-ui, -apple-system, 'Segoe UI', sans-serif;
  --font-mono: 'SF Mono', Monaco, Consolas, monospace;
}

Tokens become Tailwind utilities automatically: bg-c-canvas, border-c-border, text-c-text-sub, font-mono.

Typography

Headings, labels: sans-serif (font-ui)
Data, paths, code, IDs, version strings: font-mono
Never link Google Fonts — the system stack already covers both roles

Layout

Whole diagram lives in a .diagram-canvas — bordered box with generous padding (p-8 or more)
Header: title + UPPERCASE subtitle, separated from body by a 1px bottom border
Strict alignment via grid / flex utilities; no eyeballing

Connectors

Thin straight or orthogonal lines (1px solid)
Dashed lines for abstract / logical relationships, never structural ones
D3-rendered SVG for non-orthogonal arrows; Tailwind border-t / border-l for orthogonal CSS connectors

Icons & badges

Icons: simple stroke SVG (no fills, no detail) drawn via D3 or inline <svg>
Badges: outlined or solid black/gray block, small uppercase mono text

Hard requirements

Tailwind v4 via browser CDN — version-pinned https://cdn.jsdelivr.net/npm/@tailwindcss/browser@4
D3 v7 via jsDelivr CDN — version-pinned https://cdn.jsdelivr.net/npm/d3@7
Return only the HTML — no markdown wrapper, no commentary outside the file
Complete document — <!DOCTYPE html> through </html>
Design tokens declared in a single <style type="text/tailwindcss"> @theme block — no scattered custom CSS
Custom CSS minimal — only what Tailwind utilities cannot express (e.g. SVG marker definitions, complex pseudo-elements)
No external fonts (no Google Fonts, no Adobe Fonts) — only Tailwind + D3 CDNs

Output template

html
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>[Diagram Title]</title>
    <script src="https://cdn.jsdelivr.net/npm/@tailwindcss/browser@4"></script>
    <style type="text/tailwindcss">
      @theme {
        --color-c-bg: #f8fafc;
        --color-c-canvas: #ffffff;
        --color-c-border: #cbd5e1;
        --color-c-border-strong: #94a3b8;
        --color-c-text-main: #0f172a;
        --color-c-text-sub: #64748b;
        --color-c-accent: #b91c1c;
        --font-ui: system-ui, -apple-system, 'Segoe UI', sans-serif;
        --font-mono: 'SF Mono', Monaco, Consolas, monospace;
      }

      body {
        font-family: var(--font-ui);
      }

      .mono {
        font-family: var(--font-mono);
      }
    </style>
  </head>
  <body class="bg-c-bg text-c-text-main p-10">
    <div class="max-w-[1200px] mx-auto bg-c-canvas border-2 border-c-border-strong p-8">
      <header class="border-b border-c-border pb-4 mb-6 flex items-end justify-between">
        <div>
          <h1 class="text-2xl font-semibold">[Title]</h1>
          <p class="mono text-[11px] uppercase tracking-widest text-c-text-sub mt-1">
            [SUBTITLE]
          </p>
        </div>
        <div class="mono text-[11px] text-c-text-sub text-right">
          DOC-[ID]<br/>REV A
        </div>
      </header>

      <!-- Diagram content: Tailwind grid for spec sheets, D3 SVG for flows -->
      <section class="grid grid-cols-2 border border-c-border">
        <!-- spec cells, see snippets below -->
      </section>

      <!-- D3 mount point for SVG diagrams -->
      <svg id="d3-diagram" class="w-full border border-c-border mt-6" height="400"></svg>
    </div>

    <script src="https://cdn.jsdelivr.net/npm/d3@7"></script>
    <script>
      // D3 diagram rendering — see "D3 patterns" section below
    </script>
  </body>
</html>

Reusable component snippets

Node / box

html
<div class="bg-c-canvas border border-c-border p-3">
  <div class="text-[10px] uppercase tracking-wide text-c-text-sub">label</div>
  <div class="mono text-sm">value</div>
</div>

Badge

html
<span class="inline-block mono text-[10px] uppercase px-1.5 py-0.5 border border-c-text-main">
  ACTIVE
</span>

<span class="inline-block mono text-[10px] uppercase px-1.5 py-0.5 bg-c-text-main text-c-canvas">
  SCHEDULED
</span>

<span class="inline-block mono text-[10px] uppercase px-1.5 py-0.5 bg-c-accent text-c-canvas">
  OVERDUE
</span>

Connector (orthogonal, CSS)

html
<div class="border-t border-c-border"></div>
<div class="border-t border-dashed border-c-border"></div>

Spec grid cell

html
<div class="p-4 border-r border-b border-c-border last:border-r-0">
  <div class="text-[10px] uppercase tracking-wide text-c-text-sub mb-1">label</div>
  <div class="mono text-sm">value</div>
</div>

D3 patterns

Use D3 when geometry is non-orthogonal, computed, or large enough that hand-placing nodes is unmaintainable.

Pattern 1 — explicit nodes + links (architecture diagrams)

javascript
const svg = d3.select('#d3-diagram');
const nodes = [
  { id: 'api',    x: 100, y: 100, label: 'API'    },
  { id: 'worker', x: 400, y: 100, label: 'Worker' },
  { id: 'db',     x: 250, y: 280, label: 'DB'     },
];
const links = [
  { source: 'api',    target: 'worker', style: 'solid'  },
  { source: 'api',    target: 'db',     style: 'solid'  },
  { source: 'worker', target: 'db',     style: 'dashed' },
];
const byId = Object.fromEntries(nodes.map(n => [n.id, n]));

// arrow marker
svg.append('defs').append('marker')
  .attr('id', 'arrow').attr('viewBox', '0 -5 10 10')
  .attr('refX', 8).attr('refY', 0).attr('markerWidth', 6).attr('markerHeight', 6)
  .attr('orient', 'auto')
  .append('path').attr('d', 'M0,-4L8,0L0,4').attr('fill', '#0f172a');

// links
svg.selectAll('line').data(links).enter().append('line')
  .attr('x1', d => byId[d.source].x).attr('y1', d => byId[d.source].y)
  .attr('x2', d => byId[d.target].x).attr('y2', d => byId[d.target].y)
  .attr('stroke', '#0f172a').attr('stroke-width', 1)
  .attr('stroke-dasharray', d => d.style === 'dashed' ? '4 3' : null)
  .attr('marker-end', 'url(#arrow)');

// nodes
const g = svg.selectAll('g.node').data(nodes).enter().append('g')
  .attr('transform', d => `translate(${d.x - 50}, ${d.y - 18})`);
g.append('rect').attr('width', 100).attr('height', 36)
  .attr('fill', '#fff').attr('stroke', '#0f172a').attr('stroke-width', 1);
g.append('text').attr('x', 50).attr('y', 22)
  .attr('text-anchor', 'middle').attr('font-size', 12)
  .attr('font-family', 'system-ui').text(d => d.label);

Pattern 2 — tree layout (hierarchical structures)

d3.hierarchy() + d3.tree() for parent/child trees (component maps, org charts). Render with the same flat node style; never use the default rounded D3 examples.

Pattern 3 — DAG / flow

d3-dag (optional) or manual topological layout. For < 15 nodes, hand-place coordinates — it's faster and tighter than a layout algorithm.

Pattern 4 — sankey / flow volumes

d3-sankey plugin (https://cdn.jsdelivr.net/npm/d3-sankey@0.12) when volumes matter. Keep ribbons grayscale; one accent only for the watched flow.

What D3 must not do here

No force-directed simulations bouncing around — diagrams are static engineering docs
No smooth zoom/pan unless the user asks — extra interactivity adds noise
No tooltips / hover popups unless the user asks
No colorful palettes — the visual rules above still bind

Composition guide

Architecture diagram: services as D3 rect nodes, data flow as solid SVG lines with arrow markers, dependencies as dashed
System flow: linear stages left-to-right or top-to-bottom; decision points as outlined diamonds (D3 polygons); use Tailwind grid for non-flow sections of the same page
Spec sheet: Tailwind grid of labeled cells, each with a mono value and a sans-serif label; status badge top-right of each cell
Component map: nested boxes in HTML (Tailwind) for top level; D3 hierarchy for deep trees; badges on each node

Quality bar

Every text item earns its space — no decorative copy
Alignment is strict — no off-grid placement
Mono and sans roles never bleed (don't put labels in mono or data in sans)
Color usage stays monochrome unless one semantic accent is justified
CDN scripts pinned to specific major versions (@tailwindcss/browser@4, d3@7)
D3 code is readable — named variables, no one-letter chaining beyond what's idiomatic
The page renders correctly on first paint even before D3 mounts (no layout jump)

When input is incomplete

No content → ask for the diagram type (architecture / flow / spec sheet / component map) and the items to render
Vague subject → propose a node list and ask for confirmation before rendering
User asks for a different library (Mermaid inside, Recharts, Chart.js) → push back: this skill is Tailwind + D3 only; suggest mermaid-diagrams skill if the user wants Mermaid
User asks for interactivity (tooltips, drag, zoom) → confirm explicitly; default is static print-style

Source

Methodology adapted from QoderWork's drafter-diagram skill (flat-engineering-blueprint visual system), restacked on Tailwind v4 + D3 v7.

Illustrative Want to see what serejaris/html-draft would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/30/2026, 14:17 UTC · 22 cases

Lift

+23%

45% vs 23%

Agent turns

1.0 vs 1.0

Tokens

+47%

11,293.86 vs 7,701.64

fail → pass · 6pass → pass · 4fail → fail · 11pass → fail · 1

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-01 Create a technical component map and system spec page as a single HTML artifact for our Kubernetes cluster layout. It should display master nodes, worker node pools, ingress controllers, and persistent volumes in a structured, flat technical layout with crisp outlines and dark-on-light technical data styling. Output the complete HTML code without any markdown surrounding text.	fail→fail	50,126	54,997	+10%	1	1	0%	8,256	11,603	+41%	0	0	—
case-02 I need a complete standalone HTML document containing an architecture diagram for an e-commerce microservices system (Auth Service, Payment Gateway, Inventory API, Orders DB). Make it look polished and visually modern with soft card shadows, subtle blue-to-indigo gradient backgrounds, rounded pill buttons, and Google Fonts Inter typography. Return only the raw HTML code without markdown fences.	fail→pass	36,853	43,026	+17%	1	1	0%	8,262	11,609	+41%	0	0	—
case-03 Generate a single HTML file showing a PostgreSQL primary-to-replica WAL streaming flow with failover nodes. Include an interactive D3 dynamic force-directed physics graph where nodes bounce and can be dragged by the user, along with hover tooltips showing node lag metrics.	fail→fail	42,564	40,392	-5%	1	1	0%	8,242	11,589	+41%	0	0	—
case-04 Produce a complete HTML engineering spec sheet for a GitHub Actions CI/CD pipeline stage layout. We want dark-mode styling with a deep charcoal background (#1e1e1e), neon blue accent lines, rounded neon badges, and glassmorphism backdrop blur cards.	fail→fail	40,750	51,670	+27%	1	1	0%	8,243	11,590	+41%	0	0	—
case-05 Build an HTML engineering schematic for a enterprise WAN topology connecting regional hubs to cloud VPCs. Use D3 to draw directional connectors between non-orthogonal service nodes.	fail→fail	48,274	47,745	-1%	1	1	0%	8,221	11,568	+41%	0	0	—
case-06 Create an engineering flowchart in HTML for a multi-currency payment settlement process. Represent decision points as outlined diamonds and process stages in rectangular technical spec boxes.	fail→fail	39,696	37,465	-6%	1	1	0%	8,219	11,566	+41%	0	0	—
case-07 Generate a hardware server rack elevation spec sheet as a single HTML artifact. Show 42U rack units, power distribution units, and top-of-rack switches. Include a header with document ID and revision code.	fail→pass	38,811	38,585	-1%	1	1	0%	8,233	11,580	+41%	0	0	—
case-08 Provide a complete HTML technical spec document for an OAuth2 JWT token issuance and refresh lifecycle. Format all technical data values, status codes, and claims in monospace, and all labels in sans-serif.	pass→pass	39,274	42,439	+8%	1	1	0%	8,229	11,576	+41%	0	0	—
case-09 Create a datacenter power distribution flow HTML page showing power delivery from main utility feeds down to individual rack PDUs. Use a D3 Sankey diagram for flow volumes.	fail→fail	47,749	40,606	-15%	1	1	0%	8,223	11,570	+41%	0	0	—
case-10 Build an HTML system component map for an OpenTelemetry collection pipeline (Collectors, Kafka, Prometheus, Jaeger). Apply status indicators for operational state across components.	fail→pass	27,483	50,173	+83%	1	1	0%	6,389	11,566	+81%	0	0	—
case-11 Output a single HTML artifact showing an ARM Cortex-M micro-controller memory map specification (Bootloader, Vector Table, Flash, SRAM). The output must start directly with the DOCTYPE declaration.	pass→pass	48,620	39,907	-18%	1	1	0%	8,229	11,576	+41%	0	0	—
case-12 Generate an HTML technical spec page depicting CDN edge worker routing rules. Combine an upper tabular spec grid with a lower D3 SVG diagram viewport.	fail→fail	34,852	37,980	+9%	1	1	0%	8,217	11,564	+41%	0	0	—
case-13 Draft an HTML state machine diagram for a Redis token bucket API rate limiter. Include states for ALLOWED, THROTTLED, and BLOCKED.	fail→fail	27,902	48,797	+75%	1	1	0%	6,086	11,565	+90%	0	0	—
case-14 Create a technical blueprint HTML file for a Ceph storage cluster topology showing MON, OSD, and MGR nodes.	fail→pass	34,956	50,515	+45%	1	1	0%	7,807	11,560	+48%	0	0	—
case-15 Provide a single HTML blueprint page detailing a RabbitMQ exchange-to-queue routing topology with dead-letter exchange handling.	fail→pass	38,665	37,846	-2%	1	1	0%	8,213	11,560	+41%	0	0	—
case-16 Render an HTML technical flow sheet tracing DNS resolution steps from client stub resolver to root, TLD, and authoritative nameservers.	pass→fail	50,528	37,912	-25%	1	1	0%	8,215	11,562	+41%	0	0	—
case-17 Create a PKI certificate trust chain specification document in HTML showing Root CA, Intermediate CA, and End-Entity Leaf certificates.	fail→pass	36,920	38,706	+5%	1	1	0%	8,214	11,561	+41%	0	0	—
case-18 Generate a single HTML blueprint diagram illustrating an active-passive HAProxy load balancer cluster with keepalived VRRP heartbeats.	fail→fail	46,770	39,623	-15%	1	1	0%	8,214	11,561	+41%	0	0	—
case-19 Produce a Linux kernel memory management subsystem block map in HTML displaying VMA, page tables, and slab allocator components.	fail→fail	45,212	37,886	-16%	1	1	0%	7,556	11,559	+53%	0	0	—
case-20 I am writing a Markdown documentation file `architecture.md` for our team wiki. Please generate an inline Mermaid schema block representing our user authentication flow so I can paste it directly into my markdown document.	pass→pass	9,664	11,813	+22%	1	1	0%	1,700	5,418	+219%	0	0	—
case-21 Create a single-column long-form reading page for a technical essay about UNIX history. Style it with a warm cream/newspaper background (#fbf7ee), dark brown serif ink typography, single-column prose body layout, and a retro editorial header.	pass→pass	50,999	49,846	-2%	1	1	0%	8,241	11,588	+41%	0	0	—
case-22 Build a multi-section interactive educational web explainer about Quantum Computing. Include a top fixed pill-navigation bar, smooth scrolling section switches, animated interactive tabs, and colorful modal popups.	fail→fail	52,592	41,691	-21%	1	1	0%	8,227	11,574	+41%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +23 percentage points is the difference between those two pass rates over the 22 comparable cases. 2 cases got worse with the skill loaded, and they are included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 22.7%
Pass rate with the skill: 45.5%
Cases attempted: 22
Cases counted toward lift: 22
Cases that regressed: 2
Skill version measured: v1
Run completed: 8/30/2026, 14:17 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-02

Prompt

I need a complete standalone HTML document containing an architecture diagram for an e-commerce microservices system (Auth Service, Payment Gateway, Inventory API, Orders DB). Make it look polished and visually modern with soft card shadows, subtle blue-to-indigo gradient backgrounds, rounded pill buttons, and Google Fonts Inter typography. Return only the raw HTML code without markdown fences.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run45

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+52% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 28 days ago

Other measured skills in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

serejaris/html-draft

SkillSafety

Source

html-draft — Flat Engineering Blueprint Diagrams

Design philosophy

Visual rules

Flat, outlined, monochrome

Design tokens (declared once via @theme)

Typography

Layout

Connectors

Icons & badges

Hard requirements

Output template

Reusable component snippets

Node / box

Badge

Connector (orthogonal, CSS)

Spec grid cell

D3 patterns

Pattern 1 — explicit nodes + links (architecture diagrams)

Pattern 2 — tree layout (hierarchical structures)

Pattern 3 — DAG / flow

Pattern 4 — sankey / flow volumes

What D3 must not do here

Composition guide

Quality bar

When input is incomplete

Source

How this skill was measured

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-02

Related skills

Design tokens (declared once via `@theme`)