Create Expert FAQ Documentation

This skill provides expertise in creating comprehensive, user-focused FAQ documentation that maximizes discoverability, reduces support burden, and enhances user experience, grounded in the psychology of user queries, information architecture, and modern documentation best practices. Core principles cover a question-first approach (writing questions exactly as users ask them in natural language, including multiple phrasings for the same question, progressive disclosure from overview to details to examples, and clear headings/bullets/actionable steps in answers) and strategic organization (grouping FAQs by user journey stage from getting-started through troubleshooting, prioritizing most-asked questions, cross-referencing related questions, and maintaining separate FAQ sets per user persona when needed).

Content structure and formatting cover standard question formats ("How do I...", "What happens when...", "Why am I seeing...", "Can I...", "What's the difference between...") and an answer structure template pairing a one-sentence quick answer with detailed numbered steps, a code or screenshot example, and a related-questions cross-reference. Effective answer patterns lead with the direct answer before context, use active voice and imperative mood, state expected outcomes per step, and provide both GUI and programmatic solutions when applicable.

Advanced FAQ techniques cover multi-modal answers (a single question answered with a quick answer, a JavaScript fetch code example, a cURL equivalent, and a common-issues subsection listing specific error codes with their causes) and conditional answers (branching instructions for different user segments, such as free versus paid account deletion flows, with a data retention note). Search optimization strategies cover keyword integration (synonyms, technical and colloquial phrasing, common misspellings, keyword-structured URLs) and metadata enhancement using meta description/keywords tags plus schema.org FAQPage JSON-LD structured data marking up question/answer pairs for search visibility.

FAQ maintenance and analytics cover content lifecycle management (reviewing analytics for high-exit-rate or low-time-on-page gaps, tracking support ticket themes for missing topics, updating answers as features change, archiving outdated questions with redirects, A/B testing question phrasing) and user feedback integration (a was-this-helpful widget with links to support, community forum, and video tutorial resources). Performance indicators tracked include FAQ page views versus support ticket reduction, average time on page, click-through to related docs, user satisfaction scores, and search query gap analysis. Integration with the documentation ecosystem covers cross-platform consistency (markdown-based content synced across help desk, website, and in-app help, embeddable FAQ widgets, PDF exports) and API documentation integration (linking FAQ answers to detailed rate-limit or code-example documentation rather than duplicating content).

Use this skill when writing or restructuring FAQ documentation - question-first content organization, multi-modal answer formatting, FAQPage schema markup, or analytics-driven maintenance. It is well suited to products or services with a meaningful volume of recurring user questions worth documenting systematically. It is not meant for one-off support responses, or products too new to have identified recurring question patterns yet.

Input: the product's common user questions, support ticket themes, and existing documentation to restructure.

Output: organized FAQ content with question-first structure, multi-modal answers, and FAQPage schema markup. Example FAQPage structured data:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How do I authenticate API requests?",
    "acceptedAnswer": { "@type": "Answer", "text": "Set your API key in the Authorization header..." }
  }]
}
</script>

Produces markdown-based FAQ content compatible with help desks, websites, and in-app help widgets, with schema.org FAQPage JSON-LD for search engine visibility.

Technical writers and support/documentation teams building self-service FAQ resources, and teams that need discoverable, analytics-maintained FAQ content rather than a static, rarely-updated question list.