faq-page — Claude Code skill: FAQ page builder
Builds an HTML FAQ page with an accordion, search, and category filters. Use it when a brief calls for a help centre or support page.
npx skills add nexu-io/open-design --skill faq-page -a claude-codeWhat faq-page does
This skill creates a single HTML FAQ page with a header, search field, category filters, expandable question-and-answer items, and a support contact area. Search matches text in both questions and answers, while category controls use data-category attributes.
It reads the active DESIGN.md and applies component tokens to interactive controls. The output is a complete HTML document with inline CSS and JavaScript, using semantic details and summary elements or ARIA attributes for a custom accordion.
An active DESIGN.md with a design system is required, so check that it covers colour, typography, layout, and components before running the skill. It also checks keyboard navigation, case-insensitive search, and mobile interaction.
What it helps with
- create an FAQ page from question-and-answer content
- search across questions and answers
- filter help items by category
- expand and collapse FAQ answers
- produce self-contained HTML with CSS and JavaScript
Example prompts for the agent
- Create an FAQ page for a service with search, categories, and an accordion.
- Build a help centre with account and billing questions.
- Generate a support HTML page that filters questions by category.
How to install faq-page
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill faq-page -a claude-code2Manually: put the files in place
~/.claude/skills/faq-page/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/faq-page/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill faq-page -a codex2Manually: put the files in place
.agents/skills/faq-page/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill faq-page -a cursor2Manually: put the files in place
.cursor/skills/faq-page/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design faq-page2Manually: put the files in place
.github/skills/faq-page/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill faq-page -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path skills/faq-pageManually: put the files in place
.devin/skills/faq-page/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill faq-page -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set106
The whole set →Similar
Questions about faq-page
How do I install faq-page in Claude Code?
Run npx skills add nexu-io/open-design --skill faq-page -a claude-code, then run npx skills add nexu-io/open-design --skill faq-page -a claude-code again and open ~/.claude/skills/faq-page/SKILL.md.
What does faq-page do?
It generates an HTML FAQ page with an accordion, text search, category filtering, and a support contact section.
What does faq-page need for interface styling?
The skill reads the active DESIGN.md. Its design system needs tokens for colour, typography, layout, and components.
Source text
SKILL.md · Apache-2.0
---
name: faq-page
description: |
A Frequently Asked Questions (FAQ) page with collapsible accordion sections,
search functionality, and category filtering. Use when the brief asks for
"FAQ", "help center", "questions", or "support page".
triggers:
- "faq"
- "FAQ"
- "frequently asked questions"
- "help center"
- "support page"
- "Q&A"
- "常见问题"
- "帮助中心"
od:
mode: prototype
platform: desktop
scenario: support
preview:
type: html
entry: index.html
design_system:
requires: true
sections: [color, typography, layout, components]
craft:
requires: [typography, accessibility-baseline, state-coverage]
---
# FAQ Page Skill
Produce a single FAQ page with collapsible accordion sections, search, and category filtering.
## Workflow
1. **Read the active DESIGN.md** (injected above). Use the component tokens for
interactive elements (accordion headers, search input, category pills).
2. **Pick the domain** from the brief (e.g., SaaS product, e-commerce, service)
and write 12–18 real FAQ entries across 3–4 categories.
- **Edge cases**:
- If the brief provides fewer than 8 FAQs, ask for more content or generate
realistic questions based on the domain.
- For 1–5 FAQs, skip categories and search; show a simple list.
- For very long answers (>100 words), break into paragraphs or bullet points
to maintain readability.
3. **Sections**, in order:
- **Header** — page title ("Frequently Asked Questions" or "Help Center"),
optional subtitle (1 sentence explaining what users can find here).
- **Search bar** — prominent search input with placeholder text and icon.
Functional JS to filter questions in real-time.
- **Category filters** — 3–4 pill-style buttons to filter by category
(e.g., "Billing", "Account", "Technical", "General"). "All" selected by default.
- **FAQ accordion** — collapsible question/answer pairs:
- Question as clickable header with expand/collapse icon (chevron or plus/minus).
- Answer hidden by default, expands on click with smooth animation.
- Each entry has `data-category` attribute for filtering.
- **Footer CTA** — "Still have questions?" section with contact link or
support email.
4. **Write** a single HTML document:
- `<!doctype html>` through `</html>`, CSS and JS inline.
- Accordion uses semantic HTML (`<details>` and `<summary>` for progressive
enhancement, or custom JS with proper ARIA attributes).
- Search filters questions by matching text in question or answer.
- Category filters show/hide questions based on `data-category`.
- Smooth transitions for expand/collapse (max-height or grid-template-rows).
- `data-od-id` on header, search, categories, accordion container, footer.
5. **Self-check**:
- Questions are specific and realistic (not generic placeholders).
- Answers are concise (2–4 sentences) but complete.
- Keyboard navigation works (Tab through questions, Enter to expand).
- Search is case-insensitive and filters by matching text.
- Only one accordion item expanded at a time (optional, depends on UX preference).
- Mobile-friendly (accordion headers are tappable, search is usable).
## Output contract
Emit between `<artifact>` tags:
```
<artifact identifier="faq-page" type="text/html" title="FAQ Page">
<!doctype html>
<html>...</html>
</artifact>
```
One sentence before the artifact, nothing after.
## Example questions by category
**Billing**
- How do I update my payment method?
- What payment methods do you accept?
- Can I get a refund?
- How do I cancel my subscription?
**Account**
- How do I reset my password?
- Can I change my email address?
- How do I delete my account?
- What happens to my data after I cancel?
**Technical**
- What browsers do you support?
- Is there a mobile app?
- How do I export my data?
- What are your API rate limits?
**General**
- What is [Product Name]?
- How do I get started?
- Do you offer customer support?
- Where can I find your terms of service?
© nexu-io · Apache-2.0 · nexu-io/open-design