Loading...
Loading...
Found 57 Skills
Formats markdown files according to best practices and common style guidelines. Use when cleaning up markdown documentation, ensuring consistent formatting, or standardizing README files.
Creates 4 root documentation files (CLAUDE.md, docs/README.md, documentation_standards.md, principles.md). L3 Worker invoked by ln-110-project-docs-coordinator.
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation.
Implement and maintain GitHub project documentation using a layered system. Use when creating, updating, or auditing documentation.
Best practices for organizing project folders, file naming conventions, and directory structure standards for research and development projects
Guides creation of high-quality SHARE.md files for shareful.ai. Covers repo setup, frontmatter, required sections, and validation. Use when the user wants to create a share, document a coding solution, contribute to shareful.ai, or run npx shareful-ai create.
Create and maintain technical documentation including READMEs, API docs, architecture decision records (ADRs), and user guides. Use this skill when writing project documentation, documenting APIs, recording architectural decisions, creating how-to guides, or establishing documentation standards.
Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.
Use when the user requests Chinese or Traditional Chinese output for responses, comments, docs, or localization, following Taiwan terminology (zh-Hant-TW/zh-TW/zh_TW).
This skill should be used when content teaches patterns (skills, subagents, ADRs, PHRs, specifications) that have canonical sources elsewhere. Prevents format drift by ensuring content references and follows the authoritative format from canonical sources. Use before implementing lessons that teach platform patterns, or when reviewing content for format consistency.
PDCA document templates for consistent documentation. Plan, Design, Analysis, and Report templates with proper structure. Use proactively when generating PDCA documents to ensure consistent format. Triggers: template, plan document, design document, analysis document, report, 템플릿, 계획서, 설계서, 분석서, 보고서, テンプレート, 計画書, 設計書, 模板, 计划书, 设计书, plantilla, documento de plan, documento de diseño, documento de análisis, informe, modèle, document de plan, document de conception, document d'analyse, rapport, Vorlage, Plandokument, Designdokument, Analysedokument, Bericht, modello, documento di piano, documento di progettazione, documento di analisi, rapporto Do NOT use for: code implementation, deployment, or non-documentation tasks.
Save an archival summary of an AI conversation to Nathan's Obsidian vault, using Nathan's Thinking note template and vault folder conventions to capture intellectual journeys, key insights, and technical logs. Use when archiving a chat session to Nathan's Obsidian vault.