design-page
Implement an approved storefront page plan with verified production assets. Authors canonical Lexsis source, creates or edits one unpublished hosted draft, performs hosted responsive and commerce QA, and returns DESIGN_APPROVED. Never plans, produces assets, or publishes.
Install / Use
npx skills add Aetheria-Labs1/storefront-skills --skill design-pageInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of design-page
design-page scores 65/100 on our quality scale, 3996th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 10 KB long, well organised into 11 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit ā read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-09. It catches known dangerous patterns, not every risk ā read a skill before letting an agent act on it.
design-page compared with similar skills
All 4 of these similar skills score higher than design-page; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| design-page (this skill)by Aetheria-Labs1 | 65 | 0 | ā | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install design-page?
- Run
npx skills add Aetheria-Labs1/storefront-skills --skill design-page. The install tabs above show the steps for each supported agent. - Which AI agents does design-page work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is design-page safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is design-page still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubname: design-page description: "Implement an approved storefront page plan with verified production assets. Authors canonical Lexsis source, creates or edits one unpublished hosted draft, performs hosted responsive and commerce QA, and returns DESIGN_APPROVED. Never plans, produces assets, or publishes."
Design an Approved Page
Turn the approved specification into one verified unpublished Lexsis draft. This skill owns implementation schemas, source, CSS, compilation, draft creation or version-safe editing, hosted QA, and design approval.
Required Inputs
Read:
work/storefront/setup.md;- the selected store's
brand.md,design.md,products.md,persona.md,rules.md, and default theme CSS; - the exact page plan with
PLAN_APPROVED <who> <date>; - the asset handoff with
ASSETS_READY; - optional
VISUAL_DIRECTION_APPROVEDframes and visual decisions; references/design-authoring.md;references/hosted-design-review.md.
Use exact Lexsis actions:
lexsis_brand.context,lexsis_brand.get_theme, andlexsis_brand.navigationwhen the plan requires full navigation;lexsis_catalog.get,lexsis_catalog.reviews, andlexsis_catalog.review_collection_items;lexsis_template_library.get_kitandlexsis_template_library.get_mineonly for directions selected upstream;lexsis_design.get_section,lexsis_design.islands, andlexsis_design.island_schema;lexsis_build.push_tokenplusnpx @lexsis/cli new/pull/diff/pushin CLI mode (the default, seelexsis-mcp-contract.mdWrite Path);- inline mode only:
lexsis_build.commitwithcreateto make the draft, thenlexsis_build.get,patch,commitanddifffor every edit (last-resort fallback:lexsis_pages.compilethenlexsis_page_create.create); lexsis_pages.integrityandlexsis_pages.qa;lexsis_drafts.page_update_head(pagetheme_css) andlexsis_drafts.page_record_qa.
Resolve unfamiliar schemas through exact router/action discovery.
1. Enforce the Handoff
Stop before implementation when:
- setup context or the selected binding is missing;
- the plan is blocked, awaits approval, or lacks final section copy;
- the asset status is
ASSETS_PENDING_USERorASSETS_BLOCKED; - any required slot lacks a permanent verified binding;
- supplied concepts remain
VISUAL_DIRECTION_IN_REVIEW; - plan, asset, concept, store, or theme bindings disagree.
Return strategy, copy, offer, proof, claim, section, or template changes to
/plan-page. Return missing, unsuitable, inaccessible, or unverified media
to /plan-assets. The visual stage is optional; continue when it was never
used or was explicitly skipped.
Preserve the approved value argument, component explanations, mechanism
evidence, proof placement, and offer terms through copy, imagery, and section
order. Previously approved plans remain usable without the newer value-strategy
fields; do not require retroactive replanning for unrelated scoped edits.
Changing the argument or commercial terms returns to /plan-page.
An explicit /design-page request authorizes one unpublished page-creation
credit for the named page. It does not authorize another page, paid asset
work, publication, or live operations.
2. Refresh Implementation Facts
Confirm the live store and selected theme. Refresh every bound product and variant used by commerce controls. Read live review data only for review components already specified by the approved plan.
Stop and return to the owning stage when live data invalidates approved copy, offer terms, claims, product availability, variant defaults, proof totals, or asset identity. Do not silently rewrite the plan.
3. Resolve the Implementation
Follow references/design-authoring.md.
- Apply the plan's design direction, selected theme, and optional approved visual decisions.
- Resolve the selected page kit, section source, or saved merchant section. For a custom direction, author the source directly.
- For each planned interaction, inspect the compact island catalogue and fetch the exact current schema only for the chosen island.
- Bind only production assets listed in the
ASSETS_READYtable. Use their permanent URLs, crops, alt intent, and provenance decisions. - Place final plan copy verbatim. A wording change returns to
/plan-page; responsive line breaks are implementation. - Render proof, claims, offers, urgency, inventory, prices, reviews, and policies only from their approved rows and refreshed live facts.
- Author semantic source, scoped section styles, page-wide
theme_css, required scripts, head data, and schema-valid islands.
When the plan's scope is a product or collection template, follow
references/resource-templates.md: pass resource_type at compile and
create, bind islands and text to the resource instead of one product or
collection, and review the hosted preview at the plan's sample handles.
Routing live URLs to the template is a separate approved live operation.
On a PDP or product template, bind reviews with productIds and never
hardcode a fallback collection in props. Apply the plan's review fallback by
passing review_fallback to lexsis_page_create.create, or
lexsis_drafts.set_review_fallback on an existing page; unset means store
reviews. Write the product and fallback headings as page HTML toggled by CSS
on data-reviews-source (snippet in references/resource-templates.md);
the island renders no fallback labels.
Concept images guide composition only. Their URLs never enter source or asset bindings.
4. Compile Early
Compile the complete rough source before polishing isolated sections.
- Treat
validation_errorsas the work list. - Resolve only the schemas implicated by planned behaviour or compiler findings.
- Repair editable source and CSS, preserving section ids and approved copy.
- Recompile until blocking errors are clear.
- Retain the clean compile id, input hashes, and bundle hash.
The compiler is the compatibility authority. Do not patch compiled output or replace unsupported interactions with unverified custom behaviour.
5. Create or Update One Draft
For a new page in CLI mode, write the files into a folder and run
npx @lexsis/cli new ./page --slug <slug> --theme <theme_id> --dry-run, then
again without --dry-run, with a create-only token from lexsis_build
push_token (no page_id). Pass the store header and footer ids as
--shared <id,id> and a similar page as --from <page_id>. Inline (no
shell), call lexsis_build.commit once with no page_id, a
create object (slug, title, theme_id, plus archetype,
product_binding or resource_type when needed) and the page as files
(lexsis.json, sections/<id>.html, styles/*.css). Run it with
dry_run: true first: one call returns every diagnostic with file and line
and creates nothing. Pass the store header and footer ids from setup.md in
shared_sections so they are linked at creation. When a similar page or kit
page exists, pass it as from and send only the new or changed files. See
page-editing.md, New Page.
Fallback when lexsis_build is unavailable: lexsis_page_create.create once
with the clean compile_id, creation metadata and publish:false. Do not
combine compile_id with source, CSS, head, scripts or runtime dependencies.
Record the returned page id, version, hosted preview, compile evidence,
DRAFT_CREATED, design.status: pending-approval, and
qa.status: pending. Return the hosted preview immediately.
If the page already has an id, read its edit context and current source.
Reconcile unexpected version drift, compile the updated complete source, and
write the smallest source-based change with expected_version. Never spend a
second creation credit to fix or revise the same page.
6. Run Hosted Review
Follow references/hosted-design-review.md against the hosted draft at 390,
768, and 1280. Verify:
- fidelity to the approved plan, asset bindings, and optional visual decisions;
- responsive hierarchy, typography, spacing, media crops, accessibility, motion, and absence of generic design clutter;
- exact copy, proof, offer, claim, policy, and product treatment;
- island hydration and expected interaction;
- real variant, cart, quantity, subtotal, sold-out, navigation, header, and footer behaviour;
- no overflow, broken media, duplicated chrome, console errors, or unexpected layout shifts.
Save supported evidence through lexsis_drafts.page_record_qa. Fix findings
in the existing draft with version-safe source edits, then rerun the affected
checks. If browser evidence is unavailable, keep QA pending and return
DRAFT_CREATED.
7. Approve the Design
Show:
Hosted preview: [url]
Draft: [page id] version [version]
Plan: PLAN_APPROVED [who, date]
Assets: ASSETS_READY [binding count]
Visual direction: [approved | skipped | not used]
Sections: [ordered ids]
Interactive components: [islands]
Hosted review: 390/768/1280 [passed | findings]
Commerce: [passed | findings]
Source and bundle hashes: [values]
After hosted QA passes and the user explicitly approves that reviewed version,
record DESIGN_APPROVED <who> <date> for the page id and version.
Any later visible source, CSS, copy, layout, island, or asset change returns
the design to changes-pending-approval. /publish must gate on the same
DESIGN_APPROVED version.
Shared Sections
Read the Shared sections table in work/storefront/setup.md. Never rebuild a
header, footer, or entry pop-up that already exists as a shared section. On a
new page, pass the shared section ids as lexsis new --shared
(inline: lexsis_build.commit shared_sections); they are added and linked with no extra version. On an
existing page, link one with lexsis_drafts.shared_section_sync and
page_ids.
To change a shared section, edit it once with
lexsis_drafts.shared_section_update, or change only island props or one
exact CSS/JS snippet with lexsis_drafts.shared_section_patch; both reject a
source no page could compile. Then run
lexsis_drafts.shared_section_sync without page_ids. Sync writes drafts, so
live pages change only after /publish. Pages in a running experiment are
skipped with reason: "running_experiment"; report them. Use
lexsis_drafts.shared_section_detach only when one page must diverge.
Return
Return the page id, version, hosted preview, compile evidence, QA evidence, sections, islands, and status:
DRAFT_CREATEDwhile hosted QA or user approval is pending;DESIGN_APPROVEDonly after hosted QA and explicit approval.
Never publish.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code ā from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio ā 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit ā see the Safety scan above for what the skill file itself contains.
