react-components
CoreAI Sandbox component usage: import boundaries, published CoreAI documentation, and local adapter inspection. USE WHEN: editing any `*.tsx` file, picking a component, or writing component imports.
- License 许可
- MIT
- 所属仓库
- github/replica
- 最近更新
- 2026-11-12
- Stars
- ★ 258
- Forks
- 30
01 前言 Front Matter
- name
- react-components
- description
- CoreAI Sandbox component usage: import boundaries, published CoreAI documentation, and local adapter inspection. USE WHEN: editing any `*.tsx` file, picking a component, or writing component imports.
03 SKILL.md 正文
CoreAI Sandbox Component Usage
Import Boundary
Import CoreAI components, styling APIs, and tokens directly from
@coreai-ds/react-components.
import { Button, Dropdown, Spinner } from '@coreai-ds/react-components';
Import CoreAI-Sandbox-owned components and adapters from ~/components/common.
import { Card, ExternalLink, Image, Link, TabLinkList } from '~/components/common';
The app barrel exports only repository-owned behavior. It does not re-export CoreAI. Never import
components from @fluentui/react-components directly. Direct imports from
@fluentui/react-icons remain supported.
Use the local Link for React Router navigation, ExternalLink for external URLs, Card for all
cards, and Image for theme-aware and deployment-safe image sources. ESLint restricts direct
Link, Card, and Image imports from @coreai-ds/react-components; only the local adapter
implementations may import those underlying CoreAI components.
Skill Boundary
- This skill owns CoreAI Sandbox's repository boundary: decide whether the need is satisfied by CoreAI or by an existing app-owned adapter, composition, hook, theme utility, or asset.
coreai-ds-fluentui-reactowns external package documentation retrieval and version checks. Invoke it for every CoreAI component or prop decision instead of restating its catalog here.- Local source under
app/components/common/**is authoritative only for CoreAI-Sandbox-owned behavior; it is not a substitute for CoreAI documentation.
Choose and Verify Components
- Invoke the
coreai-ds-fluentui-reactskill and retrieve the relevant published documentation before selecting, changing, or reviewing a component or its props. Follow its discovery, version-check, and retrieval-failure workflow. Do not infer APIs from stock Fluent behavior. - Verify the selected API against the installed package when documented versions differ. Report missing guidance or unsupported APIs rather than silently substituting prior knowledge.
- Check
app/components/common/index.tsfor an existing CoreAI-Sandbox-owned export only when the requested behavior is product-specific or integrates an app concern such as React Router. - When a local export exists, read its source under
app/components/common/**before using it. Published package documentation does not define CoreAI-Sandbox-owned behavior. - Prefer an existing documented component or template over recreating the same interaction with custom markup and CSS.
Do not maintain a static component catalog in this skill. Published CoreAI documentation is the source of truth for CoreAI components, and the app barrel and local source are the source of truth for repository-owned exports.
Semantics
Use links for navigation and buttons for actions. Do not make a Button navigate
or use a link to perform an action. Use Link for app routes and ExternalLink for URLs outside
the app.
Related skills
css-styling— required when writing styles for the componenticons— for icon selection and bundlingcoreai-ds-fluentui-react— required for CoreAI component documentation and API decisions
04 同仓库更多 Skills
visual-design-review
Reviews page hierarchy, grouping, density, actions and state design using consumer-owned product and design-system guidance. Use when asked for a visual design review, page critique or whether a new page communicates its task clearly.
setup-skills
Configures shared sources and drafts context with independent writers. Plain/fresh setup offers installation of user-named packages and reuses built-in browser capabilities, adding browser tooling only for an evidenced required-check gap. Use for setup, source repair, writing context or refreshing drafts. Configure-only skips tooling and authoring; installations and activation require separate approval.
review-hub-feedback
Review Hub feedback for reusable design themes through discovery, independent judging and synthesis. No diagnosis or optimization.
responsive-audit
Audits UI layout, overflow and navigation across product-defined viewports using consumer context and browser tools. Use when asked to check responsiveness, test mobile layout or audit breakpoint behavior.
prototype-controls
Create and wire Replica prototype controls. Use when asked to add or change dropdowns, sliders, input fields, toggles or action buttons that configure variants, scenarios, visible UI, app state or data sources, even without canvas terminology. Covers declarations, typed bindings, defaults, conditions, resets and actions. Product UI form fields and filters alone belong to create-prototype.
product-design
Guides product-design decisions using the consuming repository's design-system, product, and repository context. Use when designing UI, choosing layout or navigation, handling states and forms, messaging, disclosure, onboarding, visualization, copy, delete, filter, or search interactions. Triggers on 'design guidance', 'how to design', 'UI pattern', 'product design', 'scenario pattern', 'confirmation dialog', 'delete flow', 'copy to clipboard', 'filter', and 'search'.