Results for “aspect-ratio”

Audit a component or page for accessibility issues and fix them

A rating component for collecting user feedback with customizable icons, colors, and half-star support in Naive UI. Ideal for product reviews, feedback forms, and rating systems.

Audits colour decisions on a screen for contrast ratios, palette coherence, semantic meaning, and accessibility, flagging deviations and recommending specific corrections.

Audit a component or page for accessibility issues and fix them

Aesthetic assessment and design scoring across 6 dimensions. Use for UI critique, design review, visual quality assessment, remix suggestions. Activate on "design critique", "aesthetic review", "UI assessment", "visual quality", "design score", "remix this design". NOT for implementation (use frontend-developer), accessibility-only audits (use color-contrast-auditor), or brand identity creation.

Audits and fixes responsive design issues across breakpoints, including fixed widths, missing media queries, non-responsive images, undersized touch targets, and horizontal scroll, with framework detection and verification at mobile, tablet, desktop, and wide viewports.

ScepticAgent UI and styles reference. Use whenever the user wants to change the side panel UI, modify highlight colours, update the markdown renderer, work with CSS architecture, add or change category colours, or understand how the sidepanel renders analysis output.

Radix UI unstyled accessible React components. Headless primitives. USE WHEN: user mentions "Radix", "Radix UI", "headless components", "unstyled primitives", asks about "accessible components", "Radix primitives" DO NOT USE FOR: shadcn/ui (use shadcn-ui skill), styled component libraries (Material-UI, Chakra), Vue/Svelte (use Headless UI)

Identify render hotspots, isolate expensive updates, and apply targeted React optimizations without changing UI behavior.

Audit a StyleSeed-based component or page for WCAG 2.2 AA issues and apply practical accessibility fixes where the code makes them safe.

Audit a component or page for accessibility issues and fix them

Review a built frontend against its chosen direction, catch drift back to generic AI defaults, enforce state coverage, ethical patterns, UX heuristics, and polish, and check contrast with APCA (not the legacy WCAG ratio). Produces specific, prioritized fixes — never vibes-based feedback. Works with pasted screenshots or Playwright MCP automated capture. Load when the user asks to review a UI, audit a design, check if a frontend looks generic or vibecoded, evaluate visual quality or polish, says "review this UI", "is this design good", "audit my frontend", "does this feel like [product]", "design QA", or when frontend-design routes here. Sub-skill of frontend-design.

Apply subtle gradient-border treatments for premium web surfaces. Use when cards, pricing panels, nav bars, modals, buttons, or hero surfaces need a refined edge highlight without a loud glow.

Audits components and pages for WCAG 2.2 AA accessibility issues and applies practical code fixes for touch targets, focus states, contrast, labels, and reduced motion.

Use when writing or editing a React component. Covers preferred patterns for functional components, prop types, and styling.

Audit frontend API calls against backend implementation for contract alignment and network shape. Use when "API audit", "FE-BE contract", or "review frontend API integration". Live 4xx/5xx reproduction → debug-fe-be-integration.

Select, pair, and implement typefaces for web projects with guidance on readability, CSS implementation, and performance optimization.