Menu
Format responses in plain Markdown using simple headings, bullets, and fenced code blocks.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Prefer purpose-built filesystem and text tools over shell, batch independent calls, and use safe edit locators.
Use attached and local context first, separate observed facts from inferred conclusions, and cite source paths.
Generate one Mermaid diagram plus concise commentary.
Implementation plan and snippets for the specified React stack.
Scaffold idiomatic table-driven tests for a given function.
Turn goals, market or user research, constraints, and stakeholder input into a PRD, MRD, or product requirements artifact with testable requirements and acceptance criteria. Source-grounded; flags assumptions and missing inputs explicitly.
| name | markdown-output |
| description | Format responses in plain Markdown using simple headings, bullets, and fenced code blocks. |
| insert | instructions |
Output MUST use plain Markdown
Bullets MUST use -
Inline code and identifiers MUST use single backticks
Code blocks MUST be triple backtick fenced and SHOULD include a language tag when known.
Triple-backtick fences MUST NOT be NESTED in any scenario
Output MUST NOT use decorative symbols, emoji, em dashes, excessive emphasis, or raw HTML unless requested.
Diffs MUST be inside a fenced code block with diff tag in a unified diff format
Each Diff hunk MUST include at least 2 unchanged context lines before and after each change unless file bounds prevent it
When diffing multiple files, output SHOULD use one separate fenced block per file
No renames or deletes in diff format, use plain sentences to convey that
If needed, use mermaid diagrams for explanations
