Documentation
Documentation tools and technical writing skills
6825 skills in this category
Subcategories
practice-hub-testing
Comprehensive testing workflows for Practice Hub including Vitest configuration, tRPC router testing, multi-tenant validation, Better Auth flows, and component testing. Use for writing tests, validating multi-tenant isolation, and ensuring production readiness.
direct-mail-strategist
Expert direct mail marketing strategist for writing compelling copy, designing high-converting mail pieces, and developing measurement strategies. Use when planning direct mail campaigns, writing mailer copy, designing postcards/letters, or measuring campaign effectiveness with incremental lift analysis.
screen-spec-guide
画面ID(SAPP-CTG-030 など)から仕様・ワイヤーフレーム・Figma ノードを特定し、関連ドキュメントや画面遷移を横断して確認したいときに使います。docs/2-requirements/24-画面一覧.csv・23-画面設計.md・assets/*.svg・figma・docs/3-external/31-画面遷移図.md を参照して要件を整理する用途を想定しています。
documentation-audit
Systematic documentation audit that validates every documentation claim against code and identifies undocumented features - executable as a repeatable Claude Code skill (project)
testing-pest
Generate comprehensive Pest test suites for Laravel projects including tests for controllers, services, Livewire components, commands, jobs, and models with proper describe blocks for organization, mocking setup, happy path and failure scenarios, RefreshDatabase trait, and coverage for all public methods. Use this skill when creating test files for new features, adding test coverage for controllers or services, writing tests for API endpoints, testing Livewire components, ensuring proper test structure with beforeEach and describe blocks, implementing mocking strategies, or writing dataset-driven tests. This skill applies when working on files in tests/Feature/ or tests/Unit/ directories, creating Pest test files, or ensuring comprehensive test coverage.
uml-diagram
Generate UML diagrams including class, sequence, and use case diagrams. Use when modeling software systems or documenting architecture.
tdd-red-phase
Guide through RED phase - writing failing tests and verifying failures
wastewise-regulatory
WasteWise Complete Analysis with automated regulatory compliance research and LLM Judge validation. Includes all standard analysis features PLUS automated ordinance research, compliance checklists, and quality-scored evaluation. Use when you need both waste analysis AND regulatory compliance documentation.
software-principles
Core software engineering principles including DRY, SOLID, KISS, and YAGNI for writing maintainable and scalable code
write-issue
Create or update project issues following the standardized format with Functional Specifications (Preconditions/Workflow/Postconditions), Technical Specifications, and hierarchical task lists. Use when user asks to create/update an issue, document requirements, or write specifications for a new feature.
design-spec-extraction
Extract comprehensive JSON design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant output with component trees, suitable for code generation, design documentation, and developer handoff.
adr-log
Document architecture decisions with ADR (Architecture Decision Records). Use when making significant technical decisions, choosing between alternatives, or when onboarding needs context on past decisions.
testing-standards
Standards and best practices for writing effective tests including the testing pyramid, test structure patterns, and coverage guidelines
moai-library-mermaid
Enterprise Mermaid diagramming skill for Claude Code using MCP Playwright
moai-alfred-config-schema
.moai/config.json official schema documentation, structure validation, project metadata, language settings, and configuration migration guide. Use when setting up project configuration or understanding config.json structure.
pop-next-action
Context-aware recommendation engine that analyzes git status, TypeScript errors, GitHub issues, and technical debt to suggest prioritized next actions. Returns specific popkit commands with explanations of why each is relevant. Use when unsure what to work on next, starting a session, or feeling stuck. Do NOT use when you already know what to do - just proceed with that task directly.
docs-seeker
Search technical documentation using executable scripts to detect query type, fetch from llms.txt sources (context7.com), and analyze results. Use when user needs: (1) Topic-specific documentation (features/components/concepts), (2) Library/framework documentation, (3) GitHub repository analysis, (4) Documentation discovery with automated agent distribution strategy | Dùng khi tìm tài liệu, hướng dẫn, docs, documentation, api docs, tham khảo.
github-repo-hunter
Autonomous GitHub repository discovery and integration agent that hunts relevant open-source projects for BidDeed.AI (foreclosure auctions) and Life OS (productivity/ADHD). Searches GitHub for repos matching domain keywords, evaluates relevance via README/tech stack analysis, auto-adds as submodules or archives to target repos, and alerts Ariel with actionable summaries. Use when (1) User requests "find relevant GitHub repos", (2) Exploring new integrations for BidDeed.AI workflows, (3) Discovering productivity tools for Life OS, (4) Keeping repositories updated with latest open-source innovations.
walkthrough
Generate step-by-step walkthrough guides for testing features or bug fixes. Use when the user asks to create testing instructions, QA guides, walkthrough documentation, or says something like "write a walkthrough" or "create testing steps" after implementing a feature.
confluence-board
Manage Confluence pages and spaces. Use when the user wants to: (1) List, create, update, or delete Confluence pages, (2) Search content across spaces, (3) View or manage spaces, (4) Read or update page content, (5) Manage page attachments. Requires environment variables CONFLUENCE_URL, CONFLUENCE_USERNAME, CONFLUENCE_API_TOKEN, and optionally CONFLUENCE_SPACES_FILTER.