Menü
Sync VitePress documentation with recent code changes
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Verifies factual claims in documents using web search and official sources, then proposes corrections with user confirmation. Use when the user asks to fact-check, verify information, validate claims, check accuracy, or update outdated information in documents. Supports AI model specs, technical documentation, statistics, and general factual statements.
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.
Research an external website, API, tool, or service and produce an MMPS-specific feasibility + integration plan
Plan new MMPS features by exploring the codebase and producing a structured implementation plan that follows project conventions
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
Generates optimized prompts for AI tools. Activates only when the user explicitly asks to write, fix, improve, or adapt a prompt for a specific AI tool (LLM, Cursor, Midjourney, image AI, video AI, coding agents, etc.). Does not activate for general conversation, coding tasks, document writing, or other non-prompt-engineering work.
| name | update-docs |
| description | Sync VitePress documentation with recent code changes |
Sync VitePress documentation with recent code changes.
Determine what changed: Run git diff --name-only HEAD~1 (or a broader range if the user specifies). If the user points to a specific area, focus on that.
Map changes to doc pages using this guide:
| Code area changed | Docs page to update |
|---|---|
src/features/{name}/ | docs/bots/{name}.md |
src/shared/ai/tools/ | docs/development/ai-tools.md |
src/services/{name}/ | Relevant architecture or service docs |
| Architecture patterns, new patterns | docs/architecture/*.md |
| Setup, config, env vars | docs/guide/*.md |
AGENTS.md conventions (CLAUDE.md is a symlink) | docs/architecture/*.md or docs/development/*.md |
Read the existing doc pages that need updating. Understand their current structure and style before making changes.
Update only what's needed:
Do NOT:
docs/.vitepress/) unless sidebar entries are needed for new pagesReport: After updating, list which doc files were changed and summarize what was updated in each.