define-quality-standardslisted

# Purpose Decide what "good" means for this project up-front so the scaffold can include the right guardrails from day one. # Questions to ask (in order) 1. Code style: existing style guide (company, open-source convention) or pick language defaults? 2. Linting and formatting tools per language. 3. Testing strategy: which levels apply (unit, integration, end-to-end) and rough coverage expectation. 4. Test frameworks per language. 5. Security baseline: dependency scanning, secrets management, SAST, auth testing, and whether to include a threat-modeling commitment (ask explicitly whether a threat model document should be part of the scaffold). 6. Accessibility target (for any UI): none, WCAG AA, or WCAG AAA. 7. Performance budgets: any hard numbers (page load, API p95 latency, memory ceiling, bundle size)? 8. Documentation expectations: README only, README plus ADRs, or full docs site. 9. Observability baseline: logs only, logs + metrics, or logs + metrics + tracing. 10. Profile opt-ins: which `profile-*` skills in the session workspace should this project follow? List skill names by exact name (e.g., `profile-java-database-access`). Leave empty if none apply. If the user is unsure, glob `<SESSION_DIR>/.claude/skills/profile-*/SKILL.md` and show the names plus their description lines so the user can pick. Use `AskUserQuestion` where multiple choice fits. # Solution space to present - **Test pyramid shapes**: heavy unit / balanced / heavy integration or E2E. Tradeoff: feed