niko-qalisted

# QA Phase - Post-Implementation Semantic Review This command performs a structured semantic review of the code just implemented against the original plan. It catches over-engineering, incomplete implementations, pattern violations, and implementation debris that mechanical checks (lint/build/test) cannot detect. ## Step 1: Load Memory Bank Files Read: - `memory-bank/active/tasks.md` - `memory-bank/active/projectbrief.md` - `memory-bank/systemPatterns.md` - `memory-bank/active/activeContext.md` - `memory-bank/active/progress.md` - `memory-bank/active/creative/` ## Step 2: QA Workflow 1. **Verify Prerequisites** - Check `memory-bank/active/tasks.md` for build phase completion - Read the original implementation plan to establish the review baseline - For Level 3-4: Read creative phase documents for design intent 2. **Review the code just implemented against the original plan and apply these constraints:** - **KISS**: Simplify over-engineered logic; flatten unnecessary abstractions or indirection layers introduced during the build. If a simpler construct achieves the same outcome, prefer it. Do not preserve complexity merely because it was part of the initial implementation approach. - **DRY**: Consolidate any duplicate code, boilerplate, or redundant patterns introduced during iterative development into clean, reusable constructs. Cross-reference new code against existing utilities and helpers to avoid reinventing what the codebase already provides.