Loading...
Loading...
Found 44 Skills
Skill for implementing actual UI and integrating with APIs. Covers frontend-backend integration, state management, and API client architecture. Use proactively when user needs to connect frontend with backend APIs. Triggers: UI implementation, API integration, state management, UI 구현, API連携, 状态管理, implementación UI, integración API, gestión de estado, implémentation UI, intégration API, gestion d'état, UI-Implementierung, API-Integration, Zustandsverwaltung, implementazione UI, integrazione API, gestione dello stato Do NOT use for: mockup creation, backend-only development, or design system setup.
Builds, fixes, styles, and composes UI with the Gravity UI design system — the React ecosystem of @gravity-ui/* packages (uikit, charts, table, navigation, date-components, icons, and more). Routes to the correct package when look-alikes exist, applies theming and required setup, and prevents invented component APIs. Applies when working with @gravity-ui imports, uikit, ThemeProvider, --g- CSS tokens, or any prompt (EN or RU) mentioning gravity-ui, гравити, дизайн-система, компоненты, дашборд, таблица, график, or форма.
[廃止] このプロジェクトのUI実装には ppt-trans-design を使うこと。 ppt-trans-design が MD3 トークンを内部基盤として含んでいるため、 別途このスキルを使う必要はない。MD3 の実装パターン参照が必要な場合は ppt-trans-design/references/md3-patterns.md を参照。
implement or refine production frontend code with maintainable structure, responsive behavior, accessibility coverage, and clear alignment to the intended user experience.
Build or repair game inventory, loot, equipment, tooltips, drag-and-drop, persistence, and progression systems. Use for item schemas, pickup flows, stack rules, equipment slots, atomic swaps, save migration, and no-loss regression testing.
Recreate websites, application screens, components, dashboards, landing pages, and responsive interfaces from attached screenshots or visual references as accurate, maintainable frontend code. Use when implementing a supplied screenshot, matching an existing UI image, converting mockups into code, rebuilding multiple screens, or correcting a coded page whose rendering differs from a reference. Inspect each image and intelligently infer whether it represents desktop web, tablet, or mobile, then implement and verify the appropriate responsive mode. Supports existing and new projects, any suitable frontend stack, responsive inference, asset matching, accessibility, interaction reconstruction, and visual comparison.
Build, redesign, or visually refine product interfaces using project evidence, real content, functional states, and deliberate composition. Use for implementation work on websites, apps, dashboards, landing pages, or component systems. Do not use for read-only audits or logic-only changes.
Use for "/build-figma", a figma.com/design URL with node-id, or "implement this Figma" into a web, desktop, or shared UI. Orchestrates Figma MCP intake, maps nodes to the repo's own design system, then a verify-this visual judge. Do not paste Figma Tailwind.