Auto-invokedSkill
od-contribute
One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD;…
@nexu-ioView Skill/faq-page
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".
Install
$ npx -y skills add nexu-io/open-design --skill faq-page --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/faq-page
Context preview
The summary Claude sees to decide when to auto-load this skill.
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".
SKILL.md
faq-page.SKILL.mdname: 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?
Read more
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?
Ships withopen-design
🎨 Best DeepSeek Harness Design Plugin. The open-source Claude Design alternative. 🖥️ Local-first desktop app. 🖼️ Your coding agent becomes the design engine: prototypes, landing pages, dashboards, slides, images & video — real files, HTML/PDF/PPTX/MP4 export. 🤖 Claude Code / Codex / Cursor / DeepSeek Harness / OpenCode & 20+ CLIs via BYOK.
Get the whole plugin, auto-invoked
Stats
95,466
Stars
11,063
Forks
Active
Maintenance
TypeScript
Language
Apache-2.0
License
3d ago
Last commit
4mo ago
Created
Repo: nexu-io/open-design
Other skills on open-design.
@nexu-ioView SkillAuto-invokedSkill
8-bit-orbit-video-temp…
Hyperframes-based video template for retro pixel deck motion design. Use when users want a high-fidelity, multi-scene HTML-to-video composition with advanced…
@nexu-ioView SkillAuto-invokedSkill
ad-creative
Generate and iterate ad creative including headlines, descriptions, and primary text. Useful for paid social and search ad iteration.
@nexu-ioView SkillAuto-invokedSkill
after-hours-editorial-…
Luxury dark-editorial HyperFrames template for three-page cinematic storyboards, inspired by haute couture title cards and magazine chapter spreads. Use when…
@nexu-ioView SkillAuto-invokedSkill
agent-browser
Browser automation CLI for AI agents. Use when the user needs to inspect, test, or automate browser behavior: navigating pages, filling forms, clicking…
@nexu-ioView SkillAuto-invokedSkill
ai-music-album
Full-lifecycle AI music album production — concept, lyric drafting, track sequencing, and export. Useful for indie album experiments and brand soundtracks.
@nexu-ioView Skill