mlorentedev

systematic-debugging

mlorentedev2/14/2026

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

qa-plan

mlorentedev3/1/2026

Use when creating test plans, QA plans, or acceptance testing strategies. Generates structured test scenarios from PRDs with traceability back to requirements.

docker

mlorentedev3/27/2026

Generate production-ready Dockerfile and docker-compose.yml. Use when containerizing applications, setting up local development environments, or creating multi-service deployments. Applies security be...

brainstorming

mlorentedev2/8/2026

Use before any creative work - creating features, building components, adding functionality. Explores user intent, requirements, and design before implementation through collaborative dialogue.

backlog

mlorentedev2/8/2026

Update and consolidate project backlog. Use when reviewing, reorganizing, or triaging BACKLOG.md, tasks/todo.md, or TODO files across the repo.

refactor

mlorentedev2/12/2026

Refactor code for improved structure, readability, and maintainability. Use when code needs cleanup following SOLID/DRY/KISS principles, adding type hints, reducing complexity, improving naming, or mo...