OpenParable
Skip to content
← Back to skills

Static Web Artifacts Builder

Design
static-web-artifacts-builder

Static Web Artifacts Builder is an Agent Skill for design published in the Mathews-Tom/armory repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Build self-contained static HTML artifacts opened in a browser: interactive diagrams, dashboards, infographics. Pure HTML5+CSS3+inline SVG, zero toolchain. Triggers on: "interactive HTML", "open in browser", "HTML artifact", "visual dashboard", "HTML infographic". NOT for PNG/SVG output, use concept-to-image.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Mathews-Tom/armory/blob/HEAD/skills/static-web-artifacts-builder/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/static-web-artifacts-builder, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Static Web Artifacts Builder

To build high-density static infographic artifacts, follow these steps:

  1. Initialize the project scaffold using scripts/init-artifact.sh
  2. Develop your artifact by editing the generated HTML file(s)
  3. Validate and finalize using scripts/bundle-artifact.sh
  4. Display artifact to user

Stack: Vanilla HTML5 + CSS3 (Grid/Flexbox) + inline SVG — zero runtime dependencies

Design & Style Guidelines

VERY IMPORTANT: To avoid what is often referred to as "AI slop", avoid excessive centered layouts, purple gradients, uniform rounded corners, and Inter font.

Infographic-Specific Constraints

  • Density: Content-to-whitespace ratio ≥ 70:30. Maximize signal per pixel.
  • Geometry: Layered/nested containers, shaped regions (clip-path, border-radius variations), gradient fills, subtle box-shadows — not flat uniform boxes.
  • Iconography: Inline SVG icons for every major concept. No naked text labels.
  • Color: Purposeful palette (3-4 hues + neutrals), encoding meaning (category, flow direction, severity). Define as CSS custom properties.
  • Flows: Directional connectors with SVG arrowheads, curved paths, labeled edges. Architecture diagrams = layered tiers with bidirectional data flows, not flat node graphs.
  • Layout math: CSS Grid with explicit grid-template-columns/grid-template-rows fractional allocations. No auto-spacing defaults. Every margin/padding intentional.

Quick Start

Step 1: Initialize Project

Run the initialization script to create a new static project:

bash scripts/init-artifact.sh <project-name>
cd <project-name>

This creates a minimal scaffold with:

  • ✅ Template HTML with CSS custom properties (theming)
  • ✅ CSS Grid + Flexbox layout utilities (inline <style>)
  • ✅ Print-ready viewport meta configuration
  • ✅ No node_modules, no package.json, no build toolchain

Step 2: Develop Your Artifact

Edit the generated index.html directly. Each HTML file = one page = one clear message.

Key patterns:

  • Use CSS Grid grid-template-areas for named region layouts
  • Use fr units for proportional spatial allocation
  • Embed SVG icons inline (not as external references)
  • Use CSS custom properties (--color-primary, --color-accent, etc.) for palette cohesion
  • Use clip-path, border-radius, gradients, and box-shadow for visual depth

Step 3: Validate and Finalize

bash scripts/bundle-artifact.sh

This validates the artifact is fully self-contained:

  • Checks for zero external resource references (no CDN links, no external stylesheets/scripts)
  • Verifies inline SVG presence
  • Reports file size
  • Copies validated output to bundle.html

Step 4: Share Artifact with User

Share the validated HTML file in conversation with the user so they can view it as an artifact.


When to Use This Skill vs Other Visual Skills

TaskUse This SkillUse Instead
Rich infographic with multiple sections, high data densityYes—
Self-contained dashboard with interactive tabs or togglesYes—
Architecture diagram with bidirectional flows and layered tiersYesarchitecture-diagram for auto-generated from code
Simple concept illustration or icon-style imageNoconcept-to-image
Slide deck or multi-page presentationNohtml-presentation
Architecture diagram generated from existing codebaseNoarchitecture-diagram
Single-page visual where CSS Grid layout control is criticalYes—
Artifact must be screenshot-ready via PlaywrightYes (with caveat — see Limitations)—

Error Handling

ErrorCauseResolution
CDN link detected by bundle-artifact.shExternal stylesheet or script reference in HTMLInline all CSS and JS — no external URLs allowed in output
Content overflow / clipping in browserViewport too small or fixed heights with overflow:hiddenUse min-height instead of height; test at 1440px wide; use overflow: auto on scroll regions
Playwright screenshot cuts off contentPage height exceeds screenshot viewportSet page.setViewportSize to match content dimensions; use fullPage: true
bundle-artifact.sh reports missing inline SVGSVG loaded via <img src> or external refReplace with inline <svg> block directly in HTML
File size too large to share as artifactEmbedded base64 images or verbose SVGOptimize SVG paths; avoid embedding raster images

Limitations

  • Browser required for screenshots: Rendering and Playwright-based screenshot capture require a browser runtime. The HTML file itself has no server-side dependency, but visual validation needs a browser.
  • No server-side rendering: Output is purely client-side. Dynamic data, API calls, or server-computed content are not supported.
  • No persistent state: The artifact has no backend. User interactions (form inputs, toggles) reset on page reload and cannot be saved.
  • File size guidance: Aim for under 500KB. Artifacts above 1MB may not render as inline conversation artifacts in some Claude interfaces.
  • Font availability: System fonts only (or inline base64-encoded web fonts). Do not reference Google Fonts or other external font CDNs.
  • Print fidelity: CSS print media queries are supported but browser print rendering varies. Test @media print explicitly if print output is a requirement.