Vmarble-Warehouse-Management-Client

Use when setting up, modifying, or debugging Harness CI pipelines for the VMARBLE project. Covers connector setup, pipeline authoring (Visual editor vs YAML), secrets, triggers, free-tier constraints, and common errors. Trigger words: "harness", "CI pipeline", "build pipeline", "connector", "harness cloud", "docker build ci", "pipeline trigger".

Use to ensure absolute sync between frontend and backend. Invoke this skill in the next-task automation flow whenever the selected issue introduces a new endpoint, modifies an existing DTO mirrored from iface.go, changes request/response fields, or adds a new backend-facing interface such as deps.go. Verify contract consistency before merge.

Use when starting ANY non-trivial issue or feature on the Next.js frontend — covers the full Senior Engineer workflow: requirements clarification → technical design → task breakdown → implement → self-QA → PR. ALWAYS trigger this skill when the user says "implement", "add feature", "build page", "add component", "create hook", "fix", "fix bug", "find root cause", "plan and implement", or pastes a GitHub issue/ticket number. Do NOT skip phases — Phase 5 (Self-QA) is the gate before PR and the phase most commonly skipped; skipping it is the #1 source of rework.

Use when adding a new API domain, new endpoint to an existing domain, or a new TanStack Query hook. Covers the 4-file pattern (api client + types + hook), query key conventions, mutation invalidation, and error handling.

Use when adding a new page or route — choosing the correct route group (kiosk/dashboard/auth), structuring the page file, adding loading.tsx and error.tsx siblings, and following responsive layout rules.

Use when adding a new shadcn/ui component to the project — running the CLI, placing files, writing wrappers, or creating custom CVA-based variants following the existing button/card/badge patterns.

Use to verify whether UI/UX and frontend logic reflect the business rules. Always invoke this skill during the "Làm task tiếp theo" / "Start next task" automation flow after selecting an issue: read docs/backend-business-logic-en.md (primary, v2.0 Container-flow pivot) and docs/backend-business-logic-vi.md (Vietnamese terms), identify every touched BR-* rule, map required states/validations/terminology, and block implementation if any relevant business rule is unclear.

Use to ensure absolute sync between frontend and backend. Invoke this skill in the next-task automation flow whenever the selected issue introduces a new endpoint, modifies an existing DTO mirrored from iface.go, changes request/response fields, or adds a new backend-facing interface such as deps.go. Verify contract consistency before merge.

Use when building any component for the (kiosk) route group — shop-floor mobile UI for workers. Covers touch targets, BigButton, ScannerView, QR print, Vietnamese labels, and sonner toasts.

Use to analyze the backlog from a user perspective (Kiosk/Dashboard), break down tasks, manage FE issues, and drive next-task triage when the user says "Làm task tiếp theo", "task tiếp theo", "Start next task", or asks to pick an issue from the GitLab board. In that trigger flow, identify the highest-priority open issue first, then hand the selected issue into the audit and implementation workflow.

Use when implementing any feature related to remnant tracking, allocation, cutting records, costing, overflow alerts, or barcode/QR. Provides the business rules and API endpoints without requiring you to read the docs.

Use when starting ANY non-trivial issue or feature on the Next.js frontend — covers the full Senior Engineer workflow: requirements clarification → technical design → task breakdown → implement → self-QA → PR. ALWAYS trigger this skill when the user says "implement", "add feature", "build page", "add component", "create hook", "fix", "fix bug", "find root cause", "plan and implement", or pastes a GitHub issue/ticket number. Do NOT skip phases — Phase 5 (Self-QA) is the gate before PR and the phase most commonly skipped; skipping it is the #1 source of rework.

Use when starting any non-trivial issue or feature on the Next.js frontend — 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", "build page", "add component", "create hook", "fix", "fix bug", "find root cause", pastes a GitHub issue/ticket, or enters the "Làm task tiếp theo" / "Start next task" automation flow after issue selection. Start at Phase 1 and never jump straight to coding.

Use when the user says "Làm task tiếp theo", "task tiếp theo", "Start next task", asks to pick the next issue, or wants to continue from a GitLab board item. Orchestrate the automation workflow: fetch the highest-priority open issue from the GitLab FE project via the product-manager workflow, read the full issue and DoD, run a business-auditor pass against docs/backend-business-logic-en.md + docs/backend-business-logic-vi.md, identify every touched BR-* rule and block if any rule is unclear, hand off to senior-workflow-frontend at Phase 1, invoke integration-architect whenever the task adds or changes an endpoint or DTO, and update docs/PROJECT-STATUS.md after the issue is closed.

Use when writing TypeScript in this project — API DTOs, component prop types, hook generics, strict null handling, and avoiding common TS mistakes with the existing codebase patterns.

Use when adding a new API domain, new endpoint to an existing domain, or a new TanStack Query hook. Covers the 4-file pattern (api client + types + hook), query key conventions, mutation invalidation, and error handling.

Use when adding a new shadcn/ui component to the project — running the CLI, placing files, writing wrappers, or creating custom CVA-based variants following the existing button/card/badge patterns.

Use to analyze the backlog from a user perspective (Kiosk/Dashboard), break down tasks, manage FE issues, and drive next-task triage when the user says "Làm task tiếp theo", "task tiếp theo", "Start next task", asks Codex to pick an issue from the GitHub Projects Kanban board, or hands Codex a concrete issue to execute end-to-end. In that trigger flow, identify or confirm the issue first, then hand the selected issue into the audit, implementation, and PR workflow.

Use when starting ANY non-trivial issue or feature on the Next.js frontend — covers the full Senior Engineer workflow: requirements clarification → technical design → task breakdown → implement → self-QA → PR. ALWAYS trigger this skill when the user says "implement", "add feature", "build page", "add component", "create hook", "fix", "fix bug", "find root cause", "plan and implement", pastes a GitHub issue/ticket number or URL, or asks Codex to take a selected issue all the way from intake to PR. Do NOT skip phases — Phase 5 (Self-QA) is the gate before PR and the phase most commonly skipped; skipping it is the #1 source of rework.

Use when starting any non-trivial issue or feature on the Next.js frontend — 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", "build page", "add component", "create hook", "fix", "fix bug", "find root cause", pastes a GitHub issue/ticket/URL, asks Codex to continue a selected issue from intake to PR, or enters the "Làm task tiếp theo" / "Start next task" automation flow after issue selection. Start at Phase 1 and never jump straight to coding or stop before the PR phase unless blocked.

Use when the user says "Làm task tiếp theo", "task tiếp theo", "Start next task", asks Codex to pick the next issue, wants Codex to continue from a GitHub Projects Kanban item, or wants Codex to take a selected issue from intake all the way to branch/commit/PR. Orchestrate the automation workflow in order: fetch or accept the chosen issue, read the full issue and Definition of Done, run a business-auditor pass against docs/backend-business-logic-vi.md to identify every touched BR-* rule and block if any rule is unclear, then hand off to senior-workflow starting at Phase 1, invoke integration-architect whenever the task adds or changes an endpoint, a DTO mirrored from iface.go, or a deps.go interface, and continue through self-QA into the standard branch/commit/PR flow when implementation is done.

Use when writing TypeScript in this project — API DTOs, component prop types, hook generics, strict null handling, and avoiding common TS mistakes with the existing codebase patterns.

Use to verify whether UI/UX and frontend logic reflect the Vietnamese business rules. Always invoke this skill during the "Làm task tiếp theo" / "Start next task" automation flow after selecting an issue: read docs/backend-business-logic-vi.md, identify every touched BR-* rule, map required states/validations/terminology, and block implementation if any relevant business rule is unclear.

Use when starting ANY non-trivial issue or feature on the Next.js frontend — covers the full Senior Engineer workflow: requirements clarification -> technical design -> task breakdown -> implement -> self-QA -> PR. ALWAYS trigger this skill when the user says "implement", "add feature", "build page", "add component", "create hook", "fix", "fix bug", "find root cause", "plan and implement", "sua" or pastes a GitHub issue/ticket number. Do NOT skip phases — Phase 5 (Self-QA) is the gate before PR and the phase most commonly skipped; skipping it is the #1 source of rework.