arvoreeducacao

Code review knowledge. Use when reviewing an implementation against requirements, validating code quality, checking edge cases and security, or before opening a PR.

Systematic debugging knowledge. Use when diagnosing errors, investigating unexpected behavior, doing root cause analysis, or troubleshooting production issues.

QA and testing knowledge. Use when testing an implementation end-to-end — building a test plan, validating APIs with curl, driving the UI with Playwright, comparing against Figma, and documenting pass/fail with evidence.

Requirements refinement knowledge. Use when turning a vague request into a clear spec, defining API contracts, identifying affected repositories, or capturing scope and edge cases before coding.

AWS infrastructure patterns. Use when working with AWS services, secrets, ECS/EKS, RDS, S3, CloudWatch, or debugging infrastructure issues.

NestJS backend development patterns. Use when developing backend APIs with NestJS, TypeORM/Prisma, and TypeScript.

MySQL database patterns. Use when querying database schema, exploring data, understanding table relationships, or debugging data issues.

NextJS frontend development patterns. Use when developing frontend code with NextJS, React, Tailwind, and TypeScript.

Team knowledge base with decisions, conventions, incidents, domain knowledge, and gotchas. Use before starting any task to search for relevant context, past decisions, and known gotchas.