code-showcase-core-components
Core Components
When to Use
Use when maintaining a project that follows the ChrisWiles showcase component conventions. For a different or unknown library, start with core-components and map its examples to the actual project API; do not install both expecting additional components.
This entry describes the upstream project's component API/token names, not a bundled component library or universal React Native API. Verify actual exports, tokens and props in the target repository before using snippets. CardProps/variantStyles, handlers and imported components are illustrative dependencies; token use alone does not prove contrast, labeling or behavior.
Design System Overview
Reuse verified project primitives when they provide the required semantics and behavior. Native components remain appropriate when no equivalent primitive exists; token use alone does not establish accessibility.
Design Tokens
Prefer the project's existing semantic tokens. If no token expresses the requirement, document the exception or propose a scoped token addition; do not invent token names or change the whole design system.