webkubor/ui-craft / skills/landing-page-design
landing-page-design
VerifiedComplete system for building high converting landing pages: intake questions, page structure, layout selection, conversion copywriting, SEO, plus project-led visual decisions. Use for landing page strategy, marketing structure, conversion copy and optional visual recipes.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 11.1 KB |
| references/content-discipline.md | markdown | 2.0 KB |
| references/single-ruler-principle.md | markdown | 1.4 KB |
| references/style-anchors.md | markdown | 6.3 KB |
| references/three-track-separation.md | markdown | 2.0 KB |
| references/upstream-visual-recipe.md | markdown | 10.1 KB |
| templates/inject-bar.js | script | 2.3 KB |
references/three-track-separation.md
View on GitHub# 三轨分离 — 产品文档组织方法
> 由产品、设计与交互文档混杂的复盘抽象。
> 核心问题:把产品定义、视觉规范、交互流程揉进同一文档 → 两层节奏打架、变更混乱。
## 根因诊断
一个「发现→DESIGN.md」节点等于把三件事揉在一起:
- **产品问题**(这玩意给谁用、解决什么 job、范围边界)→ 变更罕见
- **设计系统**(token、视觉、组件契约)→ 变更罕见
- **交互体验**(状态机、流程、动效、异常处理)→ 变更高频
三轨变更频率完全不同,塞进同一文档必然导致:改一个按钮状态要动整个产品定义文档;加一个新页面要重写视觉规范。
## 正解:三轨分离
按职责与变更频率组织三类信息;项目较小时可以是同一文档的清晰章节,不强制文件名或文件数。
| 轨道 | 文件 | 变更频率 | 核心内容 |
|------|------|----------|----------|
| **PRODUCT** | `PRODUCT.md` | 罕见(产品方向变更) | 定位、目标用户、Job-to-be-Done、MVP 边界、定价、明确不做 |
| **DESIGN** | `DESIGN.md` | 罕见(设计方向/Token 变更) | 视觉原则、Token 体系、单尺原则、Tailwind 收口、组件契约、明确禁令 |
| **EXPERIENCE** | `EXPERIENCE.md` | 高频(功能迭代/流程优化) | 页面流程图、状态机、动效规范、异常处理、数据流转 |
## 关键原则
1. **不要为了分离而分离** — 三轨的核心价值是「变更频率不同」,不是文档好看。
2. **主 PRD 引用三轨** — 项目根目录保留一份简短 README.md,只引用三轨文档,不重复内容。
3. **高频改 EXPERIENCE,低频改 PRODUCT/DESIGN** — 频繁修改产品定义时,重新确认范围和验收契约。
4. **DESIGN.md 是单尺原则的载体** — 样式收口规则写在 DESIGN.md,不在代码注释或 PRD。
## 适用场景
任何需要产品文档的项目(小程序、Web App、SaaS、工具站)。按文档规模与协作成本决定是否拆文件。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |