Total 53,207 skills, Documentation & Writing has 1507 skills
Showing 7 of 1507 skills
Generate comprehensive technical documentation for developers taking over an AEM Edge Delivery Services project. Use when onboarding developers, creating technical handover documentation, or documenting a project's architecture — analyzes codebase structure, custom implementations, design tokens, and produces a complete developer guide.
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.
Use when writing or reviewing anything that will be read as true — a decision record, a README, an acceptance report, a runbook, a changelog entry, an audit finding, or any claim that something was verified. Applies the ten canons of evidence-backed documentation — what makes a claim documentation rather than an assertion — and routes to the doctrine that enforces each one. Also use when a project needs a documentation gate, a decision register, a propagation matrix, or a retrospective that outlives its author. Triggers - 'documentation gate', 'decision record', 'ADR', 'acceptance report', 'runbook', 'is this verified', 'доказательная документация', 'записать решение', 'отчёт о приёмке', 'раннбук', 'чем это подтверждено', 'доки в синхроне'. Not for: drafts, chat answers, commit messages or code comments — say 'без доков' to opt out.
Edit drafts into sharper, more human writing while preserving the writer's personal voice, or detect AI-slop patterns without rewriting. Use when the user wants a draft clearer, more direct, more opinionated, or less AI-sounding, or asks whether writing reads as AI.
Running structured, multi-source research that produces a trustworthy, cited synthesized answer. Use when a question needs more than a single lookup — comparing options, validating a claim, surveying a market or technology, or briefing a decision where being wrong is costly. Covers scoping (and narrowing) the question, fanning out across sources, judging source quality, adversarially verifying each key claim, separating fact from inference, and reporting with explicit confidence. Keywords deep research, multi-source, fact-check, verify, synthesize, cited report, source credibility, due diligence.
Reviews and improves English text for grammar, clarity, and tone while preserving the original intent. Tailored for non-native English speakers, especially Spanish speakers. Use when proofreading emails, Slack messages, reports, meeting notes, or presentation content.
Patterns for writing clear, consistent API field descriptions including types, constraints, examples, and edge cases.