Lintel on GitHub Copilot. Generated from skills/generate-web/SKILL.md; edit the canonical file, then run
li-copilot init.
- Resource root:
../../.. from this skill's base directory (the Lintel source with bin/,
lib/, skills/). Write plans, state and evidence into the working repository's .claude/
tree, never into the resource root.
- Skill-relative paths: this skill's own
scripts/, references/ and data/ folders (and a
<base> that the workflow defines as its own directory) mean
../../../skills/generate-web/ in the Lintel source, not this generated folder.
${LINTEL_SKILLS_DIR:-skills} means the skills root, ../../../skills. A bin/li-run step
runs in the working repository, so use $LINTEL_SKILLS_DIR/generate-web/ there.
- Shell steps: run Bash snippets with Bash (Git for Windows'
bash.exe on Windows, never
System32\bash.exe). Save a snippet to a temporary .sh file and run
bash "<resource root>/bin/li-run" <file>; it prepares LINTEL_SOURCE_ROOT, LINTEL_REPO_ROOT
and the profile context.
- Tools: Read=
view, Write=create, Edit=edit, Bash=bash/powershell, Grep=grep,
Glob=glob, AskUserQuestion=ask_user, TodoWrite=the plan checklist, Task or a named role=task
with that custom agent, WebFetch=web_fetch.
- Other Lintel workflows are native skills: invoke
/li-<name> rather than reading their
files. Named roles such as CodeReviewer are custom agents.
/generate-web
Web artifact generation with --mode artifact|mockup; default artifact
preserves the existing brief/pipeline/frontend-design routes below.
- Mockup mode: follow the mockup procedure for
--brief, --reference, --tokens, --inherit-project, --copy-tier,
--out and optional --preview. It implies single-file: actual static HTML,
inline CSS/minimal JS, no framework or build step.
- Artifact variants:
single-file is self-contained HTML; nextjs-scaffold
is a multi-file project with routes and components, not a deployment.
Use only explicitly selected or verified-profile templates and available project
resources. A named template is not proof a bundled skeleton exists.
The shared design contract is the
only input/argument/profile boundary. Template paths must be explicitly authorized;
their historic home convention does not permit personal-directory discovery.
When to use
- Customer-demo landing page (single-file for quick iteration; Next.js for deployable demo)
- Engagement-internal microsite (technical wiki, runbook viewer)
- Pitch artifact that needs to look modern + carry the active pack's brand
When NOT to use
- Static markdown — direct edit is faster
- Complex web app — Next.js scaffold is starter, not full product
- Slide artifact — use
/generate-ppt
Inputs
- Required
--brief <path|inline> — content brief OR --from-pipeline <dir> (Phase 2: shared pipeline mode) OR --from-frontend-design <dir> (v3.7 Phase B: frontend-design family integration)
- Required
--variant <single-file|nextjs-scaffold> in artifact mode; mockup implies single-file
- Optional
--audience <text> — primary audience
- Optional
--use-defaults — force in-repo default templates
- Optional
--preview — after generation, use /web-session --mode open on an owned admitted preview
- Optional
--theme <name> — apply a pack-provided theme palette (default: neutral)
- Required explicit
--out <path> for owned output; optional --customer-share
is propagated from the director. Reject conflicting input modes, unknown or
duplicate options; direct --brief remains an entry point into the same contract.
From-pipeline mode (v3.5 Phase 2 — generate-pipeline integration)
If invoked with --from-pipeline <run-dir> instead of --brief:
Read shared pipeline-output:
<run-dir>/content.md — hero + sections + body with HTML-comment annotations
<run-dir>/design-spec.json — read per_format.web.sections for layout-mappings
- Validate its existing envelope plus resolved
web_design/binding through
design_contract.load_design. Preserve legacy readability, not fabricated
render readiness. Keep P12's document mappings intact.
Replace brief-parsing logic with direct-read of content.md sections + design-spec web-block-types (hero / sections / features / FAQ).
Apply format-specific design-pass via design_pass_hook:
- Reads
per_format.web.sections[N].design_pass_hook (canonical: WebExperienceCritic)
- Applies the web-specific fidelity method to the selected sections; the hook
name does not require another default post-generation reviewer
- Per Reviewer Concern #7: WebExperienceCritic stays web-specific, not lifted
CLI stays backward-compat: existing --brief-flag invocations work unchanged. --from-pipeline is additive.
4-gate pipeline runs as usual after generation.
From-frontend-design mode (v3.7 Phase B — frontend-* family integration, M-1 resolution)
If invoked with --from-frontend-design <run-dir> instead of --brief or --from-pipeline:
Read frontend-design output:
<run-dir>/frontend-design-spec.json — distinct filename from pipeline's design-spec.json, avoiding a schema collision. Verify "source": "frontend-design" + "schema_version": 1 before consuming.
- Embedded blocks:
typography, motion, nullable shader, component_libraries, layout_grammar, interaction_signature and visual_thesis.
Shared handshake: use design_contract.load_design with the external
prepared P05 context and explicit P07 configuration, then renderer_args.
Checking two JSON strings alone does not validate bindings, choices or policy.
Replace brief-parsing logic with direct-read of spec:
- Copy: preserve the bound brief/content; a visual thesis is design direction,
not a replacement for substantive source text, tables or limitations
- Typography: honor
typography.font_stacks[].loading_strategy through the
existing target's CSS/config; fetch or link external assets only when authorized
- Motion:
none emits no animation dependency; css emits only selected CSS;
library imports only the selected, sourced library and justified configuration.
- Shader: emit a selected GPU component only when
shader != null && shader.visual_thesis != "none" && shader.library != null.
Both null and the accepted non-null visual_thesis: none, library: null
representation emit no GPU canvas, import or dependency. Apply the same
predicate to pipeline web_design.shader; do not substitute an artificial score.
- Component libraries: preserve existing primitives; emit no setup/import when
the selected list is empty. New library advice requires source/version/license evidence.
- Layout: apply
layout_grammar.max_width + grid-config to root layout
- Interaction: apply selected smoothing only through its explicitly chosen
library/stack; native scrolling emits no smoothing dependency
Design-pass hook integration:
- Follow review ownership and reuse:
return actual produced output, input identity and observations to one
post-generation owner; do not run both critic aliases by default
frontend-design-review consumes that handoff and the original required
observations. An optional request cannot waive mandatory independent review,
and reuse requires the existing current-context reader/QA checks
CLI stays backward-compat: existing --brief + --from-pipeline-flag invocations work unchanged. --from-frontend-design is an additive third mode.
prefers-reduced-motion handling — always emit fallback per motion.perf_budget.fallback_for_prefers_reduced_motion field. Non-negotiable.
Mobile-strategy emission — apply the selected strategy through the actual
CSS/library mechanism; do not introduce GSAP solely to handle a media query.
4-gate pipeline runs as usual after generation.
Boundary with frontend- family (L-002):* generate-web is the rendering-engine — file-output. frontend-design is the design-director — decisions. generate-web does NOT make design-decisions; it READS them from frontend-design-spec.json + renders accordingly.
Workflow
Preflight gates — brand templates check, staleness, the active pack's compliance gates if customer-bound
Read brief + parse structure:
- Hero (title + subtitle + CTA)
- All substantive sections, preserving source detail rather than a fixed section cap
- Optional: features grid, FAQ, footer
Resolve direct brief input into the same frontend contract, pinning the existing
project/profile and retrieval evidence before rendering. With no handed-over lock, follow
the direct-entry steps in Reusable patterns before the first design
choice. No parallel private schema for this entry point.
Apply the WebExperienceCritic method for layout review BEFORE generation:
- Information hierarchy
- Accessibility (WCAG AA via existing AccessibilityChecker)
- Motion-language considerations
- Brand alignment
Use actual native delegation when available and authorized; otherwise label
the builder's pass as self-review. No actor or model is implied by this recipe.
3b. Stack-guidance pass (ADR-0015 — retrieval before rendering):
python3 "${LINTEL_SKILLS_DIR:-skills}/design-dna/scripts/search.py" "<layout/feature keywords>" --stack html-tailwind # or nextjs per variant
Apply the returned Do/Don't/Severity rules during generation. python3 absent → Read
design-dna/data/stacks/<stack>.csv (same root) directly.
Generate per variant:
- single-file: render the selected design as one HTML file with inline
CSS and only necessary authorized interactions
- nextjs-scaffold: use a selected compatible skeleton or the established
project structure; write routes/components and only justified manifest changes
Gate 0 + 4-gate quality pipeline (per /generate-ppt):
- Gate 0 (mechanical, ADR-0015): use the
design validator,
validate_design.check(content, path, profile_hexes) on actual HTML with the loaded design's resolved palette.
Hard errors such as zoom-disable, killed focus and emoji icons block;
off-palette/token findings retain their warning severity. Do not reconstruct
a bundled profile path that ignores a selected pack asset or brief override.
- Gate 1: voice (if customer-bound)
- Gate 2: brand-conformance
- Gate 3: honest-limitations (only if generating an AI-feature page with disclosure)
- Gate 4: provenance
Publish within scope: atomically write/read back the selected --out,
preserving an authorized replacement's preimage. Report actual checks and
blocked/unverified obligations; no draft move confers release clearance.
Optional preview through the shared browser operations on an authorized owned
local server. Verify health and actual session ownership first; provider availability
and URL admission are not established by this instruction.
Reusable patterns
Follow the reusable pattern consumer contract.
generate-web still makes no design decisions of its own; it renders the projected values.
Handed-over lock (from-frontend-design mode, or a direct run that is given a lock): run
li-pattern verify-lock on it against the current context before rendering. Only ok
continues. Then check the spec's pattern_context with validate_visual against that verified
lock, never against a stored report. A stale context, a mismatched setting or an unusable
selection blocks the render; it is not corrected here.
Direct entry without a handed-over lock (--mode mockup --brief, and the plain artifact
--brief route) resolves itself through the same contract. Do this before the first design
choice:
- Write the evidenced context, and turn explicit brief decisions about bound settings into
--overrides. Omit unknown facts, and never infer a target.
- Run
li-pattern resolve --context <ctx> [--overrides <file>] from the trusted source root.
empty: continue exactly as without patterns. Write no lock and no pattern_context.
ready: rerun the same command with --lock .claude/runtime/patterns/<run-id>/patterns.lock.json. The lock goes inside this repository
even when --out is elsewhere. Confirm the same selection_digest, then run
li-pattern verify-lock on the new lock against the same context; only ok continues.
Carry the full requirements and setting winners into the design choices.
- Any other status blocks the dependent design decision and the render:
needs-context,
conflict, unavailable (including a pack context in fallback or error) and
invalid. So does a run that prints no JSON report. Report the status; never
hand-write a lock, and never fall back to another source or renderer.
- Apply
$LINTEL_SOURCE_ROOT/lib/pattern_visual.py project_visual with the verified lock to
the synthesized design spec. This writes the final frontend-design-spec.json, with its
pattern_context, before that spec's P05 binding is prepared.
- Never project after binding: that would change bytes the bound context already selected.
- Load the bound spec with
design_contract.load_design and the current P07 configuration.
With a ready selection, pass pattern_lock and pattern_context, and select both files
plus .claude/patterns in the P05 context; this is what lets a verified pattern palette winner
outrank the pinned profile.
Run validate_visual against the verified lock before rendering; only passed
continues, and unknown settings stay open review items.
The mockup procedure's step 2 decision method and step 3 load follow these steps; see
mockup mode. Direct entry and cycle entry call the same command with the
same inputs, so they produce the same selection_digest. When the runtime reports no patterns,
rendering is unchanged.
Report format
Report mode/variant, exact source/design/output paths, selected profile/template,
retained content, actual rendering operations and mechanical/voice/brand/
limitations/provenance outcomes. State whether preview, keyboard, responsive,
reduced-motion and other required observations ran, with their actual evidence.
Missing browser or renderer coverage remains unverified, not a fabricated pass.
Compliance integration
- 4-gate pipeline is the customer-bound enforcement path; the specific gates are pack-configurable (
resolve_pack_field compliance.hooks; none by default)
- HTML/JS output sanitized — no inline scripts that fetch external resources without disclosure
- nextjs-scaffold retains applicable deployment requirements but triggers no deployment
Failure modes
- nextjs-scaffold template incomplete — block that requested target with the
concrete missing resource; do not silently change the requested artifact.
- Voice gate fails on customer-facing content — surface flagged paragraphs, allow regen
- Accessibility audit fails (contrast issue, missing alt text) — surface findings; require fixes before gate-2 passes
- Customer-data in brief — BLOCK
Examples
Single-file customer demo:
> /generate-web --brief demo-brief.md --variant single-file --out demo.html --preview
[Render; preview only through a verified owned server and authorized provider.]
Next.js scaffold:
> /generate-web --brief microsite-brief.md --variant nextjs-scaffold --use-defaults --out microsite
[Render a compatible scaffold; use existing tooling and authorized dependency restoration only.]
See also
BRAND-INTEGRATION.md
WebExperienceCritic agent
AccessibilityChecker (Layer 4) for WCAG audit
/web-session --mode open — preview the generated file through owned loopback
/frontend-design --mode variants — compare directions around a mockup
/generate-docs — produce source-grounded Markdown before a format handoff
- The active pack's deploy gate — wire Next.js deployment (pack-configurable)
1---2name: li-generate-web3description: Use to render a static HTML mockup, a profile-aware single-file page or a Next.js scaffold from a brief or the existing design/content contracts.4metadata:5 source: https://skillmd.com/skills/jokerman89/li-generate-web6---78> **Lintel on GitHub Copilot.** Generated from `skills/generate-web/SKILL.md`; edit the canonical file, then run9> `li-copilot init`.10> - **Resource root:** `../../..` from this skill's base directory (the Lintel source with `bin/`,11> `lib/`, `skills/`). Write plans, state and evidence into the working repository's `.claude/`12> tree, never into the resource root.13> - **Skill-relative paths:** this skill's own `scripts/`, `references/` and `data/` folders (and a14> `<base>` that the workflow defines as its own directory) mean15> `../../../skills/generate-web/` in the Lintel source, not this generated folder.16> `${LINTEL_SKILLS_DIR:-skills}` means the skills root, `../../../skills`. A `bin/li-run` step17> runs in the working repository, so use `$LINTEL_SKILLS_DIR/generate-web/` there.18> - **Shell steps:** run Bash snippets with Bash (Git for Windows' `bash.exe` on Windows, never19> `System32\bash.exe`). Save a snippet to a temporary `.sh` file and run20> `bash "<resource root>/bin/li-run" <file>`; it prepares `LINTEL_SOURCE_ROOT`, `LINTEL_REPO_ROOT`21> and the profile context.22> - **Tools:** Read=`view`, Write=`create`, Edit=`edit`, Bash=`bash`/`powershell`, Grep=`grep`,23> Glob=`glob`, AskUserQuestion=`ask_user`, TodoWrite=the plan checklist, Task or a named role=`task`24> with that custom agent, WebFetch=`web_fetch`.25> - **Other Lintel workflows** are native skills: invoke `/li-<name>` rather than reading their26> files. Named roles such as `CodeReviewer` are custom agents.2728# /generate-web2930Web artifact generation with `--mode artifact|mockup`; default `artifact`31preserves the existing brief/pipeline/frontend-design routes below.3233- **Mockup mode:** follow the [mockup procedure](../../../skills/generate-web/references/mockup.md) for34 `--brief`, `--reference`, `--tokens`, `--inherit-project`, `--copy-tier`,35 `--out` and optional `--preview`. It implies `single-file`: actual static HTML,36 inline CSS/minimal JS, no framework or build step.37- **Artifact variants:** `single-file` is self-contained HTML; `nextjs-scaffold`38 is a multi-file project with routes and components, not a deployment.3940Use only explicitly selected or verified-profile templates and available project41resources. A named template is not proof a bundled skeleton exists.4243The [shared design contract](../../../skills/design-dna/references/design-contract.md) is the44only input/argument/profile boundary. Template paths must be explicitly authorized;45their historic home convention does not permit personal-directory discovery.4647## When to use4849- Customer-demo landing page (single-file for quick iteration; Next.js for deployable demo)50- Engagement-internal microsite (technical wiki, runbook viewer)51- Pitch artifact that needs to look modern + carry the active pack's brand5253## When NOT to use5455- Static markdown — direct edit is faster56- Complex web app — Next.js scaffold is starter, not full product57- Slide artifact — use `/generate-ppt`5859## Inputs6061- Required `--brief <path|inline>` — content brief **OR** `--from-pipeline <dir>` (Phase 2: shared pipeline mode) **OR** `--from-frontend-design <dir>` (v3.7 Phase B: frontend-design family integration)62- Required `--variant <single-file|nextjs-scaffold>` in artifact mode; mockup implies single-file63- Optional `--audience <text>` — primary audience64- Optional `--use-defaults` — force in-repo default templates65- Optional `--preview` — after generation, use `/web-session --mode open` on an owned admitted preview66- Optional `--theme <name>` — apply a pack-provided theme palette (default: neutral)67- Required explicit `--out <path>` for owned output; optional `--customer-share`68 is propagated from the director. Reject conflicting input modes, unknown or69 duplicate options; direct `--brief` remains an entry point into the same contract.7071## From-pipeline mode (v3.5 Phase 2 — generate-pipeline integration)7273If invoked with `--from-pipeline <run-dir>` instead of `--brief`:74751. **Read shared pipeline-output:**76 - `<run-dir>/content.md` — hero + sections + body with HTML-comment annotations77 - `<run-dir>/design-spec.json` — read `per_format.web.sections` for layout-mappings78 - Validate its existing envelope plus resolved `web_design`/`binding` through79 `design_contract.load_design`. Preserve legacy readability, not fabricated80 render readiness. Keep P12's document mappings intact.81822. **Replace brief-parsing logic** with direct-read of content.md sections + design-spec web-block-types (hero / sections / features / FAQ).83843. **Apply format-specific design-pass via design_pass_hook:**85 - Reads `per_format.web.sections[N].design_pass_hook` (canonical: WebExperienceCritic)86 - Applies the web-specific fidelity method to the selected sections; the hook87 name does not require another default post-generation reviewer88 - Per Reviewer Concern #7: WebExperienceCritic stays web-specific, not lifted89904. **CLI stays backward-compat:** existing `--brief`-flag invocations work unchanged. `--from-pipeline` is additive.91925. **4-gate pipeline runs as usual** after generation.9394## From-frontend-design mode (v3.7 Phase B — frontend-* family integration, M-1 resolution)9596If invoked with `--from-frontend-design <run-dir>` instead of `--brief` or `--from-pipeline`:97981. **Read frontend-design output:**99 - `<run-dir>/frontend-design-spec.json` — **distinct filename** from pipeline's `design-spec.json`, avoiding a schema collision. Verify `"source": "frontend-design"` + `"schema_version": 1` before consuming.100 - Embedded blocks: `typography`, `motion`, nullable `shader`, `component_libraries`, `layout_grammar`, `interaction_signature` and `visual_thesis`.1011022. **Shared handshake:** use `design_contract.load_design` with the external103 prepared P05 context and explicit P07 configuration, then `renderer_args`.104 Checking two JSON strings alone does not validate bindings, choices or policy.1051063. **Replace brief-parsing logic** with direct-read of spec:107 - Copy: preserve the bound brief/content; a visual thesis is design direction,108 not a replacement for substantive source text, tables or limitations109 - Typography: honor `typography.font_stacks[].loading_strategy` through the110 existing target's CSS/config; fetch or link external assets only when authorized111 - Motion: `none` emits no animation dependency; `css` emits only selected CSS;112 `library` imports only the selected, sourced library and justified configuration.113 - Shader: emit a selected GPU component only when114 `shader != null && shader.visual_thesis != "none" && shader.library != null`.115 Both null and the accepted non-null `visual_thesis: none, library: null`116 representation emit no GPU canvas, import or dependency. Apply the same117 predicate to pipeline `web_design.shader`; do not substitute an artificial score.118 - Component libraries: preserve existing primitives; emit no setup/import when119 the selected list is empty. New library advice requires source/version/license evidence.120 - Layout: apply `layout_grammar.max_width` + grid-config to root layout121 - Interaction: apply selected smoothing only through its explicitly chosen122 library/stack; native scrolling emits no smoothing dependency1231244. **Design-pass hook integration:**125 - Follow [review ownership and reuse](../../../skills/frontend-design-review/references/built-review.md#review-ownership-and-reuse):126 return actual produced output, input identity and observations to one127 post-generation owner; do not run both critic aliases by default128 - `frontend-design-review` consumes that handoff and the original required129 observations. An optional request cannot waive mandatory independent review,130 and reuse requires the existing current-context reader/QA checks1311325. **CLI stays backward-compat:** existing `--brief` + `--from-pipeline`-flag invocations work unchanged. `--from-frontend-design` is an additive third mode.1331346. **prefers-reduced-motion handling** — always emit fallback per `motion.perf_budget.fallback_for_prefers_reduced_motion` field. Non-negotiable.1351367. **Mobile-strategy emission** — apply the selected strategy through the actual137 CSS/library mechanism; do not introduce GSAP solely to handle a media query.1381398. **4-gate pipeline runs as usual** after generation.140141**Boundary with frontend-* family (L-002):** generate-web is the **rendering-engine** — file-output. frontend-design is the **design-director** — decisions. generate-web does NOT make design-decisions; it READS them from frontend-design-spec.json + renders accordingly.142143## Workflow1441451. **Preflight gates** — brand templates check, staleness, the active pack's compliance gates if customer-bound1461472. **Read brief + parse structure:**148 - Hero (title + subtitle + CTA)149 - All substantive sections, preserving source detail rather than a fixed section cap150 - Optional: features grid, FAQ, footer151 Resolve direct brief input into the same frontend contract, pinning the existing152 project/profile and retrieval evidence before rendering. With no handed-over lock, follow153 the direct-entry steps in [Reusable patterns](#reusable-patterns) before the first design154 choice. No parallel private schema for this entry point.1551563. **Apply the `WebExperienceCritic` method** for layout review BEFORE generation:157 - Information hierarchy158 - Accessibility (WCAG AA via existing AccessibilityChecker)159 - Motion-language considerations160 - Brand alignment161162 Use actual native delegation when available and authorized; otherwise label163 the builder's pass as self-review. No actor or model is implied by this recipe.1641653b. **Stack-guidance pass (ADR-0015 — retrieval before rendering):**166 ```bash167 python3 "${LINTEL_SKILLS_DIR:-skills}/design-dna/scripts/search.py" "<layout/feature keywords>" --stack html-tailwind # or nextjs per variant168 ```169 Apply the returned Do/Don't/Severity rules during generation. python3 absent → Read170 `design-dna/data/stacks/<stack>.csv` (same root) directly.1711724. **Generate per variant:**173 - **single-file:** render the selected design as one HTML file with inline174 CSS and only necessary authorized interactions175 - **nextjs-scaffold:** use a selected compatible skeleton or the established176 project structure; write routes/components and only justified manifest changes1771785. **Gate 0 + 4-gate quality pipeline** (per /generate-ppt):179 - Gate 0 (mechanical, ADR-0015): use the180 [design validator](../../../skills/design-dna/scripts/validate_design.py),181 `validate_design.check(content, path,182 profile_hexes)` on actual HTML with the loaded design's resolved palette.183 Hard errors such as zoom-disable, killed focus and emoji icons block;184 off-palette/token findings retain their warning severity. Do not reconstruct185 a bundled profile path that ignores a selected pack asset or brief override.186 - Gate 1: voice (if customer-bound)187 - Gate 2: brand-conformance188 - Gate 3: honest-limitations (only if generating an AI-feature page with disclosure)189 - Gate 4: provenance1901916. **Publish within scope:** atomically write/read back the selected `--out`,192 preserving an authorized replacement's preimage. Report actual checks and193 blocked/unverified obligations; no draft move confers release clearance.1941957. **Optional preview** through the shared browser operations on an authorized owned196 local server. Verify health and actual session ownership first; provider availability197 and URL admission are not established by this instruction.198199## Reusable patterns200201Follow the [reusable pattern consumer contract](../../../skills/pattern/references/consumer-contract.md).202generate-web still makes no design decisions of its own; it renders the projected values.203204**Handed-over lock** (from-frontend-design mode, or a direct run that is given a lock): run205`li-pattern verify-lock` on it against the current context before rendering. Only `ok`206continues. Then check the spec's `pattern_context` with `validate_visual` against that verified207lock, never against a stored report. A stale context, a mismatched setting or an unusable208selection blocks the render; it is not corrected here.209210**Direct entry without a handed-over lock** (`--mode mockup --brief`, and the plain artifact211`--brief` route) resolves itself through the same contract. Do this **before the first design212choice**:2132141. Write the evidenced context, and turn explicit brief decisions about bound settings into215 `--overrides`. Omit unknown facts, and never infer a target.2162. Run `li-pattern resolve --context <ctx> [--overrides <file>]` from the trusted source root.217 - `empty`: continue exactly as without patterns. Write no lock and no `pattern_context`.218 - `ready`: rerun the same command with `--lock219 .claude/runtime/patterns/<run-id>/patterns.lock.json`. The lock goes inside this repository220 even when `--out` is elsewhere. Confirm the same `selection_digest`, then run221 `li-pattern verify-lock` on the new lock against the same context; only `ok` continues.222 Carry the full requirements and setting winners into the design choices.223 - Any other status blocks the dependent design decision and the render: `needs-context`,224 `conflict`, `unavailable` (including a pack context in `fallback` or `error`) and225 `invalid`. So does a run that prints no JSON report. Report the status; never226 hand-write a lock, and never fall back to another source or renderer.2273. Apply `$LINTEL_SOURCE_ROOT/lib/pattern_visual.py` `project_visual` with the verified lock to228 the synthesized design spec. This writes the **final** `frontend-design-spec.json`, with its229 `pattern_context`, before that spec's P05 binding is prepared.230 - Never project after binding: that would change bytes the bound context already selected.2314. Load the bound spec with `design_contract.load_design` and the current P07 configuration.232 With a `ready` selection, pass `pattern_lock` and `pattern_context`, and select both files233 plus `.claude/patterns` in the P05 context; this is what lets a verified pattern palette winner234 outrank the pinned profile.235 Run `validate_visual` against the verified lock **before rendering**; only `passed`236 continues, and unknown settings stay open review items.237238The mockup procedure's step 2 decision method and step 3 load follow these steps; see239[mockup mode](../../../skills/generate-web/references/mockup.md). Direct entry and cycle entry call the same command with the240same inputs, so they produce the same `selection_digest`. When the runtime reports no patterns,241rendering is unchanged.242243## Report format244245Report mode/variant, exact source/design/output paths, selected profile/template,246retained content, actual rendering operations and mechanical/voice/brand/247limitations/provenance outcomes. State whether preview, keyboard, responsive,248reduced-motion and other required observations ran, with their actual evidence.249Missing browser or renderer coverage remains unverified, not a fabricated pass.250251## Compliance integration252253- 4-gate pipeline is the customer-bound enforcement path; the specific gates are pack-configurable (`resolve_pack_field compliance.hooks`; none by default)254- HTML/JS output sanitized — no inline scripts that fetch external resources without disclosure255- nextjs-scaffold retains applicable deployment requirements but triggers no deployment256257## Failure modes258259- **nextjs-scaffold template incomplete** — block that requested target with the260 concrete missing resource; do not silently change the requested artifact.261- **Voice gate fails on customer-facing content** — surface flagged paragraphs, allow regen262- **Accessibility audit fails** (contrast issue, missing alt text) — surface findings; require fixes before gate-2 passes263- **Customer-data in brief** — BLOCK264265## Examples266267**Single-file customer demo:**268```269> /generate-web --brief demo-brief.md --variant single-file --out demo.html --preview270[Render; preview only through a verified owned server and authorized provider.]271```272273**Next.js scaffold:**274```275> /generate-web --brief microsite-brief.md --variant nextjs-scaffold --use-defaults --out microsite276[Render a compatible scaffold; use existing tooling and authorized dependency restoration only.]277```278279## See also280281- `BRAND-INTEGRATION.md`282- `WebExperienceCritic` agent283- `AccessibilityChecker` (Layer 4) for WCAG audit284- `/web-session --mode open` — preview the generated file through owned loopback285- `/frontend-design --mode variants` — compare directions around a mockup286- `/generate-docs` — produce source-grounded Markdown before a format handoff287- The active pack's deploy gate — wire Next.js deployment (pack-configurable)