Documentation

Use the docmgr CLI to manage ticketed docs (create tickets, add docs, relate code files with file-note, update changelog, and search). Use when the user asks how to use docmgr, wants a docmgr command sequence, or needs docmgr best practices (file-note, quoting, doctor).

Develop, test, and document the PikaCSS monorepo (core engine, unplugin adapters, Vite/Nuxt plugins, docs site) using pnpm-based workflows.

Convert Deckset-format markdown slides with speaker notes to presentation video with TTS narration. Use when user requests to create video from slides, generate presentation video, or convert slides to MP4 format.

Generates metadata for research documents and specifications including date/time, git commit, branch, and repository info. Use when creating research documents, handoffs, or any documentation that needs timestamp and git metadata.

Create Obsidian-compatible Mermaid diagrams. Prefer square layouts (TB + subgraph LR), avoid markdown in labels. Use when creating flowcharts, sequence diagrams, or any Mermaid diagrams in markdown files.

HODD-RUST: Validation-first Rust development. Strictly validation-first before-and-after(-and-while) planning and execution. Merges Type-driven + Spec-first + Proof-driven + Design-by-contracts. Use for Rust projects requiring formal verification, safety proofs, comprehensive validation, or when working with unsafe code, concurrency, or FFI boundaries. This skill provides both reference documentation AND execution capabilities for the full PLAN -> CREATE -> VERIFY -> REMEDIATE workflow.

Write focused tests for core user flows and critical business logic, testing behavior rather than implementation, with clear names and fast execution. Use this skill when writing unit tests, integration tests, or end-to-end tests. When testing critical user workflows and primary application features. When creating tests that focus on what code does rather than how it does it. When mocking external dependencies like databases, APIs, or file systems. When naming tests to clearly describe the scenario and expected outcome. When keeping tests fast and independent. When completing feature implementation and adding strategic tests at logical completion points. When working with test files or test frameworks.

Escalation path when stuck on pattern development. Use when encountering TypeScript errors, framework confusion, unexpected behavior, or blocked progress. Five-step recovery: check docs, study examples, strategic investigation (plan mode + subagents), reset and retry, ask user.

Format and validate Obsidian wiki links with proper filename, section, and folder conventions. Verify links exist before creation and fix broken links. Use when creating or checking wiki links in markdown files.

Core Python development concepts, idioms, best practices, and language features.Covers Python 3.10+ features, type hints, async/await, and Pythonic patterns.For running scripts, see uv-run. For project setup, see uv-project-management.Use when user mentions Python, type hints, async Python, decorators, context managers,or writing Pythonic code.

Validate and enforce markdown document structure including frontmatter positioning, heading hierarchy, and content organization. Use when creating or validating markdown files.

Analyze codebases for anti-patterns, code smells, and quality issues using ast-grep structural pattern matching. Use when reviewing code quality, identifying technical debt, or performing comprehensive code analysis across JavaScript, TypeScript, Python, Vue, React, or other supported languages.

Playwright end-to-end testing for web applications. Cross-browser testing (Chromium, Firefox, WebKit),visual regression, API testing, mobile emulation. Use when writing E2E tests, testing across browsers,or setting up automated UI testing workflows.

Maintain consistent code formatting, naming conventions, and structure across the entire codebase with automated tools and clear standards. Use this skill when writing any code in any language or framework. When naming variables, functions, classes, or files. When formatting code with proper indentation and line breaks. When refactoring code to remove duplication or extract reusable functions. When running linters or formatters to ensure consistency. When removing dead code, unused imports, or commented-out blocks. When applying DRY principles to avoid code duplication. This skill applies universally to all programming tasks.

Idiomatic Rust patterns for pikru C port. Use when writing or reviewing Rust code ported from C. Don't write C in Rust - the goal is correct behavior, not line-by-line translation.

Conventions and style guidelines for dgroomes' personal projects. Use when upgrading, maintaining, or creating projects in dgroomes' repositories. Covers README style, Gradle configuration, version catalogs, commit messages, and general code conventions.

This skill enables GitHub repository documentation exploration using DeepWiki API directly via curl. Use when researching repository structure, understanding library APIs, or asking questions about open-source projects. MCP server not required.

Restore a project from 99-archive, a remote git repo, or a local codebase back to the workspace root, including reconstructing missing docs, stages, and sprints. Use when the user asks to resume work on an existing project.

Investigate website structure and debug web scraping using Chrome DevTools MCP. Use when analyzing documentation frameworks, debugging extraction issues, understanding HTML structure, investigating why web content isn't being captured correctly, or exploring API documentation sites. Covers Redocly, Swagger UI, and other modern documentation frameworks.

Translate MDX articles between English and Japanese for global engineers. Use when the user says "translate this article", "convert to Japanese/English", or asks to localize content in `src/content/docs/`. Auto-detects source language and outputs to the correct i18n path.