Loading...
Loading...
Found 1,015 Skills
M3-compliant UI components (buttons, cards, forms, inputs). USE WHEN: creating components <300 lines, M3 migrations, Design System work. NOT FOR: complete screens, features with business logic (use flutter-developer). Always validate M3 components with MCP tools before creating custom. Examples: <example> Context: Need to migrate a button component to M3. user: "Migrate BukeerButton to Material Design 3" assistant: "I'll use flutter-ui-components to migrate BukeerButton to M3." <commentary>UI component migration is flutter-ui-components specialty.</commentary> </example> <example> Context: Create a new reusable form field. user: "Create a new date picker input component following M3" assistant: "I'll use flutter-ui-components to create the M3-compliant date picker." <commentary>Single UI components should be handled by flutter-ui-components.</commentary> </example>
Complete guide for building accessible, high-UX forms in modern stacks (React/Next.js, Tailwind, Zod). Includes specific patterns for clickable areas, range sliders, output-inspired design, and WCAG compliance.
Design System Governance Workflow for auditing, refactoring, and syncing enterprise design systems, design tokens, Figma variables, and developer handoff outputs.
Design clear, accessible data visualizations with appropriate chart selection and styling.
Use this skill when choosing color palettes, ensuring contrast compliance, implementing dark mode, or defining semantic color tokens. Triggers on color palette, contrast ratio, WCAG color, dark mode, color tokens, HSL, OKLCH, brand colors, color harmony, and any task requiring color system design or implementation.
Design de produto nivel Apple — sistemas visuais, UX flows, acessibilidade, linguagem visual proprietaria, design tokens, prototipagem e handoff. Cobre Figma, design systems, tipografia, cor,...
Use when making UI/UX decisions, building components, choosing colors, layouts, typography, or reviewing any visual design — enforces anti-slop standards against generic AI aesthetics
Use when designing UI components, creating component architectures, implementing responsive layouts, setting up design systems, or selecting state management solutions for frontend applications
freeCodeCamp's "Command-line Chic" UI design system and aesthetic guidelines. Apply these rules whenever building, styling, or reviewing any UI that should look and feel like a freeCodeCamp product — web apps, dashboards, landing pages, admin tools, component libraries, or themes. Use this skill when the user mentions freeCodeCamp styling, fCC design, "Command-line Chic", dark theme development for fCC, or asks for a UI that follows freeCodeCamp's visual identity. Also use when working on any freeCodeCamp repository, contributing to freeCodeCamp projects, or building tools and dashboards for freeCodeCamp staff, even if the user doesn't explicitly mention the design system.
Approachable, intuitive design with rounded elements, ample whitespace, and soft pastel color palettes.
Dark-themed cloud-platform aesthetic with modular grids, glass-like panels, and strong data hierarchy for productivity dashboards.
Soft, rounded 3D-like shapes mimicking malleable clay with playful, puffy elements and colorful surfaces.