agentleFS
GitHubKnown publishergithub/replica/starters/coreai/.agents/skills/react-components/SKILL.md

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
  1. Very specific:

    Import CoreAI components, styling APIs, and tokens directly from @coreai-ds/react-components.

    line 10
  2. Very specific:

    Import CoreAI-Sandbox-owned components and adapters from ~/components/common.

    line 17
  3. Very specific:

    Use the local Link for React Router navigation, ExternalLink for external URLs, Card for all cards, and Image for theme-aware and …

    line 27
  4. Distinctive:

    Verify the selected API against the installed package when documented versions differ.

    line 47
  5. Very specific:

    Check app/components/common/index.ts for an existing CoreAI-Sandbox-owned export only when the requested behavior is product-specific or …

    line 49
  6. Very specific:

    When a local export exists, read its source under app/components/common/ before using it.

    line 51
  7. Distinctive:

    Prefer an existing documented component or template over recreating the same interaction with custom markup and CSS.

    line 53
  8. Distinctive:

    Do not maintain a static component catalog in this skill.

    line 56
  9. Very specific:

    Use links for navigation and buttons for actions.

    line 62

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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-react owns 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

  1. Invoke the coreai-ds-fluentui-react skill 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.
  2. Verify the selected API against the installed package when documented versions differ. Report missing guidance or unsupported APIs rather than silently substituting prior knowledge.
  3. Check app/components/common/index.ts for an existing CoreAI-Sandbox-owned export only when the requested behavior is product-specific or integrates an app concern such as React Router.
  4. 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.
  5. 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 component
  • icons — for icon selection and bundling
  • coreai-ds-fluentui-react — required for CoreAI component documentation and API decisions

Download now (ZIP)

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.