AI / Agent Resources 1.4.0

Machine-readable discovery for VelinStyle 1.4.0: manifests, skills, components, Atelier, CLI diagnostics, and SAFE/REVIEW boundaries. Twin: Deutsch · AI Skills · Agent workflows.

Do not invent capabilities. Use only registry skills, generated component docs, Atelier catalog fields (id/title/href, plus optional related when match: "direct"), and Phase 5 scanner semantics. Candidate ≠ Apply. links/* stays Detect-only.

Discovery hierarchy

.well-known/ai.json
        ↓
/dist/velin-agent.json
        ↓
/dist/llms.txt
        ↓
Skills · Docs · Components · Atelier · CLI

/.well-known/ai.json — thin entry pointer
/dist/velin-agent.json — full agent manifest (MIME application/vnd.velinstyle.meta+json)
/dist/llms.txt — LLM entry + site overlay (no second skill inventory)

Version

Public agent discovery targets VelinStyle 1.4.0. Check framework.version in velin-agent.json. Skills registry version remains 1.0.0 (language-neutral skill IDs).

Skills

Source of truth: @birdapi/velinstyle/skills-registry (registry 1.0.0)
Manifest projection: velin-agent.json → skills (count, categories, capabilities, items)
CLI: npx velinstyle skills list|show|run|install · npx velinstyle workflow …
Human docs: AI Skills (EN) · AI Skills (DE) · Agent workflows
Public skill prose: generated Markdown mirror at docs/generated/skills/<skill-id>/SKILL.md (from registry prosePath). Manifest field proseHref points there. Package prosePath remains for CLI/npm. No per-skill HTML pages; do not invent DE skill IDs.

Components

Generated Web Component API (minimal HTML when SoT allows; attributes, events, slots, a11y)
Design intelligence JSON (purpose, variants, examples where present)
Human docs under docs/components/
CSS primitives (not WC tags): e.g. buttons use .velin-btn — see buttons.html / buttons-de.html. There is no <velin-button> tag; do not invent one.

Missing fields are gaps — do not invent relatedSkills or undocumented APIs.

Atelier

Atelier home · Library
Public machine catalog: docs/generated/atelier/catalog.json (mirror of CLI SoT cli/atelier-catalog.json)
Base fields always: id, title, href (showcase/template character — not a component API contract)
Optional related: only for DIRECT CE matches (match: "direct") — currently 7 Atelier → Component doc links. Absence of related means no proven link (covers AMBIGUOUS and MISSING). Do not invent relationships from titles or filenames.

CLI / Scanner / Diagnostics

CLI docs (EN) · CLI (DE)
Generated rules index: scanner.md (may lag)
Machine-readable scan-policy.json (SAFE / detect-only / review-only from Apply gates)
Detect ≠ Fix ≠ Apply. Findings may include additive diagnostic (source, resolution, reason, candidates).

SAFE / REVIEW / CANDIDATE / BLOCKED / UNKNOWN

Signal	Meaning	Auto Apply?
SAFE	Existing SAFE fix + Apply gates (`html-lang`, `skip-link` with `id="main"`, `safe-external-link`, `z-index-token`, `hardcoded-email`)	Only via official Apply / `--fix-dry-run`
REVIEW	Developer decision required	No
CANDIDATE	Suggestion in `diagnostic.candidates`	Never — does not set `fixable: true`
BLOCKED	No safe automated action (e.g. Apply reject, `links/*`)	No
UNKNOWN	Runtime/AT not statically proven	No

links/local-href-target and links/local-fragment-target are Detect-only. candidatesSummary: exact still ≠ Apply.

Example agent workflow

Task: “Create an accessible VelinStyle page.”

Read /.well-known/ai.json → /dist/velin-agent.json → /dist/llms.txt
Resolve skills via registry / skills in the manifest (e.g. a11y checklist, scan/fix, focus/keyboard, components a11y map) — do not invent IDs
Read generated component docs + intelligence JSON as needed
Optionally browse Atelier templates; follow related only when present with match: "direct"
Author with documented velin-* utilities and components
Run npx velinstyle scan (and related CLI as documented) Machine results: --json or --sarif (same findings; Candidates ≠ Apply).
Interpret diagnostics; apply only SAFE + fixable: true through the official pipeline
Report remaining REVIEW / CANDIDATE / BLOCKED / UNKNOWN items

EN / DE

Registry and skill IDs stay language-neutral. Human guides use EN/DE twins (*-leitfaden.html / *-de.html). Do not invent German skill pages when only English prose exists.

Partner / Motion AI (PixVerse)

Optional AI video for Motion Clips is documented as a partner guide (not a skill). Discover via Search, Docs Nav, or agent manifests:

PixVerse partner setup (EN) · PixVerse (DE)
Velin Motion Clips (EN) · Motion Clips (DE)
Manifest pointers: documentation.guides.pixverseEn / pixverseDe in velin-agent.json; resources.pixverseGuideEn / pixverseGuideDe in /.well-known/ai.json
Affiliate signup links use rel="noopener sponsored" — scanner SAFE requires noopener; keep sponsored; do not force noreferrer for attribution