Technical Writing
5624 skills in Documentation > Technical Writing
repo-maintainer
Audits and reorganizes messy repositories into clean, LLM-friendly structures. It uses a non-destructive "Migration Manifest" process to safely consolidate scripts, establish documentation, and create AI context zones.
organize-folders
Provides guidance on organizing folder structures and file system layouts for any project. Use when planning project organization, reorganizing messy directories, setting up folder hierarchies, creating folder structures, designing directory layouts, organizing drafts and published content, structuring repositories, cleaning up file layouts, arranging files, or need help with folder structure or file organization. Helps with writing projects, code projects, document collections, or any file organization task. Provides guidance for creating appropriate folder structures, organizing versions, implementing simple systems, following user preferences.
moai-workflow-jit-docs
Enhanced Just-In-Time document loading system that intelligently discovers, loads, and caches relevant documentation based on user intent and project context. Use when users need specific documentation, when working with new technologies, when answering domain-specific questions, or when context indicates documentation gaps.
ln-140-test-docs-creator
Creates test documentation (testing-strategy.md + tests/README.md). Establishes testing philosophy and Story-Level Test Task Pattern. L2 Worker in ln-100-documents-pipeline workflow.
refactor-code-readme
This skill should be used when the user asks "refactor code", "improve code quality", "use refactor plugin", "run /refactor", or needs guidance on automated iterative code refactoring with test coverage, architecture review, and clean code improvements.
voice-and-tone
Defines brand voice persona and tone calibration using persona and positioning data to produce a reusable meta-prompt for copywriting.
testing
Automate test writing for AgentOS project with proper conventions. Applies layer-specific test patterns (Unit/E2E/Electron-E2E) based on code location and generates consistent test code following Given-When-Then structure.
planning-and-building
Approach for planning and implementing code changes. Use when starting new features, starting bug fixes, beginning any implementation work, or when unsure how to approach a coding task. Covers learning the codebase first, verifying approaches, and writing simple maintainable code.
writing-style
Writing guidelines for clear, economical prose. Reference this skill when creating or enhancing note content.
generating-commit-messages
Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.
code-review-assistant
Comprehensive PR review using multi-agent swarm with specialized reviewers for security, performance, style, tests, and documentation. Provides detailed feedback with auto-fix suggestions and merge readiness assessment.
raouf-change-protocol
Before making any code changes, read AGENT.md/agent.md and changelog variants (CHANGELOG*.md, HISTORY.md, RELEASES.md). After changes, update both agent + changelog files with a "Raouf:" template entry. If blocked, search latest official developer docs and use all available tools/MCPs.
code-hygiene
Apply code hygiene standards for clean, maintainable code. Use when writing, refactoring, or reviewing code.
loki
Guide for implementing Grafana Loki - a horizontally scalable, highly available log aggregation system. Use when configuring Loki deployments, setting up storage backends (S3, Azure Blob, GCS), writing LogQL queries, configuring retention and compaction, deploying via Helm, integrating with OpenTelemetry, or troubleshooting Loki issues on Kubernetes.
require-why-when-how-docs
Require comprehensive WHY/WHEN/HOW documentation for all functions. Apply when writing functions, classes, or complex logic to explain purpose, usage context, and implementation approach.
new-agent
Create a new underwriting agent (assets, credit, collateral) following established patterns. Use when implementing new agents, extending the system with new document analysis capabilities, or understanding how agents work.
documentation-writer
Activates when creating or improving technical documentation, READMEs, and API docs
doc-maintainer
Maintains high-quality, concise, project-aligned documentation. Creates, updates, and validates README.md, CLAUDE.md, code comments, and other documentation. Activates after implementing features, when documentation is outdated, or when explicitly requested.
code-style
代码风格规范 / Code style conventions。在编写、编辑、评审 Python 代码时使用。包括类型注解、Decimal 精度、Docstring、模块组织等规范。Use when writing, editing, or reviewing Python code. Enforces type hints, Decimal precision, docstrings, and module organization.
arcanea-technical-writing
Technical writing excellence - documentation, API references, tutorials, and guides that users actually understand. Clear, accurate, useful.