worldclass-frontend

Implements and verifies accessible, responsive frontend interfaces against existing design systems.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/sabiscore/the-yap-engine --skill worldclass-frontend-sabiscore
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worldclass-frontend
Source: https://github.com/sabiscore/the-yap-engine/tree/main/.agents/skills/worldclass-frontend
Command: npx skills add https://github.com/sabiscore/the-yap-engine --skill worldclass-frontend-sabiscore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend work often stops at a component inventory with unverified states, broken responsiveness, and unchecked accessibility. This Skill enforces a complete audit-to-verification workflow so interfaces ship with all states implemented and evidence-backed quality checks. ## Core Features & Use Cases - Structured Design Workflow: Audits the current UI, writes an internal design brief, builds a coherent page composition, and extends existing tokens and primitives. - Complete State Coverage: Implements loading, empty, error, offline, unauthorized, disabled, pending, and success states rather than only the happy path. - Verification with Evidence: Checks accessibility, captures responsive layouts at 375/768/1024/1440 widths via Playwright, profiles performance, and runs lint, typecheck, tests, and production builds. - Use Case: Ask the agent to rebuild a product landing page; it audits hierarchy and tokens, implements the page with real content, verifies keyboard navigation and contrast, captures screenshots at four breakpoints, and reports files changed plus remaining risks. ## Quick Start Redesign the dashboard page using the worldclass-frontend workflow and verify it visually at mobile and desktop widths before reporting the results.

Frequently Asked Questions about worldclass-frontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify frontend responsiveness across breakpoints?▼

Use Playwright or available browser tooling to capture or inspect layouts at 375x812, 768x1024, 1024x768, and 1440x900, plus one intermediate width. Check overflow, clipped text, sticky elements, overlay bounds, touch usability, and navigation reflow.

How to audit a web page for accessibility issues?▼

Check semantic structure, heading order, keyboard navigation, focus visibility, labels, dialog behavior, announcements, contrast, target size, zoom, and reduced motion. Correct the issues found rather than only documenting them.

What UI states should a production frontend implement?▼

Implement and verify loading, empty, filtered empty, error, offline where applicable, unauthorized, disabled, pending, success, and partial data states. Covering only the success path leaves real user scenarios broken.

Does this workflow require an existing design system?▼

It uses the existing brand, tokens, and components gathered from the repository unless a redesign is explicitly requested. It extends semantic tokens, primitives, and typography and spacing scales rather than inventing a parallel system.

Why does frontend performance verification matter before shipping?▼

Unchecked request waterfalls, oversized images, font loading, heavy dependencies, and layout shifts degrade real user experience. The workflow prefers removing work over masking it with memoization and inspects the console after production builds.