About help-center-architecture
help-center-architecture is a skill for planning support knowledge so people can find answers and act on them. It guides teams through information architecture, article design, escalation, search, and upkeep, with a defined set of planning outputs.
Key features
- 01Identify audiences and support drivers
- 02Design information architecture and templates
- 03Plan escalation, search, and feedback
- 04Connect content to UI and analytics
- 05Produce taxonomy and article backlog
Use cases
- 01Planning a new help center
- 02Reorganizing support articles
- 03Defining article quality checks
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/help-center-architecturein Claude Code to confirm it loaded.
Bundled filesagents/openai.yamlreferences/help-center-architecture-patterns.md
Details
From the project READMEHelp Center Architecture
Use this skill to make support knowledge easy to find, act on, and improve.
Workflow
- Identify audiences, top support drivers, product surfaces, support channels, and trust-sensitive flows.
- Read
references/help-center-architecture-patterns.md. - Design information architecture, article templates, escalation routes, search, feedback, and maintenance ownership.
- Connect help content to product UI, support macros, and analytics.
- Produce taxonomy, article backlog, and quality checks.
When not to use
- Do not use for generic advice the base model already handles without this skill's specific artifact contract.
Guardrails
- Do not use help content to hide product defects or unclear pricing.
- Do not bury refund, cancellation, deletion, or safety routes.
- Keep support articles current with product behavior.
Output format
Audiences:
Top support drivers:
Help center IA:
- <category> -> <articles and escalation>
Article template:
- Problem:
- Applies to:
- Steps:
- If this fails:
- Contact/support:
Quality checks:
- <check>
Comments
Markdown supported