Iot_Simulator

Use when writing or modifying Express + Prisma backend code in VSmartwatch admin (HealthGuard/backend). Reference patterns for Prisma client singleton, JWT auth, route/controller/service layering, error handling, Postgres patterns, Socket.IO realtime, AWS S3, and Jest testing.

Use when writing or modifying FastAPI backend code in VSmartwatch (health_system/backend, healthguard-model-api, Iot_Simulator_clean/api_server). Reference patterns for router/service/repository layering, Pydantic v2, async DB, internal-secret auth, error handling, sanitized responses, and pytest.

Use when writing or modifying Flutter/Dart code in VSmartwatch mobile app (health_system/lib). Reference patterns for Riverpod state management, dio HTTP, repository pattern, GoRouter navigation, FCM (push only), elderly UX, and widget testing.

Use when about to claim work is complete, fixed, or passing. Requires running verification commands and reading actual output BEFORE making any success claims. Evidence before assertions.

Ultra-compressed Vietnamese mode. ONLY activate when the user types "/caveman" or says "bật caveman", "caveman mode", "ngắn gọn cực", "tiết kiệm token". Off by default. Output stays Vietnamese; only the response style changes.

Five-axis code review framework. Use when reviewing your own changes before merge, or reviewing PR. Evaluates correctness, readability, architecture, security, performance.

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria. Applies to ALL code work in VSmartwatch.

Manage screen spec lifecycle for VSmartwatch mobile app — generate from UC/SRS, edit, cross-link, and maintain the Screen Index. Use when user says "list all screens", "quản lý màn hình", "scan screens", "generate screen spec", "kiểm tra screen index", "sync screens", or "TASK <subcommand>".

Use when encountering any bug, test failure, or unexpected behavior, BEFORE proposing fixes. Enforces root-cause investigation over symptom patching. 4-phase process.

Test-Driven Development discipline. Use when implementing any feature or bugfix BEFORE writing implementation code. Enforces RED-GREEN-REFACTOR cycle with mandatory failing-test verification.

Use when you have an approved spec and need to break it into bite-sized vertical-slice tasks with exact files, test code, and commands. Required before /build for non-trivial features.

Use when investigating or fixing a non-trivial bug to track all attempted approaches in a centralized log. Prevents proposing the same failed approach twice across sessions. MUST read existing log before proposing fix; MUST update after each attempt.

Quét mã nguồn thực tế và cập nhật Project_Structure.md + summaries/ để PM_REVIEW luôn khớp với code hiện tại. Dành cho PM/AI agent quản lý cấu trúc dự án HealthGuard. Kích hoạt khi: "check project", "cập nhật cấu trúc", "kiểm tra source", "project thay đổi chưa?", "sync lại PM", "update summaries", "review structure", "kiểm tra project", "project còn đúng không?", "check source", "update structure".

Use when making an architectural or design decision (choosing approach A over B, adopting library, changing convention, defining cross-repo contract). Records context + options + decision + consequences in PM_REVIEW/ADR for future-self and other sessions to read.

Perform a detailed evaluation of a specific feature — analyze actual source code against architecture standards, verify SRS compliance, assess implementation quality, and cross-check JIRA Stories for the project development team. Use when user says "review code", "đánh giá chi tiết", "evaluate feature", "check implementation", "review module", "review chức năng", "kiểm tra code", "detailed review", "danh gia chi tiet", "xem code giúp", "chấm điểm code", "review feature", "score this module". DO NOT use for: PR reviews, debugging, writing new code, generating test cases.

High-level assessment for the HealthGuard project. Triggers on keywords: project structure, project overview, tong quan, review architecture, assess structure. Uses MASTER_INDEX to optimize context.

Audit and review current JIRA sprint backlog progress by scanning _SPRINT.md and STORIES.md files. Generates progress tracking reports with completion rates and risk analysis. Triggers: check progress, review backlog, tiến độ sprint, kiểm tra backlog, sprint review, audit tasks.

Use BEFORE writing spec or code for new features. Explores user intent, constraints, and 2-3 design approaches through one-question-at-a-time dialogue. Required before /spec.

Automatically generate or draft standards-compliant SRS (Software Requirements Specification) and SDD (Software Design Document - IEEE-1016-2009) from source code and requirements. Utilizes a multi-agent brainstorming model with Architect and BA roles to cross-review and produce the documentation. Use when the user requests "write SRS", "write SDD", "create IEEE-1016-2009 template", "generate design document", "generate system design document".

Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritizati...

Act as an elite Project Manager to analyze UC, SRS, and system overview then generate structured Sprint Plans, Epics, and Stories following the established JIRA template structure. Triggers: sắp xếp task, dự toán công việc, tạo task list, lên plan, lập kế hoạch, sprint planning, create sprint, estimate workload, backlog grooming, epic breakdown, story mapping, PM review planning, chia task, phân công việc.

Structured analysis of Use Cases, requirements documents, and system specifications. Extracts complexity signals, identifies dependencies, and estimates effort for project planning.

Prioritization frameworks (RICE, MoSCoW) and capacity planning tools for Sprint structuring. Determines optimal Sprint groupings based on team velocity and dependency constraints.

Generate structured test case files from UC/SRS/SQL/API sources, execute existing test cases with timestamp tracking, or create AI-executable test plans. Triggers: generate test case, test case, testing, TC generation, sinh test case, test function, test module, run test, execute test, test tracking, QA test, test plan, kế hoạch test, tạo test plan.

Batch audit all Use Cases, evaluate relevance to SRS, cross-check UC-SQL-JIRA gaps. Triggers: audit UC, cross-check, use case coverage, gap analysis, UC inventory, UC relevance, UC SQL check, missing UC, missing task, orphan column, UC completeness, SRS alignment, check UC, evaluate UC.