stylist
stylist checks generated assets (HTML, Markdown, Word, PowerPoint, SVG, and raster images) against your house style guide and tracks conformance over time. It is built for the world where much of a company’s content is produced by AI agents: deterministic checks catch off-brand colors, fonts, banned terms, and outdated brand elements (superseded logos matched by perceptual hash, retired colors/fonts) at generation time, and every check feeds a central conformance dashboard.
How it fits together
Section titled “How it fits together” ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │ git hook │ │ Claude Code, │ │ CI / CLI │ ...adapters │ (pre-commit)│ │ Codex │ │ (stylist │ │ │ │ (PostToolUse)│ │ check dir/) │ └──────┬───────┘ └──────┬───────┘ └──────┬───────┘ └────────────┬─────┴──────────────────┘ ▼ ┌───────────────┐ embedded engine (local mode) │ core checker │ — or — │ │ core API server (api_url mode) └───────┬───────┘ ▼ ┌───────────────────────────────┐ │ check store (SQLite/Postgres)│──► conformance dashboard └───────────────────────────────┘- Adapters are thin. They gather content (staged git blobs, files an agent just wrote, CLI arguments) and hand it to the core checker. All rule knowledge lives in the core.
- The core is deployable three ways with the same binary: fully
local (embedded engine, no server), self-hosted (
stylist servein your VPC), or hosted SaaS. Adapters switch modes with one config value (api_url). - Every check is recorded. That is the dashboard’s data feed.
Documentation
Section titled “Documentation”| Page | What it covers |
|---|---|
| Getting started | Self-hosting: install, first check, first blocked commit |
| Getting started (hosted) | Hosted customers: point the CLI at your account |
| Configuration | .stylist.yaml, environment variables, precedence |
| Rulesets | The YAML rule schema, incl. outdated-asset and image rules |
| Baselines | Adopting stylist in a repo with existing violations |
| Hooks & CI | git pre-commit, Claude Code, Codex, hook managers, CI mode |
| Server | The core API: endpoints, auth, hot reload, check log |
| Database | SQLite vs Postgres, migrations, DBA workflow |
| Dashboard | The conformance dashboard and sign-in |
| Licensing | License keys and vendor tooling |
| Development | Repo layout, conventions, extending stylist |