On-demand Mermaid diagram creation from a natural-language description. Follows OutSystems brand guidelines. Optionally inserts the result into a markdown article. Use when a content developer wants to create a specific diagram without going through article analysis. For auditing an article and deciding where diagrams are needed, use /suggest-visuals instead. Trigger phrases: "create a diagram", "make a diagram", "I want a diagram", "new diagram", "create a mermaid diagram", "generate a diagram".
Analyses an existing markdown article and suggests the right visual assets — Mermaid diagrams or screenshots — based on coverage-type and audience frontmatter fields. Follows OutSystems brand guidelines. Proposes diagram placement with rationale and inserts accepted diagrams interactively. Recommends screenshots where the coverage type calls for them. Use when a content developer wants to audit an article for missing visuals, or when asked to "add diagrams", "suggest visuals", "diagram this article", or "add visuals to my article". For creating a standalone diagram without an article, use /create-diagram instead. Trigger phrases: "add diagrams", "diagram this article", "suggest visuals", "add visuals to my article".
Review the images in a single Markdown file, flagging missing or placeholder alt text and stale titles, and proposing accurate alt text and a matching short title drawn from surrounding context (headings, body text, procedure steps), only opening the image itself as a last resort when that context is too thin. Skips Marp slide decks entirely (front-matter contains marp: true), since there's no accessibility payoff to reviewing them. Updates existing alt text and titles only when they are missing, a placeholder, stale, or demonstrably wrong, never for stylistic rewording.
Validates PNG screenshots in an OutSystems docs article against the team's visual rules (highlight components, shadow, cursor, naming, cropping). Returns a short issues-only summary so the content developer knows whether the images are ready for design review. Use when a content developer wants to check their screenshots before merging, or asks to "review screenshots", "check my screenshots", "validate screenshots", "screenshot review". Trigger phrases: "validate screenshots", "review screenshots", "check my screenshots", "are these screenshots good", "screenshot review".
Identify the coverage types for a given content piece based on Bloom's taxonomy. This is used to inform content design and ensure proper coverage measurement.
Identify key target audiences for a given content piece based on the actual content of the piece, not just the topic. This is used to inform content design and ensure the right audiences are addressed.
Fix style guide errors on a file. Checks IDE diagnostics first, then runs vale and markdownlint only if IDE diagnostics are unavailable or empty. Falls back to the PR comment marked with the sticky marker "STYLE GUIDE VALIDATION" only when the prompt explicitly instructs it. Use when asked to fix style guide errors on a file.
Step-by-step content creation workflow for documentation and training materials. Includes MCP validation, discovery, content design, Jira planning, and draft generation with priority-based execution. Use when starting the content creation flow, creating documentation or training materials, or when the user asks to follow the content creation workflow.