菜单
Use when designing FAQ sections. Covers the structure (accordion vs always-open), question selection (objection-driven), the answers that build trust, and the format.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/x3allamerican/design-skills-fleetsafety --skill faq-section-design命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when designing 404 pages and the broader empty-state pattern library. Covers tone, illustration, search recovery, and the difference between 'no data yet' and 'this URL doesn't exist'.
Use when designing A/B tests. Covers hypothesis-driven testing, sample-size calculation, the test-design template, and the cultural rituals that make testing productive.
Use when shipping any user-facing UI. Covers the non-negotiable accessibility baseline: contrast, focus states, semantic HTML, keyboard navigation, screen-reader support, motion preferences. The minimum to avoid embarrassment and ADA risk.
基于 SOC 职业分类
正在显示 SKILL.md
| name | faq-section-design |
| description | Use when designing FAQ sections. Covers the structure (accordion vs always-open), question selection (objection-driven), the answers that build trust, and the format. |
A great FAQ section preemptively kills objections. A bad one is filler.
Questions should answer the buyer's REAL concerns, not your product's strengths.
Common categories:
Audit your support tickets for question 1-10 most asked. Those are your FAQ.
Questions visible; answers expand on click.
Pros: Compact, scannable. Cons: User has to click to see answers.
All questions + answers visible.
Pros: All info visible, SEO-friendly. Cons: Long page, fewer questions can be shown.
Questions left, answers right.
Pros: Easy scan + answer visible. Cons: Less mobile-friendly.
For most SaaS, accordion is default. SEO-heavy pages use always-open.
| Length | When |
|---|---|
| 1-2 sentences | Default for most questions |
| 1 paragraph | Nuanced topics (data security, legal disclaimers) |
| 2 paragraphs + link | Deep topics that deserve their own page |
NEVER more than 2 paragraphs in an FAQ answer. Move to a separate page.
FAQ should sound like you're talking to a real customer:
Bad: "Yes, we take security very seriously." Good: "TLS 1.3 in transit, AES-256 at rest, row-level security at the database level. Privacy policy here."
Each answer should:
X3 Compass has FAQ on /faq plus inline FAQ section on homepage (8 expandables). Includes "Is this legal advice?", "What if AI is wrong?", "Cancel anytime?" — the real top concerns.