react-components
Skill117 starsChanged 10 days agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Import CoreAI components, styling APIs, and tokens directly from @coreai-ds/react-components.
- Very specific: line 17
Import CoreAI-Sandbox-owned components and adapters from ~/components/common.
- Very specific: line 27
Use the local Link for React Router navigation, ExternalLink for external URLs, Card for all cards, and Image for theme-aware and …
- Distinctive: line 47
Verify the selected API against the installed package when documented versions differ.
- Very specific: line 49
Check app/components/common/index.ts for an existing CoreAI-Sandbox-owned export only when the requested behavior is product-specific or …
- Very specific: line 51
When a local export exists, read its source under app/components/common/ before using it.
- Distinctive: line 53
Prefer an existing documented component or template over recreating the same interaction with custom markup and CSS.
- Distinctive: line 56
Do not maintain a static component catalog in this skill.
- Very specific: line 62
Use links for navigation and buttons for actions.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- langchain-ai/skills-benchmarks★ 116same name
- delorenj/skills★ 18same name
- jorgeasaurus/agent-skills★ 14same name
- aprameyak/coding-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hub/AGENTS.mdAGENTS.md
- starters/coreai/AGENTS.mdAGENTS.md
- starters/minimal/AGENTS.mdAGENTS.md
- replica-pick-and-polishSkill
- replica-publish-prototypeSkill
- review-hub-feedbackSkill
- code-reviewSkill
- write-testsSkill
- coreai-ds-fluentui-reactSkill
- css-stylingSkill
- features-variantsSkill
- iconsSkill
- interpreting-htmlSkill
- lintSkill
- new-variantSkill
- routingSkill
- start-appSkill
- state-managementSkill
- context-templatesSkill
- accessibility-auditSkill
- add-seed-dataSkill
- agent-browserSkill
- browser-canvas-validationSkill
- component-design-system-reviewSkill
- create-prototypeSkill
- developer-handoffSkill
- prepare-feedback-proposalsSkill
- product-designSkill
- prototype-controlsSkill
- responsive-auditSkill
- review-hub-feedbackSkill
- setup-skillsSkill
- visual-design-reviewSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

