Skip to content

site-spec: expand into creative direction (layout, hero, typography)#3630

Open
lezama wants to merge 1 commit into
trunkfrom
enhance-site-spec-creative-direction
Open

site-spec: expand into creative direction (layout, hero, typography)#3630
lezama wants to merge 1 commit into
trunkfrom
enhance-site-spec-creative-direction

Conversation

@lezama
Copy link
Copy Markdown
Contributor

@lezama lezama commented May 27, 2026

What

Enhances the site-spec skill to auto-expand a vague brief into a creative direction — inferring layout, pages/sections, hero composition, and typography from the site name — then briefs the user in ≤4 lines before building.

Addresses @youknowriad's feedback on #3610: "we should not remove site spec, we should enhance it".

Why

When a user says "make a site for my bar", the current skill asks one binary question (one-page or multi-page?) and then the agent guesses everything else. The result is usually a minimal skeleton.

Telex's better output quality comes from two specific things it does before writing any file:

  1. Hero composition — a short paragraph of cinematic prose describing the spatial layout (full-bleed / asymmetric / centered, image placement, typographic weight). This becomes the spatial anchor for all downstream block choices.
  2. Typography inference — a font pairing derived from the site type (coffee shop → Fraunces + Spectral; law firm → Cormorant Garamond + Source Sans).

Both happen without asking the user anything extra.

Changes

2 files, +42/−17 lines.

Relationship to other PRs

Testing

npm run cli:build
  1. "ayudame a crear un sitio para una hamburguesería" — agent should ask the name, stop, wait for reply, then auto-expand (layout + hero + typography) and brief you before building. No layout question.
  2. "create a site called Bean & Brew" — agent should skip Round 1 (name already given), auto-expand directly, brief you, then build.

…typography)

Instead of asking 'one-page or multi-page?', the skill now auto-infers
layout, pages/sections, hero composition, and typography from the site
name — then briefs the user in ≤4 lines before building.

Inspired by Telex's approach: committing to a heroComposition (cinematic
prose describing spatial composition) and inferring typography from site
type are the two changes that most improve output quality.

Folds the separate creative-direction skill into site-spec as Riad
suggested — one skill for gathering user needs and expanding the brief.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@wpmobilebot
Copy link
Copy Markdown
Collaborator

📊 Performance Test Results

Comparing 11343d7 vs trunk

app-size

Metric trunk 11343d7 Diff Change
App Size (Mac) 1335.89 MB 1335.89 MB +0.00 MB ⚪ 0.0%

site-editor

Metric trunk 11343d7 Diff Change
load 1735 ms 1819 ms +84 ms 🔴 4.8%

site-startup

Metric trunk 11343d7 Diff Change
siteCreation 9604 ms 9595 ms 9 ms ⚪ 0.0%
siteStartup 4922 ms 4916 ms 6 ms ⚪ 0.0%

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants