Prompt scaffolding beta 1.2.2

Plan first, then render. Full pages use the Prompt Engine (page registry + blueprints). Fragments still use recipe intents. Deutsch: Prompt-Vorlagen

Maturity: This surface is beta / foundation in VelinStyle 1.2.0 — usable now; schemas and coverage still expanding. CSS / Web Components / runtime remain stable. Studio and the complete Utility Engine stay planned.

When to use

Prototype full pages or fragments from a natural-language prompt before hand-tuning HTML.
Run plan → scaffold → review → scan as a beta workflow.

When not

Do not ship scaffolded HTML without human review for a11y, SEO, and brand.
Do not claim this is Studio or a finished AI design system.

Commands

velinstyle plan "Steuerberater Landingpage mit Kontaktformular"
velinstyle scaffold "Steuerberater Landingpage mit Kontaktformular" -o out.html --json
velinstyle review out.html --prompt "Steuerberater Landingpage mit Kontaktformular"
velinstyle scaffold list-intents
velinstyle scaffold "Navbar with logo and search" -o nav.html

Pipeline (1.2.0)

Prompt → intent / page type → sections → design constraints → HTML → review (design, a11y, SEO, performance, conversion, prompt score).

Review hero CTAs: design.hero-cta-max counts real <a>/<button> with velin-btn--primary|outline inside the hero scope (#hero, data-velin-section="hero", or prefix until id="services|faq|testimonials"). Scripts, styles, and <velin-code-block> samples are ignored so Velin-Meta JSON cannot inflate the count.

Fragment intents

navbar, modal, card, dashboard, login, footer, pricing, empty-state, hero, table, onboarding — DE/EN keywords for small compositions.

Page types

Landing, lawyer, healthcare, SaaS, dashboard, shop, and more — see core/meta/pages/registry.json and velin-agent.json.

Workflow

plan → scaffold → review → layout suggest → scan → integrate.