CLI 1.2.2

Build custom CSS, manage icons, print HTML blueprints, compile design tokens, and scan your project for security and accessibility issues — all from the command line. Deutsch: CLI

When to use

• Build custom CSS, scan HTML, audit performance, and generate docs / search indexes.
• Use plan → scaffold → review for experimental prompt→HTML workflows (beta).

When not

• Do not treat plan/review/meta as a finished AI design system or Studio product.
• Do not invent Utility Engine CLI commands that are still planned.

Installation

Install VelinStyle globally or run it on-demand with npx:

# Install the published package
npm install -D @birdapi/velinstyle

# Or run without installing
npx @birdapi/velinstyle
# binary name: velinstyle

Commands Overview

All available commands at a glance:

Init

Creates a velinstyle.config.js file in the current directory. The interactive prompt lets you select which CSS layers to include:

velinstyle init

This generates a config file with your chosen layers, theme, output path, and scan settings.

Build

Builds a custom CSS bundle based on the layers defined in your config file.

# Build using velinstyle.config.js
velinstyle build

# Specify output file
velinstyle build --output dist/styles.css
velinstyle build -o dist/styles.css

# Minify the output
velinstyle build --minify

# Marketing lite layers
velinstyle build --preset lite -o ./velinstyle-lite.css --minify

# Production Builder (content-aware — preferred for go-live)
velinstyle build --production --explain
velinstyle production . -o ./dist/velin-production

Production

Alias command for the Production Builder. See Production Builder guide.

velinstyle production [path] --out ./dist/velin-production --explain --watch --report ./report.json

Velin Experience

Velin Experience is the product layer behind the velinstyle entrypoint — Output Contract, Event Bus, Registry-driven Help, Themes/Modes. The full CLI surface renders through Experience; the binary is only the door. Raw stdout stays for pipes / CI (--json, --sarif, blueprint without -o).

• Modes: compact · standard · dashboard · verbose · debug · json · sarif · markdown
• velinstyle dashboard — project overview
• --record + velinstyle replay <record.json> — capture and replay
• Config: velinstyle-cli.json (theme, output, analytics, record)

velinstyle doctor .
velinstyle themes
velinstyle skills list
velinstyle dashboard
velinstyle doctor . --record
velinstyle replay .velin/records/doctor-….json --output markdown

Guide: Velin Experience. Production Content Scanner treats .blade.php as first-class (scan your project, not only HTML).

Human vs machine output

Experience modes: compact · standard · dashboard · verbose · debug · json · sarif · markdown. Use --quiet / -q to suppress the branding footer (Experience still prints the contract body; prefer --json / --sarif / --compact for CI).

Scan machine output: velinstyle scan … --json or --sarif / --format sarif bypasses Experience and emits scanner findings (rule, message, location, fixable, optional diagnostic, optional autoFix). No branding footer. Human Experience scan shows a compact table (Sev · Rule · Apply · Why · Message) plus SAFE/review counts — full diagnostics remain in --json / --sarif.

Branding footer (human terminal / Experience render only):

Built with VelinStyle · Powered by SKYLITE.DESIGN
Danke, dass du VelinStyle nutzt.

The footer is not emitted for --json, SARIF, compact, markdown, or --quiet — so pipes and CI stay machine-clean.

Velin Security Suite

Velin Security Suite is the CLI surface; Velin Security Engine (core/security/) holds the Registry and rules. Auto-detect repo vs consumer; focused subcommands for CI, deps, secrets, and publish gates.

• doctor · scan · audit · publish · ci · deps · secrets · report
• Scores: Security Score · Dependency Health · Release Health · Timeline
• Flags: --repo · --consumer · --json · --strict

velinstyle security doctor .
velinstyle security deps .
velinstyle security publish
velinstyle security report --out ./.velin/security/report

Guide: Velin Security Suite · since 1.2.3.

Velin Motion

Page Motion is the Motion Design System — full Registry (presets, timelines, transitions, physics stubs, composers, triggers, policies, blueprints) plus a first-class Trigger Engine. Studio-ready data model; Studio UI later.

• 1.2.6: list · presets · doctor · scan · policy · demo
• 1.2.7: analyze · review · report · optimize · blueprint
• Attrs: velin-motion + velin-trigger (+ timeline / sequence)

velinstyle motion list
velinstyle motion doctor .
velinstyle motion analyze .
velinstyle motion blueprint landing -o motion.html
velinstyle motion demo

Clip Motion (1.3.0) — image→clip via package @birdapi/velinstyle-motion (local HTML/CSS or optional PixVerse AI). Separate from Page Motion.

AI animations are produced by external providers. PixVerse is a supported provider.

• Create / wizard: motion create · shortcuts zoom · pan · rotate · particles
• Batch / compose: atelier · transition · sequence · export · usage
• Providers: motion providers · setup: motion setup pixverse
• Presets: motion presets --clips
• Flags: --ai · --style ai · --yes · --provider

velinstyle motion providers
velinstyle motion setup pixverse
velinstyle motion create hero.png --preset cinematic --yes
velinstyle motion create logo.png --ai --yes
velinstyle motion atelier ./assets --count 10 --yes
velinstyle motion presets --clips
velinstyle motion usage

Guides: Velin Motion · Motion Clips · PixVerse partner setup (account · API key · affiliate context).

Windows notes

On Windows, velinstyle build loads velinstyle.config.js via pathToFileURL so drive-letter paths do not throw ERR_UNSUPPORTED_ESM_URL_SCHEME. Run velinstyle doctor to smoke-test the config import. Prefer relative vendor paths (vendor/velinstyle/) over absolute /dist/... sprite URLs.

Unknown CLI verbs print Unknown command '…' with suggestions and exit 1 (they no longer dump full help with a success-looking exit).

create landing copies vendor into the target directory and aims for a zero-warning scan (no inline styles; proper label for/id). Prefer bootFromDOM / runtime tree-shake in production; the scaffold falls back to the vendor components bundle offline.

Icons

Manage icon providers and generate optimized icon bundles.

Subcommands

# List all available icon providers
velinstyle icons list

# Add icons from several providers (downloads into icons/svg/ in the package)
velinstyle icons add lucide --icons menu,search,check
velinstyle icons add heroicons --icons arrow-left --variant outline

# Rebuild the combined sprite used by the framework
velinstyle icons build

# Remove every SVG that was downloaded from one provider, then rebuild
velinstyle icons remove heroicons
velinstyle icons build

Run these commands from the root of a VelinStyle clone (or ensure icons/svg/ resolves to your project). After icons build, referenced sprites are updated for local development.

Blueprint

Print copy-paste HTML wired for VelinStyle classes and tokens. Run velinstyle blueprint list for the machine-readable list, then emit one fragment with blueprint <id> (stdout or -o).

velinstyle blueprint list
# Example output shape (IDs only — exact order may vary):
#   alert-stack
#   breadcrumb-bar
#   card-grid
#   footer-simple
#   form-contact
#   form-login
#   hero-section
#   layout-dashboard
#   modal
#   navbar-header
#   pagination-bar
#   search-field
#   sidebar-layout
#   table-responsive
#   bottom-nav-mobile
#   cookie-consent
#   empty-state
#   filter-bar
#   notification-center
#   onboarding
#   pricing-table
#   settings-panel

velinstyle blueprint hero-section -o snippets/hero.html
velinstyle blueprint sidebar-layout -o snippets/sidebar.html

Tokens build

Reads JSON with a tokens map (keys become --kebab-case custom properties) and prints CSS or writes --output.

velinstyle tokens build --input tokens.json --output src/tokens-from-json.css

Blueprint catalog

Run velinstyle blueprint list for the authoritative list. Each id prints a static HTML fragment you can paste into a page or Storybook.

Migrate (Tailwind → VelinStyle) 1.4.0

Honest Tailwind migration. Dry-run by default. See the full guide: Tailwind migrate · Migration Intelligence · package @birdapi/velinstyle-tailwind · limits.

velinstyle migrate tailwind ./my-project
velinstyle migrate tailwind ./my-project --compat tailwind
velinstyle migrate tailwind ./my-project --compat tailwind --heuristic palette-roles
velinstyle migrate tailwind ./my-project --write
velinstyle migrate rollback ./my-project
velinstyle migrate acceptance ./my-project --show
velinstyle migrate rewrite-manifest ./my-project --preflight
velinstyle migrate rewrite-manifest ./my-project --dry-run

Intelligence residual --apply requires GATE_READY + DRY_RUN_OK and freigegebene Manifest entries (pilot SAFE_REWRITE = 0).

Prefix

Mechanical migration of class / className attributes in HTML, Vue, JSX, and TSX. Dry-run by default; use --write to apply.

velinstyle prefix ./src
velinstyle prefix ./src --write
velinstyle prefix ./src --bootstrap-display --write
velinstyle prefix ./src --map ./velinstyle-prefix-map.json --write

See also Migration guide.

Scaffold beta

Compose blueprint HTML from a text prompt (no API key). Full pages use the page registry; fragments use recipe intents. Guide: Prompt scaffolding.

velinstyle scaffold list-intents
velinstyle scaffold "Navbar with logo and search" -o nav.html
velinstyle scaffold "Steuerberater Landingpage mit Kontaktformular" -o out.html --json
velinstyle scaffold --atelier 04,07 -o compose.html --from ./atelier/library

Atelier compose (beta): --atelier builds a page from curated Atelier Library ids (not Velin Studio — Studio stays planned). See Atelier pull below.

Atelier pull

Pull a curated Library showcase by number or id (36 → 36-calendar). SEO variants like 3600-… are not matched.

velinstyle atelier list
velinstyle atelier 36 -o ./velin-atelier/36-calendar
velinstyle atelier 04 --format vue -o ./src/atelier/04-pricing

Plan beta

Emit structured page plan JSON (sections, constraints) without rendering HTML. Foundation for Design Intelligence — coverage still expanding. With --atelier, emits Library compose plan refs (beta).

velinstyle plan "SaaS pricing page with FAQ" --json -o plan.json
velinstyle plan --atelier 04,07 -o atelier-plan.json

Review beta

Heuristic review gate (design, a11y, SEO, performance, conversion, prompt score). Not a substitute for human WCAG or security review.

velinstyle review out.html --prompt "SaaS pricing page with FAQ" --json

Meta beta

Build agent context artifacts. Knowledge Graph embeds are a seed catalog, not a complete design system. Guide: Velin-Meta.

velinstyle meta
velinstyle meta --base-url https://velinstyle.info
velinstyle meta page docs/components/buttons.html --write
velinstyle docs generate --scope meta

Performance audit

See Performance audit guide.

velinstyle perf audit ./public
velinstyle perf suggest ./public
velinstyle perf fix ./public --write

Docs generate

Extract Markdown API tables from source (components, tokens, utilities, CLI manifest, scanner rules). Output: docs/generated/ in the framework repo — browse snapshot locally.

npm run docs:generate
velinstyle docs generate
velinstyle docs generate --scope components
velinstyle docs generate --scope tokens

Scopes: all, components, attributes, tokens, utilities, cli, rules, a11y, meta.

Search index (extension)

Build dist/search-index.json for VelinSearch. Merged with site pages via python tools/build-search-index.py.

velinstyle search index --out dist/search-index.json
velinstyle search index --extra-html ../velinstyle-site/docs

Layout audit

Static checks for flex, grid, containers, and mobile visibility. Full guide: Responsive layout.

velinstyle layout audit ./src
velinstyle layout suggest page.html
velinstyle layout fix page.html --dry-run
velinstyle layout fix page.html --write

Scan

stable tooling — complementary to beta plan/review; use in CI.

A built-in scanner that walks HTML, CSS, and JavaScript for security, accessibility, CSS hygiene, and local link integrity. Use --severity to set the minimum level shown (errors always fail CI when present).

Pipeline (one engine): Detect → Diagnostic → Candidate (review) → Fixability → Dry-Run → Apply. A finding alone is never Apply permission. Diagnostic candidates are review-only (exact ≠ auto-fix). Only the SAFE set below may write files, and only after fail-closed re-validation.

In the framework repository, npm run test:contrast verifies OKLCH token pairs (4.5:1 / 7:1) — complementary to velinstyle scan.

# Scan current directory
velinstyle scan

# Scan a specific path
velinstyle scan ./src

# Output as JSON (useful for CI/CD)
velinstyle scan --format json

# SAFE Apply only when policy + fixable gates pass (candidates ≠ Apply)
velinstyle scan --fix

# Filter by severity
velinstyle scan --only pii --fix

velinstyle scan --severity error

# Preview SAFE plans without writing (JSON: autoFix.plans / rejected)
velinstyle scan --fix-dry-run

# Local link integrity only (Detect — never auto-rewrites paths)
velinstyle scan --only links

# Default lang when fixing missing <html lang> (BCP 47)
velinstyle scan --fix --fix-lang en

Diagnostics & candidates

Selected rules attach a structured diagnostic object (reason, source, resolution, optional candidates / related). Candidates point at existing targets for human review. They do not invent ids, labels, or paths, and they never authorize Apply — even with confidence exact.

There is no finding-level action field and no separate fixability object. Use fixable plus Dry-Run plans to decide writes.

Link integrity

Static checks against the scan root only: relative and root-relative local HTML paths (directories resolve via index.html / index.htm), and #fragment ids in the target document. Skips external URLs, templates/dynamic refs, and does not perform Live-HTTP checks. Both rules stay fixable: false — no automatic start→index, EN↔DE, fragment invention, or generator bulk rewrites.

JSON and SARIF

--json prints the scanner payload. --sarif / --format sarif prints the same findings as SARIF 2.1.0 (ruleId, level, message, artifact URI + line, properties: fixable, safeApplyEligible, detectOnly, nested diagnostic). Candidates never imply Apply. Exit code 1 when error-severity findings remain (same as text/JSON).

SAFE Apply (only)

• a11y/html-lang — set missing <html lang>
• a11y/skip-link — insert skip link only when id="main" already exists
• security/safe-external-link — add rel="noopener noreferrer"
• css/z-index-token — map raw numeric z-index toward --velin-z-*
• pii/hardcoded-email — mask to placeholder

links/* and other a11y Detect rules are never applied automatically.

What scan does not claim

Static scan is not a full accessibility audit, not a screenreader test, and not a guarantee that every link or a11y issue is found or fixed. Pair with axe/Lighthouse and manual AT review for ship gates. Generator/site link problems belong in the site/generator layer, not as scanner special-cases.

Scanner rules

Severities label findings in text/JSON output. --severity sets the minimum level included (warning hides info only). Filter with --only security, --only a11y, --only links, --only pii, --only css, --only wc. Full IDs: see generated rules. Performance checks also run via velinstyle perf audit. Review remains beta / heuristic — pair with axe/Lighthouse for ship gates.

Security

PII

Accessibility

Link integrity

CSS

Performance

Configuration

The velinstyle.config.js file controls all CLI behaviour. Here is the full structure:

export default {
  layers: ['tokens', 'reset', 'base', 'a11y', 'layout', 'components', 'utilities', 'security', 'helpers'],
  theme: null,
  output: './velinstyle-custom.css',
  minify: true,
  scan: {
    enabled: true,
    severity: 'warning',
    fix: false,
    ignore: ['node_modules', 'dist'],
  },
};