web-design-builder_skill

This skill generates accessible, responsive HTML/JS web designs from descriptions, with automated verification and optional framework support.

31

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill rknall/claude-skills --skill web-design-builder

  • design-templates.md15.3 KB
  • README.md5.4 KB
  • SKILL.md17.4 KB

Overview

This skill creates and refactors production-ready HTML5/JavaScript web designs from a brief, specification, or existing code. It generates accessible, responsive layouts with modern patterns and optional framework choices (Vanilla, Tailwind, React, Vue, Alpine). The skill can automatically verify accessibility and functionality using Playwright MCP when available. Deliverables include a runnable mockup, separate production files on request, and a verification report when tests run.

How this skill works

I gather scope and technical preferences, then produce a complete mockup: semantic HTML, responsive CSS (mobile-first), and progressive JavaScript. I include accessibility features (WCAG AA baseline, ARIA landmarks, keyboard support) and can save files in a recommended project structure. If Playwright MCP is detected I run automated accessibility, keyboard, visual, functionality, and basic performance checks and generate a verification report. If Playwright MCP is not available I note that verification is skipped and provide setup instructions.

When to use it

  • Create a landing page, marketing site, or app mockup from a description
  • Refactor or improve existing HTML/CSS/JS for accessibility and responsiveness
  • Build component libraries, design systems, or UI prototypes
  • Generate accessible forms, modals, navigation, and interactive components
  • Verify design automatically with Playwright MCP when available

Best practices

  • Start mobile-first and keep layouts flexible with CSS Grid/Flexbox
  • Prefer semantic HTML and explicit ARIA landmarks for screen readers
  • Use CSS variables for theming and maintainable styles
  • Provide clear focus states and keyboard interactions for all controls
  • Split mockup (single-file) from production build (separate CSS/JS/assets)
  • Run automated accessibility checks and re-verify after fixes

Example use cases

  • Turn a product brief into a responsive landing page with CTA and form
  • Refactor an existing dashboard to improve accessibility and keyboard navigation
  • Produce a React component set with documentation and examples
  • Create a single-file prototype (index.html) for stakeholder review and screenshots
  • Run Playwright MCP checks and deliver a verification report listing fixes and next steps

FAQ

I will still generate the design but skip automated verification. I provide concise installation steps so you can enable verification later.

Which frameworks can you use?

I can produce Vanilla HTML/CSS/JS, Tailwind CSS, React, Vue, or Alpine.js depending on your preference and complexity needs.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
web-design-builder skill by rknall/claude-skills | VeilStrat