project-health-checklisted

# Project Health Check ## What this is Three checks on the health of a built project: a QA pass on what breaks with real users, a security pass on everything public, and a regression check for changes to working code. The outcome is a ranked fix list, worst first. ## When and why to use it Use it any time you want to know where the build stands: before it goes live, after a stretch of fast building, before handing the project to someone, or when a fix lands in working code. It answers the plain asks: "check my project", "test the project", "do a QA", "how healthy is this", "is it safe to put online", and "will this change break something". Each check returns findings ranked by what bites first, so limited time goes to the right problems. ## This skill runs the methods of the UX + AI MCP Each check is a method served by the UX + AI connector. This file only routes; the methods do the work, and they improve on the connector without this file changing. ## How it works 1. **Check the connector.** The UX + AI MCP must be connected on a subscribed account. If it is unavailable, say so and stop. 2. **Establish what the project is and what prompted the check.** Keep the first reply short: ask for the material and nothing else. 3. **Fetch by id and follow the text exactly as returned.** These are the three methods this skill runs; never rebuild one from memory or from this file. ``` fetch(id: "ship-readiness-qa") fetch(id: "security-and-secrets-first-pass") fetch(id: