[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEWAV52V4AEHSRGZ8H9BWF":3,"skill-same:01M7AEWAV52V4AEHSRGZ8H9BWF":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AEWAV52V4AEHSRGZ8H9BWF","landing-page-design",null,"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.","BlueprintLabIO\u002Frestless-core","BlueprintLabIO","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222796351?v=4","01M7AETKD0TZXRAGH2WAKGNYE6","01M7AETKE63A80017SD5ZWAEF4",12,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Flanding-page-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: landing-page-design\ndescription: 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.\n---\n\n# Landing-page design\n\nA landing page is a commercial and visual outcome, not a collection of valid components. The live\nbrowser result is primary evidence. A green build can reject broken work but cannot approve taste.\n\n## Accountable lead: form a team that fits the quality target\n\nBefore commissioning code, name how the team covers these responsibilities:\n\n- product and offer truth;\n- art direction and typography;\n- plain-language copy and information architecture;\n- interaction\u002Fmotion design engineering; and\n- independent comparative criticism.\n\nActors may combine adjacent responsibilities when their role and evidence justify it. Keep the\ncritic independent. If a material responsibility is uncovered, add or reassign Staff before\nproduction instead of asking one generalist to discover strategy, design, copy, implementation and\ntaste simultaneously.\n\nRead [the team and stage contract](references\u002Fteam-and-stage-contract.md) when forming or correcting\nthe team.\n\n## Start from the owner's brief, not from assumptions\n\nBefore any direction is drawn, the Work carries a brief from the person who asked for it:\n\n- who the page is for, and the one thing a visitor should do;\n- two or three sites the owner likes, and what they like about each;\n- what must be said, and what must never be (words, claims, imagery);\n- the copy budget, if it differs from the defaults below.\n\nRead it with the company's Brand & voice (`restless identity brief --outcome \u003Cwork> --channel web\n--audience \u003Caudience>`). If the brief is missing any of these, the lead asks Exec to put the missing\nquestions to the owner in one message and waits for the answers before exploring. Never fill a gap\nwith a guess about taste: a guessed audience or reference is the most expensive mistake in this\nworkflow.\n\n## Copy budget\n\nVisitors scan; they do not read. Unless the brief says otherwise, each page keeps to:\n\n- the hero: a headline of at most 10 words and at most 25 words around it;\n- every other section: at most 60 words, and a visual or an interaction that carries its point;\n- no paragraph over 40 words; and\n- at most 120 words per screen at desktop width.\n\nThe capture manifest reports `density` (words, words per screen, words and visuals per section, the\nlongest paragraph). Read it after every render. Cutting words is usually the fastest quality gain.\n\n## Establish the quality floor\n\nWhen an incumbent exists, capture it at desktop and mobile and treat it as the minimum quality floor.\nPreserve its successful assets, interaction mechanics, content and product truth unless the outcome\nexplicitly rejects them. A clean-room direction means fresh composition and judgement; it does not\nmean asset amnesia.\n\nOrder references explicitly:\n\n1. the real product and its design system define identity and factual truth;\n2. the best accepted incumbent defines the minimum public-site quality;\n3. mature external sites calibrate narrative depth, confidence and finish; and\n4. component libraries provide implementation mechanics, never brand identity.\n\nState what the candidate must improve. If the only requirement is “different,” do not infer that\nchange itself is success.\n\n## Explore before expanding\n\nFor a taste-critical or open-ended direction, commission at least three small, materially different\nvisual directions before building the full site. Each direction must show a real hero thesis, one\nrepresentative product encounter, a compact copy voice sample, desktop\u002Fmobile intent, and its single\nsignature interaction. It may be a live route or a rendered prototype.\n\nThe art\u002Fcreative lead compares the directions against product truth and the incumbent, shortlists\none or two, and records why. Do not average the directions together. Do not spend full-site\nproduction time on an unselected concept.\n\n## Give the owner a first look\n\nBefore building the full site, show the owner the shortlisted directions as screenshots at desktop\nand phone width: one owner judgement, \"First look\", with the images and one line each on what is\ndifferent. Ask which is closer, and what is wrong with it. This takes the owner a minute and saves a\nfull build in the wrong direction. Their answer is taste evidence: record it with\n`restless identity voice-evidence` or `restless identity evidence --pillar visual`, citing the\njudgement, so the next site starts from it.\n\nWhen the owner has said to go ahead without checking back, skip the first look: build the direction\nclosest to their references and name it in the review message.\n\n## Build the selected system\n\nThe design engineer and copy owner receive the selected direction, incumbent assets, product facts,\napproved component registry and route contract. They should:\n\n- use the repository's native framework and existing design system;\n- reuse mature code when it advances the selected direction;\n- make the hero a concrete thesis rather than a decorated headline;\n- spend visual boldness on one orchestrated signature and keep supporting effects disciplined;\n- write short, concrete, value-led public copy from the visitor's side of the screen;\n- give every primary route and section a visual or informational reason to exist;\n- make articles standalone, readable and generous rather than narrow repository annotations; and\n- complete mobile navigation, reduced motion, closing conversion and professional footer states.\n\nRender after each consequential slice. Preserve meaningful time for browser comparison and revision;\ndo not let orchestration or gate repair consume the entire quality budget.\n\n## Compare, do not merely inspect\n\nUse the native web-review skill for deterministic browser facts, then apply\n[the comparative review contract](references\u002Fcomparative-review.md). The critic receives the live\ncandidate, incumbent and product reference at the same viewports, but not producer rationale.\n\nThe verdict is one of:\n\n- `better` — materially improves the outcome without regressing product truth or complete-site\n  quality;\n- `changes_requested` — a plausible winning direction with consequential visible defects; or\n- `weaker` — does not beat the incumbent and should not replace it.\n\n“Acceptable,” “clean,” “coherent,” or “passes checks” are not sufficient when the outcome is to\nimprove an incumbent. If no candidate is better, retain the incumbent and say so.\n\n## Owner-facing completion\n\nThe accountable lead inspects the exact post-critique site. Escalate one live ReviewTarget only after\nthe candidate is proven better, every promised primary route is present, the strongest critic issues\nare resolved, and the comparison evidence is attached. Publication remains a separate consequence.\n\n","# Landing-page design\n\nA landing page is a commercial and visual outcome, not a collection of valid components. The live\nbrowser result is primary evidence. A green build can reject broken work but cannot approve taste.\n\n## Accountable lead: form a team that fits the quality target\n\nBefore commissioning code, name how the team covers these responsibilities:\n\n- product and offer truth;\n- art direction and typography;\n- plain-language copy and information architecture;\n- interaction\u002Fmotion design engineering; and\n- independent comparative criticism.\n\nActors may combine adjacent responsibilities when their role and evidence justify it. Keep the\ncritic independent. If a material responsibility is uncovered, add or reassign Staff before\nproduction instead of asking one generalist to discover strategy, design, copy, implementation and\ntaste simultaneously.\n\nRead [the team and stage contract](references\u002Fteam-and-stage-contract.md) when forming or correcting\nthe team.\n\n## Start from the owner's brief, not from assumptions\n\nBefore any direction is drawn, the Work carries a brief from the person who asked for it:\n\n- who the page is for, and the one thing a visitor should do;\n- two or three sites the owner likes, and what they like about each;\n- what must be said, and what must never be (words, claims, imagery);\n- the copy budget, if it differs from the defaults below.\n\nRead it with the company's Brand & voice (`restless identity brief --outcome \u003Cwork> --channel web\n--audience \u003Caudience>`). If the brief is missing any of these, the lead asks Exec to put the missing\nquestions to the owner in one message and waits for the answers before exploring. Never fill a gap\nwith a guess about taste: a guessed audience or reference is the most expensive mistake in this\nworkflow.\n\n## Copy budget\n\nVisitors scan; they do not read. Unless the brief says otherwise, each page keeps to:\n\n- the hero: a headline of at most 10 words and at most 25 words around it;\n- every other section: at most 60 words, and a visual or an interaction that carries its point;\n- no paragraph over 40 words; and\n- at most 120 words per screen at desktop width.\n\nThe capture manifest reports `density` (words, words per screen, words and visuals per section, the\nlongest paragraph). Read it after every render. Cutting words is usually the fastest quality gain.\n\n## Establish the quality floor\n\nWhen an incumbent exists, capture it at desktop and mobile and treat it as the minimum quality floor.\nPreserve its successful assets, interaction mechanics, content and product truth unless the outcome\nexplicitly rejects them. A clean-room direction means fresh composition and judgement; it does not\nmean asset amnesia.\n\nOrder references explicitly:\n\n1. the real product and its design system define identity and factual truth;\n2. the best accepted incumbent defines the minimum public-site quality;\n3. mature external sites calibrate narrative depth, confidence and finish; and\n4. component libraries provide implementation mechanics, never brand identity.\n\nState what the candidate must improve. If the only requirement is “different,” do not infer that\nchange itself is success.\n\n## Explore before expanding\n\nFor a taste-critical or open-ended direction, commission at least three small, materially different\nvisual directions before building the full site. Each direction must show a real hero thesis, one\nrepresentative product encounter, a compact copy voice sample, desktop\u002Fmobile intent, and its single\nsignature interaction. It may be a live route or a rendered prototype.\n\nThe art\u002Fcreative lead compares the directions against product truth and the incumbent, shortlists\none or two, and records why. Do not average the directions together. Do not spend full-site\nproduction time on an unselected concept.\n\n## Give the owner a first look\n\nBefore building the full site, show the owner the shortlisted directions as screenshots at desktop\nand phone width: one owner judgement, \"First look\", with the images and one line each on what is\ndifferent. Ask which is closer, and what is wrong with it. This takes the owner a minute and saves a\nfull build in the wrong direction. Their answer is taste evidence: record it with\n`restless identity voice-evidence` or `restless identity evidence --pillar visual`, citing the\njudgement, so the next site starts from it.\n\nWhen the owner has said to go ahead without checking back, skip the first look: build the direction\nclosest to their references and name it in the review message.\n\n## Build the selected system\n\nThe design engineer and copy owner receive the selected direction, incumbent assets, product facts,\napproved component registry and route contract. They should:\n\n- use the repository's native framework and existing design system;\n- reuse mature code when it advances the selected direction;\n- make the hero a concrete thesis rather than a decorated headline;\n- spend visual boldness on one orchestrated signature and keep supporting effects disciplined;\n- write short, concrete, value-led public copy from the visitor's side of the screen;\n- give every primary route and section a visual or informational reason to exist;\n- make articles standalone, readable and generous rather than narrow repository annotations; and\n- complete mobile navigation, reduced motion, closing conversion and professional footer states.\n\nRender after each consequential slice. Preserve meaningful time for browser comparison and revision;\ndo not let orchestration or gate repair consume the entire quality budget.\n\n## Compare, do not merely inspect\n\nUse the native web-review skill for deterministic browser facts, then apply\n[the comparative review contract](references\u002Fcomparative-review.md). The critic receives the live\ncandidate, incumbent and product reference at the same viewports, but not producer rationale.\n\nThe verdict is one of:\n\n- `better` — materially improves the outcome without regressing product truth or complete-site\n  quality;\n- `changes_requested` — a plausible winning direction with consequential visible defects; or\n- `weaker` — does not beat the incumbent and should not replace it.\n\n“Acceptable,” “clean,” “coherent,” or “passes checks” are not sufficient when the outcome is to\nimprove an incumbent. If no candidate is better, retain the incumbent and say so.\n\n## Owner-facing completion\n\nThe accountable lead inspects the exact post-critique site. Escalate one live ReviewTarget only after\nthe candidate is proven better, every promised primary route is present, the strongest critic issues\nare resolved, and the comparison evidence is attached. Publication remains a separate consequence.\n\n",{"name":5,"description":7},"main","74448c875ccc3d826c90b46381cc63698ba769aa","infra\u002Fcompany-image\u002Fskills\u002Flanding-page-design",1,"https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core","https:\u002F\u002Frestless.run","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO","2026-11-14 10:29:34",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add BlueprintLabIO\u002Frestless-core --skill landing-page-design",{"tool":37,"command":38},"bunx","bunx skills add BlueprintLabIO\u002Frestless-core --skill landing-page-design",{"tool":40,"command":41},"pnpm","pnpm dlx skills add BlueprintLabIO\u002Frestless-core --skill landing-page-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Flanding-page-design\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fcomparative-review.md","REFERENCE","参考文档",1783,"https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Flanding-page-design\u002Freferences\u002Fcomparative-review.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fteam-and-stage-contract.md",3924,"https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Flanding-page-design\u002Freferences\u002Fteam-and-stage-contract.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M7AEXHE6CPB3TMHWKEMDWYM7","fixture-note-etiquette","How the company writes a Fixture Notes message. Used only by the connections smoke.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Ftools\u002Ffixture-mcp-provider\u002Ffixtures\u002Fplugin\u002Fskills\u002Ffixture-note-etiquette\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7AEXC9H7TTENFY1S87TQZF5","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.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fweb-native-review\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7AEX8KTGCGTDHKMKRMV25AS","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\u002Frun\u002Fassertion\u002Fevidence—not to choose a plan, team, or business verdict.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fscenario-evidence\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7AEX433AM2YZ08ST66G3FF5","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).","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7AEWYCTNC5VF57C9PQF1X4W","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.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Freference-led-reset\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M7AEWV2KP5JM50T3S7VD7HR9","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.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fpublish-git\u002FSKILL.md",[],[]]