Guide a software project through staged engineering delivery from business discovery to architecture, technology selection, detailed requirements, API/database design, integration testing, performance testing, and release readiness. Use when a user wants project lifecycle guidance, staged delivery governance, engineering process coaching, or wants an agent to decide what project artifact or review gate should come next.
Design business architecture and technical architecture for staged software projects, including Mermaid diagrams, module boundaries, data flows, deployment view, integration points, project structure, and architecture risks. Use when moving from business context to architecture, when documenting module/service boundaries, or when reviewing whether architecture is ready for API/database design and implementation.
Verify generated or modified application code with reproducible build, test, runtime, browser, API, console, and network checks. Use after code generation or bug fixes, especially for web UI login flows, forms, dashboards, frontend/backend integration, local dev servers, and claims that implementation is complete or tested.
Guide integration testing, performance testing, release readiness, and quality gates for staged software projects. Use when planning or reviewing integration tests, test data, environment dependencies, API test collections, performance tests, release checks, rollback plans, or project acceptance gates.
Produce evidence-backed technology stack options and architecture decision records for Java Spring Boot and frontend projects. Use when selecting JDK, Spring Boot, Spring Cloud, Spring Cloud Alibaba, database, cache, messaging, API documentation, frontend framework, build tools, logging, exception handling, validation, ORM, migration, observability, code quality tools, or when validating dependency/version compatibility.
Guide API contract and database design for staged software projects. Use when designing REST APIs, OpenAPI plans, database tables, SQL migration direction, seed data, initial data, error codes, pagination, permissions, audit fields, API documentation, or when reviewing whether API/database artifacts are ready for development.
Guide frontend user experience and visual design before code generation. Use when choosing UI style, generating DESIGN.md, adapting external design references such as awesome-design-md, selecting layout density, component behavior, design tokens, frontend page standards, or preventing generic AI-looking web pages.
Clarify business context, business architecture, rough non-functional requirements, and detailed functional requirements for staged software projects. Use when a user gives a vague project idea, needs requirement elicitation, needs business workflows, user roles, acceptance criteria, or implementation-driving requirement slices before architecture or coding.