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>
60 lines
1.8 KiB
Markdown
60 lines
1.8 KiB
Markdown
---
|
|
name: seed setup
|
|
---
|
|
|
|
# /seed setup - Data Seed Setup Wizard
|
|
|
|
## Skills to Load
|
|
- skills/schema-inference.md
|
|
- skills/visual-header.md
|
|
|
|
## Visual Output
|
|
|
|
Display header: `DATA-SEED - Setup Wizard`
|
|
|
|
## Usage
|
|
|
|
```
|
|
/seed setup
|
|
```
|
|
|
|
## Workflow
|
|
|
|
### Phase 1: Environment Detection
|
|
- Detect project type: Python (SQLAlchemy, Django ORM), Node.js (Prisma, TypeORM), or raw SQL
|
|
- Check for existing schema files: `schema.prisma`, `models.py`, `*.sql` DDL files
|
|
- Identify package manager and installed ORM libraries
|
|
|
|
### Phase 2: Schema Source Configuration
|
|
- Ask user to confirm detected schema source or specify manually
|
|
- Supported sources:
|
|
- SQLAlchemy models (`models.py`, `models/` directory)
|
|
- Prisma schema (`prisma/schema.prisma`)
|
|
- Django models (`models.py` with Django imports)
|
|
- Raw SQL DDL files (`*.sql` with CREATE TABLE statements)
|
|
- JSON Schema definitions (`*.schema.json`)
|
|
- Store schema source path for future commands
|
|
|
|
### Phase 3: Output Configuration
|
|
- Ask preferred output format: SQL inserts, JSON fixtures, CSV files, or ORM factory objects
|
|
- Ask preferred output directory (default: `seeds/` or `fixtures/`)
|
|
- Ask default locale for faker data (default: `en_US`)
|
|
|
|
### Phase 4: Profile Initialization
|
|
- Create default profiles if none exist:
|
|
- `small` — 10 rows per table, minimal relationships
|
|
- `medium` — 100 rows per table, realistic relationships
|
|
- `large` — 1000 rows per table, stress-test volume
|
|
- Store profiles in `seed-profiles.json` in output directory
|
|
|
|
### Phase 5: Validation
|
|
- Verify schema can be parsed from detected source
|
|
- Display summary with detected tables, column counts, and relationship map
|
|
- Inform user of available commands
|
|
|
|
## Important Notes
|
|
|
|
- Uses Bash, Read, Write, AskUserQuestion tools
|
|
- Does not require database connection (schema-first approach)
|
|
- Profile definitions are portable across environments
|