Complex Mermaid diagrams can become unreadable or render poorly across GitHub themes. This guide provides tested syntax, styling patterns, layout techniques, and preview steps.

Vague requests create missed details, weak acceptance criteria, and unclear execution. This skill turns them into structured specifications with assumptions, constraints, priorities, and next steps.

Teams often hide mission, values, and governance rules across scattered documents. This skill extracts those elements and turns them into a clear project constitution.

Inconsistent project documentation makes installation, use, and contribution difficult. This skill supplies structured templates, formatting guidance, and local tools for maintainable Markdown.

Service catalog metadata is hard to keep consistent across repositories. This skill analyzes repo structure and creates catalog-info.yaml guidance for service catalogs.

Repository documentation often becomes stale when dependencies, APIs, and setup steps change. This skill analyzes structure and integrations, then helps create README, API, architecture, contributing, and integration docs.

Distributed services are hard to understand when metadata is spread across repositories. This skill aggregates catalog metadata and creates diagrams, tables, and summaries for architecture review.

Developers often need current API examples without loading full documentation into the model context. This skill fetches Context7 library docs and returns focused examples, signatures, and notes.

Feature teams often lose time in lengthy or incomplete technical planning. This skill creates concise, repository-aware design documents focused on MVP delivery.

Complex technical explanations can be difficult to scan in plain prose. This skill converts them into compact ASCII diagrams with consistent visual structure.

Important architecture choices often lose their rationale over time. This skill provides structured ADR templates, examples, and review guidance for preserving decisions and trade-offs.

Release notes often miss the app changes users care about. This skill reviews Git history, follows existing Fastlane style, and updates the latest changelog.

Authoring effective Claude Code skills requires knowing structure, trigger phrasing, and progressive disclosure. This skill provides a step-by-step process and best practices to produce lean, discoverable skills that load only when needed.

Skill authors need a clear reference for structuring and describing plugin skills. This guide explains required files, optional resources, frontmatter, activation wording, and practical design guidelines.

Notebook reviews can miss narrative, technical, and teaching problems. This skill combines automated checks with a structured 20-point audit.

Reusable slash commands can be difficult to structure, document, and maintain. This skill provides patterns for Markdown prompts, frontmatter, arguments, interactions, and controlled command context.

VitePress projects require coordinated configuration, content, themes, data loading, and deployment. This skill provides focused guidance for building maintainable VitePress sites with Vue and Markdown.

Technical presentations often require code, diagrams, animation, and reliable export workflows. This skill guides Claude, Codex, and Claude Code through Slidev syntax and tooling.

Blazor components can behave incorrectly when static and interactive rendering require different interfaces. This skill explains RendererInfo checks for context-aware Razor components.

Animated floating components can lose keyboard focus when CSS starts at opacity zero. This skill explains a retry pattern and tests for Select, DropdownMenu, and Popover components.