Template

Files

lmiranda 2d51df7a42 feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]

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>

2026-02-06 14:52:11 -05:00

2.4 KiB

Raw Blame History

Design: data-seed

Domain: data Target Version: v9.3.0

Purpose

Test data generation and database seeding. Generates realistic fake data based on schema definitions, supports reproducible seeds, and manages seed files for development and testing environments.

Target Users

Developers needing test data for local development
QA teams requiring reproducible datasets
Projects with complex relational data models

Commands

Command	Description
`/seed setup`	Setup wizard — detect schema source, configure output paths
`/seed generate`	Generate seed data from schema or model definitions
`/seed apply`	Apply seed data to database or create fixture files
`/seed profile`	Define reusable data profiles (small, medium, large, edge-cases)
`/seed validate`	Validate seed data against schema constraints and foreign keys

Agent Architecture

Agent	Model	Mode	Role
`seed-generator`	sonnet	acceptEdits	Data generation, profile management
`seed-validator`	haiku	plan	Read-only validation of seed data integrity

Skills

Skill	Purpose
`schema-inference`	Infer data types and constraints from models/migrations
`faker-patterns`	Realistic data generation patterns (names, emails, addresses, etc.)
`relationship-resolution`	Foreign key and relationship-aware data generation
`profile-management`	Seed profile definitions and sizing
`visual-header`	Standard command output headers

MCP Server

Not required. Seed data is generated as files (JSON, SQL, CSV). Database insertion is handled by the application's own tooling.

Integration Points

Plugin	Integration
saas-db-migrate	Schema models used as seed generation input
data-platform	Generated data can be loaded via `/data ingest`
saas-test-pilot	Seed data used in integration test fixtures
projman	Issue labels: `Component/Data`, `Tech/Faker`

Token Budget

Component	Estimated Tokens
`claude-md-integration.md`	~500
Dispatch file (`seed.md`)	~200
5 commands (avg)	~3,000
2 agents	~1,000
5 skills	~2,000
Total	~6,700

Open Questions

Should we support database-specific seed formats (pg_dump, mysqldump)?
Integration with Faker library or custom generation?

2.4 KiB Raw Blame History