メニュー
Add a new Ant Design based component or page feature to the staff or public Vite apps, or extend the shared @repo/ui library. Use when the user wants to introduce new UI elements using antd as the primary library.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implement a new feature or component following the conventions of this monorepo. Use when the user asks to build something new in the staff/public UIs, shared packages, or api. Strongly prefer using Ant Design for UI work and the shared @repo/ui library.
Scaffold a new Vite + React + TypeScript app in this Turborepo (e.g. a third UI besides staff and public). Use when the user wants to add another frontend that will also connect to the shared api backend.
Create a new reusable UI component or page feature in one of the Vite UIs (staff or public), or extend the shared @repo/ui library. Use when the user wants to add a new button, form, page section, or feature using Ant Design as the primary library.
Guide for building React applications with Apollo Client in the staff and public Vite apps. Use when: (1) setting up or configuring Apollo Client in apps/staff or apps/public, (2) writing GraphQL queries or mutations with hooks (useQuery, useMutation), (3) configuring caching, cache policies, or optimistic UI, (4) managing local state or error handling in the UIs that connect to the shared apps/api backend, (5) troubleshooting Apollo Client errors, performance, or integration with Ant Design components. Always coordinate with the backend schema in apps/api and use the shared @repo/ui + AntdProvider theming. Prefer patterns that work for both staff (internal) and public (customer-facing) experiences.
Guide for writing Apollo Connectors schemas to integrate REST APIs into GraphQL. Use this skill when: (1) connecting REST services to the GraphQL backend in apps/api, (2) using @source and @connect directives, (3) implementing entity resolvers with batching from external APIs. In this monorepo, use to extend the Hono/Apollo API without duplicating logic. The staff/public UIs can then query unified data. Coordinate with graphql-schema, update-graphql, apollo-server. Test via portless https://api.localhost/graphql.
Guide for authoring Apollo Federation subgraph schemas with entities, sharing, and cross-subgraph resolution. Use this skill when: (1) creating or evolving federated schemas for the backend (future split of apps/api or new subgraphs), (2) defining entities with @key, (3) using @shareable, @external, @requires, @provides, @override, (4) troubleshooting composition errors. In this monorepo, start with the single server in apps/api but prepare for federation. Coordinate with graphql-schema, update-graphql, rover. The UIs in staff/public would query the supergraph.
| name | add-antd-component |
| description | Add a new Ant Design based component or page feature to the staff or public Vite apps, or extend the shared @repo/ui library. Use when the user wants to introduce new UI elements using antd as the primary library. |
Follow this workflow when adding UI components that use Ant Design (antd) v5+.
Determine scope
apps/staff, apps/public, or a shared component in packages/ui?AntdProvider (staff often blue primary, public green in examples).Explore existing patterns
packages/ui/src/ (especially antd-provider.tsx).agents/skills/add-ui-component.md and the Grok-native add-ui-component skill for general guidance.Design
ConfigProvider theme tokens where possible.packages/ui/src/ and export it.Implementation
.tsx files.@repo/config-typescript/react).apps/api GraphQL backend).Polish
biome check . --write on the changed files.tsgo --noEmit (or the package's check-types).Review
review-component skill on the new work.Form, Input, Button, Card, Modal, Table, Select, etc. as primary building blocks.theme prop on ConfigProvider / AntdProvider for differentiation between staff and public.@ant-design/icons.agents/skills/.