Share Best Practice Profile

Publish a validated practice profile so others can install and use it.

Why This Is Best Practice

Adopted by: The eslint-config-* ecosystem (3000+ published configs on npm) and VS Code extension packs demonstrate the value of community-shared configuration bundles. A single eslint-config-airbnb install replaced thousands of manual ESLint rule configurations. Grimoire profiles follow the same pattern — one shareable file replaces manual skill selection for everyone who shares the same context. Impact: A shared profile eliminates onboarding friction for new team members and external contributors who need to activate the same practices. A profile shared publicly becomes a reusable community asset — the same leverage as an open-source library. Why best: Sharing without review leads to broken profiles that fail silently for others. The gate (review-best-practice-profile first) ensures what is shared actually works.

Sources: npm eslint-config-* ecosystem; VS Code extension pack format; Grimoire docs/profiles.md

Steps

1. Confirm the profile is reviewed

If review-best-practice-profile has not been run on this profile, run it now and resolve any FAIL results before continuing. Warnings are acceptable.

Review gate: Before sharing, review-best-practice-profile MUST have been run against this profile. If it hasn't been run this session, run it now. Do not skip this step — a profile shared without review may contain conflicts or missing fields that will confuse recipients. If the review produces FAIL findings, show them and require explicit user confirmation ('Share anyway? [y/n]') before proceeding.