Understanding an unfamiliar Convex application requires connecting schemas, functions, authentication, and integrations. This skill produces a structured, source-grounded architecture map without modifying the application.

Website teams need a careful way to explore emerging discovery files and structured data. This skill previews candidate artifacts and keeps approval with the user before writing changes.

Long project instructions can hide important guidance and verification steps. This skill restructures them into concise root guidance and focused rule files.

Documentation updates often land in the wrong file or duplicate existing information. This skill directs the assistant to the owning documentation layer and keeps project guidance consistent.

API documentation can drift from the schemas and routes that define actual behavior. This skill guides updates from the owning source and keeps generated artifacts out of manual edits.

Teams lose context when important technical decisions remain in chat, code comments, or individual memory. This skill turns architectural reasoning, API guidance, project instructions, and release changes into structured documentation.

Teams often declare work complete without proving every requirement, path, review, and gap. This skill creates a traceable chain from intent to evidence and a defensible delivery decision.

OpenSpec tasks and archive states do not prove evidence-backed completion. This skill maps requirements, acceptance items, journeys, and gates into an auditable RVTF closure process.

BMAD work can lose traceability between requirements, reviews, tests, and closure decisions. This skill maps BMAD artifacts to RVTF records while preserving host ownership, evidence quality, and review boundaries.

Volcengine VoiceChat integrations involve changing APIs, models, audio settings, and runtime stages. This skill provides safe configuration guidance, official documentation routing, and evidence-based troubleshooting.

Technical plans often drift from product intent or the current codebase. This skill researches repository structure and turns constraints into an actionable TECH.md implementation plan.

Spec-triggered documentation created drafts for features that had not shipped. This retired skill explains the failure and directs users to release-gated alternatives.

代码改动后，README 与版本记录常被遗漏，文档容易与实现脱节。本技能读取真实代码与现有文档，按固定清单更新 README 和版本条目，并如实标注验证状态。

Architecture decisions often remain scattered across requirements, discussions, and diagrams. This skill organizes them into consistent Markdown documents for implementation and review.

Das Erstellen einer ausgereiften Awesome-Liste erfordert eine sorgfältige Struktur, Beitragsregeln und Verifizierungsschritte. Diese Skill generiert aus einem Thema und Startressourcen ein fokussiertes Repository-Scaffold.

Projektwissen ist oft über Code, Kommentare und Dokumentation verstreut. Dieser Skill verwandelt eine Codebase in verknüpfte Obsidian-Notizen für Navigation und Wartung.

Obsidian-Nutzer benötigen Notizen, die vault-freundlichen Markdown-Konventionen folgen. Dieser Skill hilft Claude, Codex und Claude Code dabei, saubere Notizen mit Obsidian-Syntax zu erstellen.

Teams benötigen gültige Canvas-Dateien, die in Obsidian und verwandten Tools funktionieren. Diese Skill leitet Claude, Codex und Claude Code dabei an, strukturierte .canvas-Karten mit Knoten, Kanten, Gruppen und Layoutregeln zu erstellen.

Technische SEO-Entscheidungen lassen sich oft schwer mit den Richtlinien von Google Search in Einklang bringen. Diese Skill nutzt die offizielle Google-Dokumentation, um Audits, Implementierungspläne und Fehlerbehebung zu unterstützen.

Release-Dokumentation ist zeitaufwendig, wenn Teams englische und chinesische READMEs benötigen. Diese Skill generiert strukturierte zweisprachige READMEs aus Repository-Metadaten und geführter Konfiguration.