@bdelanghe/brand-tools

@bdelanghe/brand-tools

Analysis tooling for @bdelanghe/brand — token coverage, content strings, accessibility and page meta.

These are checks, not runtime code. They read a built surface (a dist/, a CSS directory) and compare it against brand's tokens and contracts.

npm i -D @bdelanghe/brand @bdelanghe/brand-tools

command	what it checks
brand-coverage --colors --check <dir>	every colour in the surface is a token, not a literal
brand-content --check <dir>	content strings validate against brand's schema; copy lint
brand-a11y	token contrast pairings hold
brand-meta <dir>	every page carries the required meta

Why it is a separate package

These scripts lived in brand/tools/ and were consumed by checking out brand's source — because they are CI-internal analysis, not a distributable asset, and brand's package had no business shipping them to every consumer.

Splitting them means brand ships tokens and assets only, and a consumer that wants the checks asks for them. @bdelanghe/brand is a peer dependency: these tools check whatever brand version you installed rather than pulling in one of their own.