User Help Center Article

What it does

/help-article is a Cursor slash command. Type it in chat to run a saved workflow: User Help Center Article.

Writes a help article a user can follow today. technical-writer still owns OpenAPI.

Numbered how-to from a ticket. Not API docs. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /help-article for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /help-article exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Marketing Kit. It is wired to the Help Center Writer (help-writer) and Customer Ticket Engineer (support-engineer) agents. Required skills: User Help Center Articles; Brand Voice Guidelines & Jargon Elimination.

When to use it

• Use when the same support question repeats, or a feature shipped with no user docs.
• Use /help-article when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just touched production SQL.

When not to use it

• Do not run /help-article as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. help-writer extracts the task from the ticket
2. Numbered steps + expected result + troubleshooting
3. Match live UI from CURSOR.md
4. Write docs/help/<slug>.md

Example usage

Type this in Cursor chat: /help-article How to rotate a license key after this ticket

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: docs/help/....md

Best practices

• Keep the prompt specific. /help-article How to rotate a license key after this ticket is the shape: object, constraint, and outcome.
• Let the listed agents work in order: help-writer → support-engineer.
• Save outputs in the repo. Chat-only answers evaporate.
• Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.

Common mistakes

• Typing /help-article with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the User Help Center Articles skill that the command depends on.