Agent Skills: React Component Scaffolder (DEPRECATED)

'DEPRECATED: Use component-builder instead for M3-compliant, production-grade

UncategorizedID: okgoogle13/careercopilot/react-component-scaffolder

Install this agent skill to your local

pnpm dlx add-skill https://github.com/okgoogle13/careercopilot/tree/HEAD/.claude/skills/react-component-scaffolder

Skill Files

Browse the full folder contents for react-component-scaffolder.

Download Skill

Loading file tree…

.claude/skills/react-component-scaffolder/SKILL.md

Skill Metadata

Name
react-component-scaffolder
Description
'DEPRECATED: Use component-builder instead for M3-compliant, production-grade

React Component Scaffolder (DEPRECATED)

⚠️ This skill is deprecated and should no longer be used.

Purpose

(DEPRECATED) Previously used to create React component directory structures. ⚠️ Use component-builder instead.

When to Use

  • ❌ NEVER. Use component-builder instead.

Process

  1. Deprecation Check: Identify that this skill is deprecated.
  2. Redirection: Direct the user to use the component-builder skill.
  3. Manual Backup (If absolutely forced): Create basic directory structure without intelligent code generation.

The component-builder skill is the recommended replacement. It provides:

  • Production-grade components with best practices
  • M3 Expressive design token compliance
  • Token-aware styling (no hardcoded values)
  • Accessibility-first approach with ARIA labels
  • Comprehensive error handling and edge cases
  • TypeScript interfaces with JSDoc documentation

Migration Path

When asked to "create a component", use component-builder instead:

Old way:

User: Create a Button component
Assistant: Uses react-component-scaffolder

New way:

User: Create a Button component
Assistant: Uses component-builder (M3-compliant)

Why Not Use This Skill Anymore?

  1. react-component-scaffolder only creates directory structure with no intelligent code generation
  2. component-builder generates complete, production-ready components with M3 tokens
  3. Having both creates user confusion about which to use
  4. component-builder is strictly superior in every way

See component-builder for the recommended replacement.