Loading...
Loading...
Found 97 Skills
Builds accessible, production-ready frontend components. Use when building UI components, forms, modals, or any React/Vue/Svelte frontend work — before writing component code.
Set up Tailwind v4 with shadcn/ui using @theme inline pattern and CSS variable architecture — component composition, accessibility, React Hook Form. Use when initializing React projects with Tailwind v4, setting up shadcn/ui dark mode, composing components, implementing forms, fixing theme/CSS issues, or migrating from v3.
Guides senior front-end software engineering—TypeScript/React/Next.js architecture, component design, client and server rendering, state and data fetching, styling and design systems, accessibility (WCAG), performance (Core Web Vitals), testing, and senior-level UI code review. Use when building or refactoring complex UIs, designing component APIs, optimizing LCP/INP/CLS, implementing accessible interactions, integrating design tokens, or reviewing front-end PRs—not for backend APIs or databases (fullstack-software-engineer, senior-fullstack-developer), design-only critiques without implementation, CI/CD (devops), or cross-service system RFCs (senior-software-engineer). For implementing screens from design specs, component states, and visual QA, use ui-software-engineer. Deep perf investigations and load/RUM analysis: performance-engineer.
Vue Component Generator - Auto-activating skill for Frontend Development. Triggers on: vue component generator, vue component generator Part of the Frontend Development skill category.
Material Symbols v3 variable icon font system. Use when adding icons to buttons, navigation, status indicators, or any UI element. Provides 2,500+ icons with fill, weight, grade, and optical size axes. Integrates with project color tokens.
Create an accessible host-site visual theme and controls around Peekling without modifying character packs or runtime semantics. Use for page styling, not character skins.
Integrate Peekling into a website with the real browser runtime, validated pack, lifecycle cleanup, CSP/CORS guidance, accessibility, and a truthful two-line embed. Use for host installation, not pack authoring.
Audit a live URL with Real A11y via MCP (audit_page / inspect_page) or the CLI (real-a11y audit / tree / outline / tabs). Use when the user wants screen-reader fidelity findings, a semantic tree dump, heading outline, or tab order for a page — public, local, or staging.
Frontend engineering standards — component architecture, state, async, forms, accessibility, performance and TypeScript discipline. Detects the project's framework and loads only the matching guidance. TRIGGER — load BEFORE writing or editing frontend code, not after: any .tsx, .jsx, .vue, .svelte, or component/hook file is being created or edited; the prompt names a component, hook, prop, state, form, modal, route, page, React, Next, Solid, SolidStart, solid-js, signal, useState, useEffect, createSignal, createStore, createResource, createAsync, <For>, <Show>, store, context, a11y, or web vitals. Trigger on plain feature requests in a frontend repo — "add a button", "wire up this form", "make this load faster", "fix this rerender" — the user will not say "best practices"; the component file is the trigger. Load it even when another skill (tdd, impeccable, simplify) is already active. SKIP only for backend-only work with no UI file touched.
rem, px or relative units for each kind of value. Use when defining spacing and sizing tokens, control heights or media queries, or when a layout breaks under enlarged text.
Expert WCAG (Web Content Accessibility Guidelines) advisor covering WCAG 2.0, 2.1, and 2.2 — the W3C international accessibility standards. Use this skill whenever a user asks about WCAG success criteria, conformance levels (A/AA/AAA), accessibility audits, POUR principles, accessibility statements, ARIA patterns, colour contrast, keyboard accessibility, screen reader compatibility, mobile accessibility, cognitive accessibility, WCAG 2.2 new criteria, WCAG 3.0 preview, legal requirements referencing WCAG (EN 301 549, EAA, ADA, Section 508), or mapping WCAG to accessibility laws. Trigger for any web or digital content accessibility question — even if the user doesn't say "skill" or "WCAG".
Design, build, audit, redesign, study, and polish distinctive production-grade web interfaces without generic AI aesthetics. Use for landing pages, websites, product UI, dashboards, portfolios, frontend components, HTML/CSS/JS, React, Next.js, Vue, Svelte, design-system work, visual redesigns, UI critiques, accessibility reviews, responsive hardening, or requests to remove AI slop.