Skip to content

goodbones

Write down how your repository is meant to be built, in one file, and have oxlint and a CLI enforce it.

Describe each folder’s imports, exports and files in one manifest, and lint every change against it.

One manifest

Rules sit at the folder they govern, so the file reads like a directory listing. Read the overview →

Real resolution

Rules match the file an import resolves to, through your tsconfig paths and workspace links. How resolution works →

Tight by default

A folder admits only the files and imports you list. Loosening a rule is always explicit. Read about inheritance →

Every rule proves itself

The plugin refuses to load if a rule can no longer match anything. How probes work →

Adopt gradually

Record today’s violations in a baseline; the build fails if the count grows. Adopting a policy →

Editor and CLI

Get feedback in the editor through oxlint, or check the whole repository with the CLI. CLI reference →

Track a multi-step refactor in the same manifest, and see how far each part of the code has moved.

A refactor you can measure

Each objective lists every place its pattern still occurs. The list only shrinks. Read the introduction →

A plan written as you learn

Define the phases you know now and leave the rest open. How phases work →

A nudge on every change

Anyone who touches the code is told what would move it to the next phase. Read about the nudge →

See both, live: the tree with the manifest laid over it, and every campaign’s ladder, redrawn as the code changes.

The Architecture Browser

Hover a file and its imports, importers and governing node light up; the manifest is beside it, line for line. Read the introduction →

The Campaign Browser

Phases, objectives and sectors as a ladder, with every holdout, note and nudge under the pointer. Running it →