vspo-portal

Next.js 15 Pages Router frontend development. Feature-based + Container/Presenter pattern, MUI v7 + Emotion CSS-in-JS.

Build API client tests with Vitest and MockHandler. Validate OpenAPI contract compliance with table-driven tests and minimal mocks.

Next.js 15 + Cloudflare Workers + @vspo-lab/api client. Result-type error handling, OpenAPI-generated client, feature-based architecture.

PR/code review based on architecture rules. Detects violations of UseCase implementation rules, Result type, and JSDoc conventions.

Create a conventional commit. No Co-Authored-By trailer.

Design tokens (OKLch), color palette, typography, UI patterns, accessibility (WCAG 2.2).

Update docs/domain alongside feature additions and spec changes, maintaining a history of specification decisions.

Initialize docs/domain with a single interview session, organizing the MVP and open items.

Create architecture diagrams using the draw.io MCP server (open_drawio_mermaid / open_drawio_xml) and reflect them in docs/infra/diagrams.

Build E2E tests with Playwright, ensuring major user flows through production-equivalent paths. Avoid internal mocks and limit mocking to external boundaries only.

Result-type-based error handling without try-catch. Type-safe error flow using wrap/Ok/Err/AppError.

Terraform (GCP), CI/CD (tfaction/GitHub Actions), security scanning, Biome lint, knip.

Skill for advancing Terraform design and implementation centered on tfaction. Standardizes state splitting, module design, and GitHub Actions integration.

Read specifications from docs/plan/<feature>/ and generate a phased implementation checklist.

Initialize a new project from the template. Define domain specifications through a structured interview and write them to docs/domain/.

Build integration tests with a real DB and real app wiring, verifying without internal mocks and using minimal mocks only at external boundaries.

Generate structured specification documents in docs/plan/<feature>/ from ambiguous requirements.

Run the project's quality checks and report only failures that need attention. Used when the user requests a check run, code change verification, or identifying the first failing gate.

Technical research and specification verification skill using Context7 MCP. Used for checking the latest library/framework documentation, verifying API specifications, confirming version differences, and gathering evidence for implementation decisions. Especially useful for investigating "latest", "recommended", "breaking changes", and "migration steps".

Comprehensive testing skill covering Unit/Integration/API/UI/VRT/E2E with Vitest at the core. Ensures quality incrementally using table-driven tests and a minimal-mock approach.

Use the t_wada-based Test-Driven Development strategy to implement incrementally and safely with Red-Green-Refactor. Used when you want to lock down specifications test-first during new feature implementation, bug fixes, or refactoring.

Type definitions via Zod Schema First, satisfies operator, type-safe patterns. Direct interface definitions and as assertions are prohibited.

Implement UI tests using Testing Library priority queries and table-driven approach, verifying from the user's perspective with minimal mocks.

Implement unit tests using Vitest table-driven approach, verifying domain/utility behavior with minimal mocks.

Update docs/ in response to code changes. Keep docs/ always up to date.

Implement VRT with Storybook + Playwright, detecting UI regressions via snapshot diffs. Pin non-deterministic elements and operate with minimal mocks.