Meep

Write and organize unit tests for functions, methods, and classes using `package:test`. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.

Uses get_runtime_errors and lsp to fetch an active stack trace, locate the failing line, apply a fix, and verify resolution via hot_reload.

Define and generate mock objects for external dependencies using `package:mockito` and `build_runner`. Use when unit testing classes that depend on complex external services like APIs or databases.

Execute `dart analyze` to identify warnings and errors, and use `dart fix --apply` to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.

Configures Flutter Driver for app interaction and converts MCP actions into permanent integration tests. Use when adding integration testing to a project, exploring UI components via MCP, or automating user flows with the integration_test package.

Implement a component-level test using `WidgetTester` to verify UI rendering and user interactions (tapping, scrolling, entering text). Use when validating that a specific widget displays correct data and responds to events as expected.

Architects a Flutter application using the recommended layered approach (UI, Logic, Data). Use when structuring a new project or refactoring for scalability.

Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools. Use when addressing "RenderFlex overflowed", "Vertical viewport was given unbounded height", or similar layout issues.

Convert Figma frame/node → Flutter widget với strict design token mapping + dual-source verification (MCP data + PNG image). Use when user pastes a Figma node URL or attaches a Figma screenshot and asks to generate a Flutter widget. Scope: 1 frame = 1 widget (compose multiple widgets sau). Strict gate: KHÔNG inline hex/font — token thiếu → ping leader.

Six-axis code review framework (folder name "five-axis" kept for backward compat) — Fast/Deep paths + precision-first output. Use when reviewing your own changes before PR or reviewing teammate's PR. Evaluates contract adherence, correctness, readability, architecture, security, performance — but defaults to flagging only real bugs (🔴 + 🟡), not nits.

Convert Figma frame/node → Flutter widget với strict design token mapping + dual-source verification (MCP data + PNG image). Use when user pastes a Figma node URL or attaches a Figma screenshot and asks to generate a Flutter widget. Scope: 1 frame = 1 widget (compose multiple widgets sau). Strict gate: KHÔNG inline hex/font — token thiếu → ping leader.

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.

Use when writing or modifying Flutter/Dart code that touches Firestore, Storage, FCM, or Auth. Reference patterns for state management, repository pattern, Firestore data modeling, security rules, and home widget integration.

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 Meep.

Use when writing or modifying Node.js + TypeScript backend code (Cloud Functions or standalone API). Patterns for env validation, error handling, logging, testing, and Express middleware.

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 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.

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.

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