landing-page-design
Lead, produce, or independently judge a high-quality public landing page or product website where art direction, copy, motion, responsive composition, and comparative visual quality matter. Use for new marketing sites and consequential redesigns; do not use for routine UI maintenance or a bounded content-only edit.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 12
- Forks
- 1
01 前言 Front Matter
- name
- landing-page-design
- description
- Lead, produce, or independently judge a high-quality public landing page or product website where art direction, copy, motion, responsive composition, and comparative visual quality matter. Use for new marketing sites and consequential redesigns; do not use for routine UI maintenance or a bounded content-only edit.
02 资源文件 2
- 参考文档references/comparative-review.md1.7 KB
- 参考文档references/team-and-stage-contract.md3.8 KB
03 SKILL.md 正文
Landing-page design
A landing page is a commercial and visual outcome, not a collection of valid components. The live browser result is primary evidence. A green build can reject broken work but cannot approve taste.
Accountable lead: form a team that fits the quality target
Before commissioning code, name how the team covers these responsibilities:
- product and offer truth;
- art direction and typography;
- plain-language copy and information architecture;
- interaction/motion design engineering; and
- independent comparative criticism.
Actors may combine adjacent responsibilities when their role and evidence justify it. Keep the critic independent. If a material responsibility is uncovered, add or reassign Staff before production instead of asking one generalist to discover strategy, design, copy, implementation and taste simultaneously.
Read the team and stage contract when forming or correcting the team.
Start from the owner's brief, not from assumptions
Before any direction is drawn, the Work carries a brief from the person who asked for it:
- who the page is for, and the one thing a visitor should do;
- two or three sites the owner likes, and what they like about each;
- what must be said, and what must never be (words, claims, imagery);
- the copy budget, if it differs from the defaults below.
Read it with the company's Brand & voice (restless identity brief --outcome <work> --channel web --audience <audience>). If the brief is missing any of these, the lead asks Exec to put the missing
questions to the owner in one message and waits for the answers before exploring. Never fill a gap
with a guess about taste: a guessed audience or reference is the most expensive mistake in this
workflow.
Copy budget
Visitors scan; they do not read. Unless the brief says otherwise, each page keeps to:
- the hero: a headline of at most 10 words and at most 25 words around it;
- every other section: at most 60 words, and a visual or an interaction that carries its point;
- no paragraph over 40 words; and
- at most 120 words per screen at desktop width.
The capture manifest reports density (words, words per screen, words and visuals per section, the
longest paragraph). Read it after every render. Cutting words is usually the fastest quality gain.
Establish the quality floor
When an incumbent exists, capture it at desktop and mobile and treat it as the minimum quality floor. Preserve its successful assets, interaction mechanics, content and product truth unless the outcome explicitly rejects them. A clean-room direction means fresh composition and judgement; it does not mean asset amnesia.
Order references explicitly:
- the real product and its design system define identity and factual truth;
- the best accepted incumbent defines the minimum public-site quality;
- mature external sites calibrate narrative depth, confidence and finish; and
- component libraries provide implementation mechanics, never brand identity.
State what the candidate must improve. If the only requirement is “different,” do not infer that change itself is success.
Explore before expanding
For a taste-critical or open-ended direction, commission at least three small, materially different visual directions before building the full site. Each direction must show a real hero thesis, one representative product encounter, a compact copy voice sample, desktop/mobile intent, and its single signature interaction. It may be a live route or a rendered prototype.
The art/creative lead compares the directions against product truth and the incumbent, shortlists one or two, and records why. Do not average the directions together. Do not spend full-site production time on an unselected concept.
Give the owner a first look
Before building the full site, show the owner the shortlisted directions as screenshots at desktop
and phone width: one owner judgement, "First look", with the images and one line each on what is
different. Ask which is closer, and what is wrong with it. This takes the owner a minute and saves a
full build in the wrong direction. Their answer is taste evidence: record it with
restless identity voice-evidence or restless identity evidence --pillar visual, citing the
judgement, so the next site starts from it.
When the owner has said to go ahead without checking back, skip the first look: build the direction closest to their references and name it in the review message.
Build the selected system
The design engineer and copy owner receive the selected direction, incumbent assets, product facts, approved component registry and route contract. They should:
- use the repository's native framework and existing design system;
- reuse mature code when it advances the selected direction;
- make the hero a concrete thesis rather than a decorated headline;
- spend visual boldness on one orchestrated signature and keep supporting effects disciplined;
- write short, concrete, value-led public copy from the visitor's side of the screen;
- give every primary route and section a visual or informational reason to exist;
- make articles standalone, readable and generous rather than narrow repository annotations; and
- complete mobile navigation, reduced motion, closing conversion and professional footer states.
Render after each consequential slice. Preserve meaningful time for browser comparison and revision; do not let orchestration or gate repair consume the entire quality budget.
Compare, do not merely inspect
Use the native web-review skill for deterministic browser facts, then apply the comparative review contract. The critic receives the live candidate, incumbent and product reference at the same viewports, but not producer rationale.
The verdict is one of:
better— materially improves the outcome without regressing product truth or complete-site quality;changes_requested— a plausible winning direction with consequential visible defects; orweaker— does not beat the incumbent and should not replace it.
“Acceptable,” “clean,” “coherent,” or “passes checks” are not sufficient when the outcome is to improve an incumbent. If no candidate is better, retain the incumbent and say so.
Owner-facing completion
The accountable lead inspects the exact post-critique site. Escalate one live ReviewTarget only after the candidate is proven better, every promised primary route is present, the strongest critic issues are resolved, and the comparison evidence is attached. Publication remains a separate consequence.
04 同仓库更多 Skills
fixture-note-etiquette
How the company writes a Fixture Notes message. Used only by the connections smoke.
web-native-review
Prepare or independently review a rendered website against its outcome contract and a mature ground-truth reference. Use for landing pages, product sites, blogs, documentation sites, or other browser-native outcomes; do not use to judge source code alone or turn mechanical layout facts into a taste score.
scenario-evidence
Run a versioned Runtime scenario, probe its real capabilities, preserve compact evidence, and prepare its native review target. Use for a project outcome that benefits from repeatable setup/run/assertion/evidence—not to choose a plan, team, or business verdict.
research
Answer a question the company needs to decide on with a sourced brief - market facts, a technology, a regulation, an audience, a price, a supplier. Use when an answer must be found and checked on the web or in documents before acting; do not use for a quick lookup a single source settles, or for competitor landscapes (use competitor-research).
reference-led-reset
Reset a rejected or repeatedly drifting outcome into a genuinely fresh Work Attempt grounded in ordered authoritative references. Use when the owner asks to start over, when qualitative defects survive revision, or when a mechanically valid result conflicts with the product or brand source of truth. Do not use for an ordinary bounded repair that should preserve the current candidate.
publish-git
Safely reconcile, verify, and publish Git refs through the governed Restless effect path. Use for pushes or deployments driven by a Git push; do not use for read-only fetches, local Git work, or provider API administration.