panino

Use when implementing a new feature end-to-end from spec to PR. Covers the full SDLC: creating a feature branch from main, user journey validation, spec review, phased implementation (utilities first, then store layer, then UI), unit/integration/e2e testing, security review checklist, code review checklist, patching, and PR creation. Never merges — that is the developer's responsibility. Use for any feature that touches multiple files or layers (util, store, component).

Use when debugging the live production server, SSHing into the VPS, checking Docker Compose services, inspecting logs, comparing deployed config against the repo, navigating panino.sh paths, or triaging deployment drift on the production host. Helpful for signup/auth failures, env mismatches, nginx/static asset issues, and fast server navigation.