Path A · CLI mega-command
One command, end-to-end. Pick this if you'd rather watch a terminal than click through a wizard. Handles testid proposals, workspace init, the pipeline run, and category seeding.
Two paths get you to the same place: a CLI mega-command that drives the whole pipeline end-to-end, or a six-step portal wizard that walks you through it. Both produce a real generated article on the other side.
One command, end-to-end. Pick this if you'd rather watch a terminal than click through a wizard. Handles testid proposals, workspace init, the pipeline run, and category seeding.
Six-step UI that runs the same operations behind the scenes, with previews at every step. Pick this if you want to inspect Quill's proposals before approving them.
One invocation. testids → init → pipeline → categorize. Drop a relative or absolute path to your repo on disk.
$ quill onboard ./path/to/your-appWant a dry-run first? Add --dry-run — Quill prints every action it would take without writing to disk.
$ quill onboard ./your-app --dry-runSame operations as the CLI, surfaced as a Linear-style wizard. Each step previews its proposals before you approve.
Confirm prerequisites and pick the brand presets that'll apply to every generated article. Defaults are sensible — you can override later from Settings → Branding.
Point Quill at the absolute path to your application on this machine. We validate it's a recognized framework (Next.js, Remix, etc.) before letting you continue.
Tell Quill how to log in to your app — form fields, dev credentials, or skip if your app has a public surface to document. The runner uses this to reach authed routes.
Quill scans your routes and components, proposes a feature catalog, and shows you the diff. You approve the features that should ship articles; the rest stay off the queue.
Quill proposes data-testid attributes for interactive elements that lack them. Review and apply in-place — the runner depends on stable selectors, never on CSS classes or text content.
Quill executes the pipeline against your selected features. Live progress streams in the portal. When it lands, you've got a real article queued for review.
Quill re-runs the relevant slice of the pipeline whenever main changes. For self-serve, run quill from a CI step on push to main; the queue picks up the deltas.
Open the portal → Articles. Each draft has a side-by-side preview, regenerate button, and a per-step diff against the source. Approve, edit, or reject.
The mega-command is one of seven CLI subcommands. The CLI reference breaks each one down with examples.