Fitness Config Init

Create fitness-config.json for a project so the review skills weigh what matters for it. A database backend should count reliability and data heavily and accessibility barely at all. A public website should count accessibility first. This skill works out which kind of project it is looking at, proposes weights from a matching profile, and saves them only after the user has seen the proposal.

The weights themselves live in references/purpose-profiles.md and in the resolver. This file never states a weight. Always take numbers from the resolver output or the profile table.

References

• references/purpose-signals.md: what to read in the fast scan, the 40-file budget, signals per archetype, and what high, medium and low confidence mean.
• references/purpose-profiles.md: the six archetype profiles, the rules for adjusting them, and typical rationale for each.

Read both before step 3.

Resolver

Every config read and write goes through the resolver CLI. Never load fitness-config.json yourself and never write it with a file tool.