paulrberg/agent-skills

html-playground

Use to build interactive single-file HTML playgrounds, explorers, or tools with visual controls, live preview, and prompt copy-out.

First seen Jul 13, 2026

Installation

$ npx skills add paulrberg/agent-skills --skill html-playground

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from paulrberg/agent-skills · top by installs.

npx skills add paulrberg/agent-skills

Browse all from paulrberg/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 70
License LICENSE.md
Default branch main
Open issues 4
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,504 B
  • docs SUMMARY.md 154 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 25 installs

SKILL.md

HTML Playground Builder

Build a self-contained interactive HTML explorer with controls, live preview, and a copyable natural-language prompt.

Workflow

  1. Infer the audience, decisions, and required states. Existing design systems and explicit requirements override these

defaults.

  1. Read exactly one closest template and adapt it:

- templates/design-playground.md - templates/data-explorer.md - templates/concept-map.md - templates/document-critique.md - templates/diff-review.md - templates/code-map.md

  1. Write one HTML file with inline CSS and JavaScript and no external runtime dependencies.
  2. Open it in a desktop browser, interact with every control and preset, and verify live preview, prompt output, copy

feedback, empty/error states, and keyboard usability. Fix rendered defects before completion.

Opinionated Defaults

Use these when product context does not indicate otherwise:

  • controls beside a live preview, with prompt output below;
  • a desktop-browser layout; do not implement or inspect responsive/mobile behavior unless requested;
  • a polished light theme, system UI font, monospace code/values, minimal chrome;
  • sensible non-empty initial state and 3–5 cohesive named presets;
  • one state object, one update path, and immediate preview/prompt refresh;
  • controls grouped by concern, with advanced controls collapsed;
  • prompt text that explains the desired outcome in natural language and mentions only non-default choices.

Invariants

  • No Apply button: relevant changes render immediately.
  • The prompt is actionable without seeing the playground and is not a raw state dump.
  • Copy has visible transient feedback and a usable fallback when the Clipboard API fails.
  • Standardize copy microcopy as Copy prompt, then Copied; on failure show Copy failed — select the prompt below.
  • Presets update controls, preview, and prompt consistently.
  • Do not add controls that do not affect either the preview or the generated prompt.

Completion requires the self-contained file and rendered, interactive inspection evidence. Finish with ### ✨ Playground ready, the linked artifact, and a compact artifact/controls/desktop-browser/copy-fallback table. Keep generated prompts free of decorative icons unless the requested content needs them.