lmiranda
2d51df7a42
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
name
| name |
|---|
| react setup |
/react setup - React Project Setup Wizard
Skills to Load
- skills/framework-detection.md
- skills/visual-header.md
Visual Output
Display header: REACT-PLATFORM - Setup Wizard
Usage
/react setup
Workflow
Phase 1: Framework Detection
- Scan for
package.jsonto confirm Node.js project - Detect framework using
skills/framework-detection.md:- Next.js (check for
nextin dependencies,next.config.*) - Vite + React (check for
viteand@vitejs/plugin-react) - Create React App (check for
react-scripts) - Remix (check for
@remix-run/react)
- Next.js (check for
- Detect App Router vs Pages Router for Next.js projects
- Identify TypeScript usage (
tsconfig.json,.tsxfiles)
Phase 2: Project Structure Analysis
- Scan directory structure for existing patterns:
- Component directory:
src/components/,components/,app/components/ - Page directory:
src/pages/,app/,src/app/ - Hook directory:
src/hooks/,hooks/ - Test patterns:
__tests__/,*.test.tsx,*.spec.tsx
- Component directory:
- Detect existing barrel files (
index.tsre-exports) - Check for existing state management (Redux store, Zustand stores, Context providers)
Phase 3: Convention Configuration
- Confirm or override detected patterns:
- Component naming: PascalCase (default)
- File naming: PascalCase (
Button.tsx) or kebab-case (button.tsx) - Test co-location: same directory (
Button.test.tsx) or__tests__/subdirectory - CSS approach: CSS Modules, Tailwind, styled-components, vanilla extract
- Export style: named exports, default exports, or barrel files
Phase 4: Summary
- Display detected configuration:
- Framework and version
- TypeScript: yes/no
- Component directory
- Routing pattern
- State management (if detected)
- CSS approach
- Test runner (Jest, Vitest)
- Store configuration for future commands
Important Notes
- Uses Bash, Read, Write, AskUserQuestion tools
- Does not install packages — only detects and configures
- Configuration stored in project for consistent scaffolding