Teams lose context when technical choices are made without a durable record. This skill creates clear ADRs that capture options, rationale, consequences, and reversal cost.

Teams need consistent structures for reusable domain guidance. This skill provides a customizable template for frameworks, processes, outputs, anti-patterns, and intake questions.

Turkish software teams need consistent documentation, comments, commit messages, and terminology. This skill helps Claude, Codex, and Claude Code produce clear Turkish developer text.

UML diagrams often become confusing when they mix structure, behavior, lifecycle, and deployment concerns. This skill helps Claude, Codex, and Claude Code choose the right UML form and improve diagram clarity.

Document identifiers can become inconsistent when files move or change across a Git repository. Shirushi provides commands and conventions for stable IDs, references, and integrity checks.

Incomplete documentation makes software harder to understand, use, and maintain. This skill creates structured README files, API references, docstrings, comments, and language-specific examples.

Scattered documentation makes projects difficult to navigate and maintain. This skill designs clear structures and guides tool selection, migrations, standards, versioning, and automation.

Incomplete documentation causes broken links, missing guides, and inconsistent project information. This skill audits Logseq Template Graph documentation and provides prioritized fixes.

Incomplete documentation makes code harder to use, maintain, and review. This skill measures coverage and quality, identifies gaps, and prioritizes improvements.

FlowGram material components need consistent docs, runnable Story examples, API tables, and bilingual review steps. This skill gives Claude, Codex, and Claude Code a structured workflow for producing those assets.

New projects often start with unclear scope, missing decisions, and weak plans. This skill turns a concept into linked planning documents for Claude, Codex, and Claude Code.

Technical changes are hard for different teams to understand quickly. This skill turns project context into short role-based guides with examples, diagrams, and checks.

Detailed AI context files are often too long for quick human review. This skill turns them into summaries, quick starts, and Mermaid visual guides.

Designing reliable AI skills is hard when structure, triggers, and validation rules are unclear. This skill guides Claude, Codex, and Claude Code through templates, naming rules, and quality checks.

Python documentation often becomes incomplete or inconsistent when maintained manually. This skill converts source structure, docstrings, and type hints into organized Markdown.

Planning long learning resources requires coordinated outlines, tasks, personas, context, and project instructions. This skill generates five aligned Markdown documents from reusable templates.

Writing reliable mathematical notation in Obsidian requires precise MathJax syntax. This skill supplies practical patterns and a detailed reference for common formulas.

Generic learning resources often miss domain conventions and evidence standards. This skill provides tailored research, terminology, structure, and review guidance for five domains.

Solved technical issues often disappear inside chat history. This skill converts confirmed fixes into searchable solution documents and promotes recurring issues into reusable patterns.

Reviewers waste time when pull requests lack context, testing evidence, and diagrams. This skill guides Claude, Codex, and Claude Code to produce structured PR descriptions.