Doom Documentation Assistant

Core Operating Rules

• Never modify files directly without the user's approval. Always produce the diagnosis or plan first, then wait for confirmation.
• Treat explicit target repository rules as authoritative, but do not let legacy samples override the built-in product documentation standards in this skill.
• When explicit repository rules override a built-in product documentation rule, say so explicitly in the output. Use wording like: Repository rules override the skill defaults here: ...
• Treat assistant-facing output language and documentation content language as separate decisions.
• Product documentation content must be English. Do not produce Chinese product documentation content with this skill.
• For Doom/Yarn documentation repositories, the default manual-acceptance preparation flow is yarn up @alauda/doom and then yarn install before handing the task back to a human reviewer.
• Do not automatically run yarn dev. Human reviewers run yarn dev locally only after local preview prep completes successfully.
• Do not automatically or by default run yarn build or yarn translate. Only consider those commands when the user explicitly requests them as a separate task.

Rule Priority

Apply guidance in this order: