project-profilelisted

# Project Profile Use this independent Skill when the project profile is missing, draft, stale, or in conflict. It owns profile facts and template selection; it does not scaffold an application or initialize the rest of the project. ## User interface Most users only need these commands: ```text $project-profile $project-profile init $project-profile profile $project-profile components $project-profile status $project-profile update ``` `$project-profile` is a read-only navigator: it explains `init`, the two peer maintenance commands, `status`, and `update`; it does not run an implicit flow. `$project-profile init` is the explicit guided initializer for a new project: it performs one scan, asks a small set of high-impact decision cards, builds an editable proposal for both domains, and writes only approved layers. `$project-profile profile` owns project-profile maintenance. `$project-profile components` owns UI component-catalog maintenance; either command performs and persists the shared maturity assessment when it is missing. `status` is read-only and reports both domains. `update` rescans a project and coordinates the two domain interviews without silently switching templates or overwriting confirmed values. Internal stages (`inspect`, `plan`, `confirm`, `apply`, `migrate`, `validate`) may be used by an orchestrator, but are not required knowledge for normal users. ## Required behavior: init 1. Confirm this is a new/unformed project from the maturity scan. This init