test-data-architect

What problem does it solve?

This Skill removes flaky, collision-prone, and unsafe test data practices by designing deterministic fixtures, seeds, personas, and baseline records that tests can rely on across unit, integration, E2E, and manual layers.

Core Features & Use Cases

• Persona and baseline cataloging: Defines a minimal read-only world with stable synthetic identifiers, including tenant and role coverage for realistic test scenarios.
• Per-layer data sourcing: Chooses in-memory builders for unit tests, real-path factories for integration, API-created fixtures for E2E, and documented seeded accounts for manual testing.
• Parallel and safety controls: Adds worker-scoped namespacing, cleanup and TTL rules, synthetic-only PII-safe generation, and schema-coupled seed evolution.
• Use Case: A team with parallel integration tests and shared seed data can use this Skill to redesign fixtures so each run is isolated, reproducible, and free of production-data leakage.

Quick Start

Ask for a test data design for your suites, including personas, seed strategy, isolation rules, cleanup, and how each test layer should obtain data.