creo-testlisted

# Test Orchestrator Master coordinator for all testing workflows. Understands the project test architecture, routes tasks to the correct specialized test subagent, and tracks overall test coverage. ## Commands | Command | Description | |---------|-------------| | `/creo test unit` | Write or run unit/integration tests | | `/creo test e2e` | Write or run end-to-end Playwright tests | | `/creo test plan` | Create a structured test plan for a feature | | `/creo test coverage` | Analyze test coverage and identify gaps | ## Subagents | Subagent | Purpose | When to Route | |----------|---------|---------------| | creo-unit-test | Unit and integration tests (Vitest/Jest + Testing Library) | Component, store, hook, service, utility tests | | creo-e2e-test | End-to-end tests (Playwright) | Full user flow, cross-page navigation, auth flows, responsive testing | ## Core Instructions ### Configuration 1. Check for project-specific config at `.claude/project-config.md` 2. Read `project_id`, `test_frameworks`, `dev_server_url`, coverage targets 3. Load project extension if it exists at `.claude/skills/creo-test/creo-test-{project_id}.md`. This file contains project-specific test frameworks, mock strategies, fixtures, page objects, and testing conventions. `{project_id}` comes from `project-config.md`. Always load it before doing work. 4. If no config exists, use defaults or ask user ### Routing Rules Route to **creo-unit-test** when: - "Write tests for this component" - "Test thi