跳到正文
cccskills
免费在 GitHub 公开

draft-landing

Use when asked to structure a landing page, design page layout for conversion, or plan landing page information architecture. Examples: "landing page structure for SaaS", "conversion-optimized layout"

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md2.9 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

draft-landing — Landing Page Information Architecture

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

When to use

User needs a landing page structure, section order, or conversion-optimized layout. Product type is known or discoverable.

Workflow

  1. Identify product type from user request or project context
  2. Search landing page patterns:
    python3 -m draft_agent.uiux search --domain landing --query "{product_type}" --limit 3
    
  3. Search product reasoning for audience + conversion context:
    python3 -m draft_agent.uiux search --domain product --query "{product_type}" --limit 3
    
  4. Validate each section against the "so what?" test — every section must earn its place
  5. Output section order with CTA placement markers

Output format

┌─ Landing Page IA — {product_type} ──────────────────────────────────┐
│ #  │ Section            │ Purpose                    │ CTA?          │
├────┼────────────────────┼────────────────────────────┼───────────────┤
│  1 │ {section_name}     │ {purpose}                  │ Primary CTA   │
│  2 │ {section_name}     │ {purpose}                  │ —             │
│  3 │ {section_name}     │ {purpose}                  │ Secondary CTA │
│  … │ …                  │ …                          │ …             │
└────┴────────────────────┴────────────────────────────┴───────────────┘

Conversion strategy: {strategy}
CTA copy guidance:   {cta_guidance}

Anti-patterns

  • Never skip the "so what?" test per section — if a section can't answer it, cut it
  • Never add sections without a clear conversion purpose
  • Never place the primary CTA below the fold on the first screen
  • Never structure the page without knowing the primary audience and their job-to-be-done

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

apex

免费

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

apex-gate

免费

Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

apex-plan

免费

Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

中文简介正在准备中。当前显示原文说明。

tonone-ai/tonone762026年10月15日 更新

查看 tonone-ai 的全部技能

报告此技能的问题