Update project structure and documentation: Add new entries to .gitignore for standalone outputs and MCP config, delete obsolete design_skill.md file, and revise README and various skills to reflect updated workflow steps, including UI design and performance testing. Adjust paths in retrospective and metrics documentation to align with new directory structure.

.cursor/skills/problem/SKILL.md

@@ -46,7 +46,7 @@ The interview is complete when the AI can write ALL of these:
 | `problem.md` | Clear problem statement: what is being built, why, for whom, what it does |
 | `restrictions.md` | All constraints identified: hardware, software, environment, operational, regulatory, budget, timeline |
 | `acceptance_criteria.md` | Measurable success criteria with specific numeric targets grouped by category |
-| `input_data/` | At least one reference data file or detailed data description document |
+| `input_data/` | At least one reference data file or detailed data description document. Must include `expected_results.md` with input→output pairs for downstream test specification |
 | `security_approach.md` | (optional) Security requirements identified, or explicitly marked as not applicable |
 
 ## Interview Protocol
@@ -187,6 +187,7 @@ At least one file. Options:
 - User provides actual data files (CSV, JSON, images, etc.) — save as-is
 - User describes data parameters — save as `data_parameters.md`
 - User provides URLs to data — save as `data_sources.md` with links and descriptions
+- `expected_results.md` — expected outputs for given inputs (required by downstream test-spec skill). During the Acceptance Criteria dimension, probe for concrete input→output pairs and save them here. Format: use the template from `.cursor/skills/test-spec/templates/expected-results.md`.
 
 ### security_approach.md (optional)