メニュー
Use to ensure alignment between Backend and Frontend, guarding the Modular Monolith and API contracts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | integration-architect |
| description | Use to ensure alignment between Backend and Frontend, guarding the Modular Monolith and API contracts. |
Ensures long-term system integrity, focusing on the BE-FE bridge.
deps.go interfaces.internal/domain/ are shared.snake_case) must match src/types/api.ts in the Client.BizError (422, 409) -> FE must have matching ApiClientError handlers.PagedResult<T> to match FE table expectations.CNC_COMPLETE, FINISHING_COMPLETE, WAREHOUSE_SHIP).ScannerView parsing logic in FE.iface.go in Service -> Alert the user to update src/types/api.ts in Client.make swagger and verify if the FE needs a new api-route.Goal: Prevent "Runtime Type Errors" and "Inconsistent UI States" during deployment.
Use to verify if the code/logic aligns with the Vietnamese business spec. Mandatory cross-referencing with BR-* rules before implementation.
Use when the user asks to deploy, dockerize, set up CI/CD, configure environments, or prepare for go-live. Covers Docker Compose, GitHub Actions, health checks, environment configuration, database backup, and production readiness checklist. Trigger words: "deploy", "docker", "CI", "CD", "go live", "production", "staging", "health check", "backup", "monitoring".
Use to analyze the backlog, break down tasks from requirements, and automate Issue/Sprint management using GitLab API.
Use to audit and enforce role-based access control (RBAC) across all API endpoints. Scans handler routes, maps required roles from the business spec, generates RequireRole middleware guards, and reports orphan (unprotected) endpoints. Trigger words: "rbac", "phân quyền", "role", "access control", "security audit", "guard endpoints", "protect routes".
Use when starting ANY non-trivial issue or feature on the Go backend — covers the full Senior Engineer workflow: requirements clarification -> technical design -> task breakdown -> implement + test -> self-QA -> PR. ALWAYS trigger this skill when the user says "implement", "add feature", "fix issue", "build", "create endpoint", or pastes a GitHub issue/ticket. Do NOT skip phases — especially Phase 5 (Self-QA) which is the most commonly forgotten step before submitting code.
Use to review Go backend changes for correctness, security, modular-monolith boundaries, error handling, SQL safety, domain invariants, and missing tests. Trigger when the user asks for code review, PR review, audit findings, or correctness/security review.