Loading...
Loading...
Found 943 Skills
Implement animations using the Motion library. Use when adding motion, transitions, gestures, scroll effects, or interactive animations to components. Triggered by implementation requests, not conceptual discussions.
Internal skill. Use cc10x-router for all development tasks.
Establish design review gates with criteria, checklists, and approval workflows.
Semi-automated design quality review for Flows apps. Runs concrete repo probes (grep, lint, build) to propose a draft 1–5 score for each of the official 10 quality-guidelines questions from docs.cognite.com/cdf/flows/guides/quality-guidelines, then asks the user to confirm or override each score. Still requires the user to walk their tasks end-to-end in the running app (Step 2) since navigation and clickability feel cannot be measured statically. Writes reviews/design-review/feedback-round-<N>/design-review-report.md with an overall average and prioritized fix lists. Use when the user asks to run a Flows design review, run the design quality assessment, or run flows-design-review. Must be run AFTER flows-code-review reaches 0 Must Fix and BEFORE flows-external-app-submit.
Chrome Extensions UX/UI design and implementation guidelines for popups, side panels, content scripts, and options pages. Triggers on tasks involving browser extension UI, manifest v3, chrome APIs.
Front's UI design system. Use when building interfaces inspired by Front's aesthetic - light mode, Inter font, 4px grid.
Deel's UI design system. Use when building interfaces inspired by Deel's aesthetic - light mode, Inter font, 4px grid.
Build production-grade, accessible, and tested component libraries with Storybook, Chromatic, and design tokens
查看用户界面代码以了解Web界面指南合规性。在被要求“查看我的用户界面”、“检查辅助功能”、“审核设计”、“查看用户体验”或“根据最佳做法检查我的网站”时使用。
Design system and token management. Use for managing design tokens, colors, typography, and maintaining design consistency.
Design and implement distinctive, production-ready frontend interfaces for the web. Use when building, redesigning, or polishing components, pages, dashboards, landing pages, design systems, or UI code (HTML/CSS/JS/TS/React/Vue/Tailwind) that must be beautiful, usable, responsive, accessible, and feel deliberately designed rather than generic.
Implement integration-ready UI code from a Figma selection or a provided nodeId using TemPad Dev MCP as the only source of design evidence (code snapshot, structure, screenshot, assets, tokens, codegen config). Detect the target repo stack and conventions first, then translate TemPad Dev’s Tailwind-like JSX/Vue IR into project-native code without adding new dependencies. Never guess key styles or measurements; avoid screenshot tuning loops. If required evidence is missing/contradictory or assets cannot be handled under repo policy, stop or ship a safe base with explicit warnings and omissions.