html-artifact
Single HTML Artifact
Default Stack
Use this stack unless the user asks otherwise:
- One
.htmlfile with embedded<style>and<script>. - Custom CSS with CSS variables for theme, spacing, borders, and status colors.
- Vanilla JavaScript for static pages and simple interactions.
- Alpine.js from CDN when stateful UI would otherwise require repetitive DOM code.
- Optional CDN libraries only when they clearly reduce complexity: Chart.js for charts, Mermaid for diagrams, highlight.js for code, KaTeX for math.
Avoid build tools, package managers, JSX transpilers, large component libraries, and app frameworks unless the artifact is truly a mini-app or the user requests them.
Workflow
More from vaayne/agent-kit
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving functionality. Triggers on "simplify this code", "clean up", "refactor for readability", "make this cleaner", or after implementing features when code polish is needed.
15mcp-jetbrains-ide
Control JetBrains IDE (IntelliJ, WebStorm, PyCharm) via MCP. Use when manipulating IDE files, running configurations, searching code, or performing refactoring. Triggers on "open in IDE", "run configuration", "refactor code", "IDE search", "JetBrains".
10web-fetch
Fetch and extract clean content from URLs using Jina Reader API. Use when users need to read webpage content, extract article text, or fetch URL content for analysis. Triggers on "fetch this page", "read this URL", "extract content from", "get the content of", "what does this page say".
10changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
9ui-skills
Opinionated constraints for building better interfaces with agents.
7specs-dev
Plan-first development workflow with review gates. Use when implementing features, refactoring, or any task requiring structured planning, iterative implementation with reviews, and clean commits. Triggers on requests like "implement feature X", "plan and build", "spec-driven development", or when user wants disciplined, reviewed code changes.
3