17 docs tagged with "schema"

Stack-agnostic accessibility model: roles, ARIA, landmarks, labels, keyboard maps, focus management, and contrast targets.

Framework adapters that translate VibeSpec Core (brief, intent, tokens, layout, motion, a11y, interaction) into concrete stack outputs without constraining the spec.

Describes an agent’s identity, capabilities, IO, tools, and security.

Declares backend endpoints, contracts, IO shapes, and auth.

Outlines frontend, backend, data, auth, storage, deployment, and dependencies.

Defines data entities, fields, indexes, and relations used by the project.

Describes environments, CI, domains, secrets, and deployment settings.

Stack-agnostic design tokens following W3C Design Tokens format with themes/modes/brands and aliasing.

Stack-agnostic interaction model: events, guards, typed actions, keyboard and gesture mappings, and optional async state hooks.

Stack-agnostic layout primitives: stack/cluster/grid/frame with constraints, alignment, gaps, and responsive overrides.

Defines core project metadata, configuration, and structure for a VibeSpec project.

Stack-agnostic motion model: transitions (tween/spring/keyframes), choreography (stagger/order/overlap), presets, and reduced-motion behavior.

Captures project-level metadata, version, tags, env config, and extensions.

High-level, stack-agnostic guidance that expresses goals and freedoms so agents can design modern or cutting-edge UIs without enumerating specific widgets or stacks.

Stack-agnostic UI spec for pages, sections, components, props, variants, states, motion, interactions, responsiveness, and accessibility.

Stack-agnostic UI intent taxonomy so agents pick the right kind of component (purpose) without naming concrete widgets.

Specifies agent orchestration, graph structure, IO, and error handling.