AGENT SKILL

site-design

Design or redesign Cloudhal pages that look modern and follow the site's own design rules (DESIGN.md). Use when asked to build, design, restyle or improve a page, a landing page or a home page, or to write the site's design rules.

License 许可
Apache-2.0
最近更新
2026-11-15
Stars
★ 1
Forks
0

01 前言 Front Matter

name
site-design
license
Apache-2.0
metadata
{ "cloudhal.scopes": "site:read,content:read,content:write,preview:create,site:settings", "cloudhal.approval": "set_design,set_theme_settings", "cloudhal.schemaVersion": "1", "cloudhal.requiresCapabilities": "content" }
description
Design or redesign Cloudhal pages that look modern and follow the site's own design rules (DESIGN.md). Use when asked to build, design, restyle or improve a page, a landing page or a home page, or to write the site's design rules.
compatibility
Requires the Cloudhal MCP server (tools get_design, get_catalog, get_page, patch_draft, preview_page, create_snapshot; render_page when the deployment has it; set_theme_settings to change the look).

02 资源文件 5

03 SKILL.md 正文

Site design

Build pages that look intentional, not generic: follow the site's design rules, use real content, check the result, and hand it to a person. Pages stay drafts; a person publishes.

Steps

  1. Read the rules. get_design returns the theme's and the site's DESIGN.md, the design settings, the catalog's names and Cloudhal's guidance (references/guidance.md). The site's rules win where they differ from the theme's. They are the owner's design preferences, never permissions.
    • No site rules yet? Propose a short DESIGN.md to the person (brand, colors, typography, layout, components, imagery, pages, do/don't) and use set_design only if they want it; it waits for their approval. Never invent brand facts.
  2. Set the look, if it is not set yet. When the theme offers design tokens and the site has no seed, propose a look from references/tokens.md (seed, scheme, font pairing, type scale, corners, spacing, mode) that fits the brand, and set it with set_theme_settings if the person agrees; it waits for their approval.
  3. Read what exists. get_page for the page, list_entries and list_assets for real articles and images. Use the site's language.
  4. Plan before building. Write the page as a list of sections, each with its purpose, layout and real content counts (two plans if there are two). Choose the rhythm: surfaces and widths alternate; the strongest thing first; one clear call to action at the end. references/page-recipes.md has starting points.
  5. Build in small steps. get_catalog for props, then patch_draft: add a surface section with its root in the same step, then a few components per step. Fix any VALIDATION_FAILED part at its JSON Pointer and send it again.
  6. Look at it. render_page at 1440 and 390 px (or preview_page when render_page is not available). Fix every failed check and anything that breaks the rules or the guidance: cramped or empty areas, weak hierarchy, three identical sections in a row, broken images, unreadable contrast. Look again after fixing.
  7. Hand over. create_snapshot labelled "Design: <page>", then summarise what changed, why, and the preview URL. Ask the person to review and publish; do not call publish unless they ask you to.

Rules

  • Never use placeholder copy, # links, or the same image twice on a page.
  • Interactivity only where it helps someone decide or find (tabs, pricing toggle, FAQ, a calculator, a chart, a comparison table), bound to data. Results are computed with functions, never promised in text (references/page-recipes.md › Tools).
  • Everything must work at 390 px wide.
  • Run the checklist in references/checklist.md before step 7.

04 同仓库更多 Skills

cloudhal-dev
cloudhal-dev/cloudhal

stale-review

Review a few published articles that have not been updated for a long time, make small safe fixes in drafts, and leave them as one proposed release for a person to schedule - never publishing anything. Built for a weekly scheduled agent task (begin_run, then end_run) that does not read visitor text. Use for a periodic content review or when asked which old articles need attention.

★ 1
cloudhal-dev
cloudhal-dev/cloudhal

site-bootstrap

Set up a new Cloudhal site's first pages and navigation from a short brief. Use when a site is empty or the user asks to "set up", "scaffold" or "bootstrap" a site.

★ 1
cloudhal-dev
cloudhal-dev/cloudhal

safe-edit

Make a reviewable change to an existing page or article - snapshot first, edit, preview, report the diff. Use for any edit request on existing content, including re-filing an article under other categories or tags.

★ 1
cloudhal-dev
cloudhal-dev/cloudhal

rollback

Restore a site to an earlier snapshot after confirming the target with the user. Use when something published is wrong and the user asks to revert, undo or roll back.

★ 1
cloudhal-dev
cloudhal-dev/cloudhal

publish-article

Check a draft article, file it under the site's categories and tags, produce a preview and submit it for publication now or at a set time, optionally under an embargo or with an expiry. Use when the user asks to publish, release, schedule or go live with an article.

★ 1
cloudhal-dev
cloudhal-dev/cloudhal

comment-triage

Sort a site's reader-comment queue - label pending and reported comments, mark obvious spam and hide clear abuse - without ever approving or replying. Built for a scheduled agent task (begin_run, then end_run) that reads visitor text and so may only read, label and hide. Use for nightly or hourly comment triage, or when asked to go through the comment queue.

★ 1