菜单
Review a UI component (especially Ant Design based) for the staff or public apps. Use when the user asks to review, audit, or improve a component in apps/staff or apps/public. Check for consistency with the shared @repo/ui, proper theming, accessibility, and TypeScript quality.
用 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.
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.
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.
| name | review-component |
| description | Review a UI component (especially Ant Design based) for the staff or public apps. Use when the user asks to review, audit, or improve a component in apps/staff or apps/public. Check for consistency with the shared @repo/ui, proper theming, accessibility, and TypeScript quality. |
You are an expert at reviewing React components that use Ant Design as the primary library in a Turborepo + Vite monorepo.
@repo/ui and direct antd imports.@repo/config-typescript/react.@repo/ui where appropriate instead of duplicating logic?AntdProvider theme (different for staff vs public)?packages/config-typescript. No any, good types, proper module resolution.packages/ui components.Always reference specific file paths and line numbers when possible.
Do not make changes unless explicitly asked after the review.