Loading...
Loading...
Found 779 Skills
Smart/Dumb component patterns, Standalone components, modern control flow (@if, @for), and OnPush strategy for Angular 17+.
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>
Internal skill. Use cc10x-router for all development tasks.
Develop SwiftUI applications for iOS/macOS. Use when writing SwiftUI views, managing state, or building Apple platform UIs.
Figma-driven Next.js development skill. Automatically triggered when users mention 'based on Figma', 'follow the design draft', provide Figma links or MCP data.
Evalúa y mejora la experiencia de usuario de formularios Aurora. Trigger: Cuando necesites evaluar UX, reordenar campos, o revisar el flujo de un formulario.
Design effective loading states, skeleton screens, and empty states that maintain user confidence. Use when content takes time to load, when showing progress, or handling empty data scenarios. Triggers on "loading state", "skeleton screen", "empty state", "spinner", "progress bar", "loading animation", "zero state".
Design System Governance Workflow for auditing, refactoring, and syncing enterprise design systems, design tokens, Figma variables, and developer handoff outputs.
Эксперт по design handoff. Используй для спецификаций дизайна, Figma annotations и developer handoff.
Use when someone asks to write, rewrite, review, or improve text that appears inside a product or interface. Examples: "review the UX copy", "is there a better way to phrase this", "rewrite this error message", "write copy for this screen/flow/page", reviewing button labels, improving CLI output messages, writing onboarding copy, settings descriptions, or confirmation dialogs. Trigger whenever the request involves wording shown to end users inside software — apps, web, CLI, email notifications, modals, tooltips, empty states, or alerts. Also trigger for vague requests like "review the UX" where interface copy review is implied. Do NOT trigger for content marketing, blog posts, app store listings, API docs, brand guides, cover letters, or interview questions — this is a technical writing skill for interface language.
Expert micro-interaction architect for mobile apps, web applications, and responsive websites. Use this skill when the user asks to add, build, fix, audit, or consult on micro-interactions, animations, transitions, motion design, gesture feedback, haptics, loading states, skeleton screens, pull-to-refresh, swipe actions, scroll animations, button states, form validation feedback, toast notifications, modals, dropdowns, toggles, progress indicators, shared element transitions, spring physics, easing curves, motion tokens, or any interaction that provides visual/haptic/auditory feedback to user actions. Triggers on: "micro-interaction", "animation", "transition", "motion", "easing", "spring", "gesture", "haptic", "feedback", "loading state", "skeleton", "shimmer", "pull to refresh", "swipe", "drag", "hover effect", "press state", "focus ring", "scroll animation", "parallax", "stagger", "orchestration", "reduced motion", "View Transitions", "layout animation", "shared element", "hero animation", "morphing", "Framer Motion", "GSAP", "Lottie", "Rive", "React Spring", "anime.js", or any request to make an interface "feel better", "feel alive", "feel snappy", "feel responsive", or "feel polished".
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