Blueprint turns one architecture definition into executable ESLint rules, a human handbook, and coding-Agent guidance. It gives React and Vue projects one durable place to describe boundaries that people, automation, and Agents can all use.
Blueprint supports both layer-first and module-first architectures. It enforces dependency direction, ownership, import boundaries, and selected code-shape rules; it also provides inspection, dependency, impact, and baseline tools for adopting those rules in existing projects.
Choose the topology for first adoption:
npx @kekkai/blueprint init --topology layer-firstnpx @kekkai/blueprint init --topology module-firstA proven-empty React or Vue application starts from the framework preset's complete canonical governance; module-first opens it as an empty runway with no invented domain module. Existing source gets an authoring playbook that adopts its current intent safely and ratchets pre-existing debt: a floor you can tighten later, not the recommended ceiling.
The resulting valid Blueprint config becomes the repository topology authority. Later topology changes use guarded transformation flows; see the documentation before applying them.
npx @kekkai/blueprint@latest upgrade --dry-run
npx @kekkai/blueprint@latest upgradeThe running release is the upgrade target. upgrade resolves every release's
upgrade operations up front, runs deterministic migrations in code, hands any
remaining semantic work to your coding Agent as one playbook, and records the new
lifecycle only after inspect and doctor pass. A bare npm update is not a
Blueprint upgrade. Supported sources start at 3.2.
npx blueprint remove --dry-run
npx blueprint removeremove deletes only what Blueprint can prove it owns, reverses recorded shared-file
edits, stops before any change when ownership is ambiguous, and uninstalls
@kekkai/blueprint last. Run it before uninstalling the package.
init --dry-run previews planned effects. Depending on the project and workflow,
Blueprint may regenerate its own outputs, merge managed sections into shared files,
or intentionally migrate a supported legacy config. Dependency installation uses
the detected package manager. An explicitly selected Agent may participate in
authoring or transformation; scaffold-only paths may use the selection only to
choose emitted Agent contracts.
Created by Taco Chang — Resume · LinkedIn
MIT © taco3064