Loading...
Loading...
Found 2,897 Skills
Expert documentation generator for coding projects. Analyzes codebases to create thorough, comprehensive documentation for developers and users. Supports incremental updates, multi-audience documentation, architecture decision records, and documentation health tracking. Works with any project type (APIs, CLIs, web apps, libraries). Use when you need to document a new project, update docs after adding features, or create comprehensive documentation for open source releases.
Generate a production-ready AbsolutelySkilled skill from any source: GitHub repos, documentation URLs, or domain topics (marketing, sales, TypeScript, etc.). Triggers on /skill-forge, "create a skill for X", "generate a skill from these docs", "make a skill for this repo", "build a skill about marketing", or "add X to the registry". For URLs: performs deep doc research (README, llms.txt, API references). For domains: runs a brainstorming discovery session with the user to define scope and content. Outputs a complete skill/ folder with SKILL.md, evals.json, and optionally sources.yaml, ready to PR into the AbsolutelySkilled registry.
Creative writing skill for creating canonical reference documentation (wikis) for fictional worlds, characters, and story events. Use when creating or updating wiki pages, official documentation, character profiles, location documentation, or lore pages. Creates polished, sourced, encyclopedic reference material.
Deterministic 4-phase documentation drift detector: Scan, Cross-Reference, Detect, Report. Use when skills/agents/commands are added, removed, or renamed, when README files seem outdated, or before committing documentation changes. Use for "check docs", "sync README", "documentation audit", or "stale entries". Do NOT use for writing documentation content, improving descriptions, or generating new README files.
Search DuckDB and DuckLake documentation and blog posts. Returns relevant doc chunks for a question or keyword using full-text search against a locally cached index.
Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.
Phase 3 of the feature workflow – Complete the acceptance closed loop. Two tasks: First, check layer by layer against {slug}-design.md to verify if the implementation deviates from the plan; if deviations are found, fix them immediately instead of just "noting them down" in the report. Second, integrate this feature into the project's overall architecture documentation. Finally, produce a {slug}-acceptance.md as the closed-loop proof for the entire workflow. Predecessor dependency easysdd-feature-implement must be completed. Trigger scenarios: User says "The feature is done, let's accept it", "Do the final check", "Prepare for merge", "Generate the acceptance report".
Generate comprehensive technical documentation for developers taking over an AEM Edge Delivery Services project. Analyzes codebase structure, custom implementations, design tokens, and produces a complete developer guide.
Apply Swift API Design Guidelines to name, label, and document Swift APIs. Covers argument label rules (prepositional phrase rule, grammatical phrase rule, first-label omission), mutating/nonmutating pair naming (-ed/-ing participle pattern, form- prefix, sort/sorted, formUnion/union), side-effect naming (noun for pure, verb for mutating), documentation comment structure (summary by declaration kind, O(1) complexity rule), clarity at call site, role-based naming, protocol naming (-able/-ible/-ing), default arguments over method families, casing conventions, and terminology. Use when designing new Swift APIs, reviewing naming and argument labels, writing documentation comments, or refactoring for call site clarity.
You are a **Technical Writer**, a documentation specialist who bridges the gap between engineers who build things and developers who need to use them. You write with precision, empathy for the read...
Write, edit, or review chapters of an arc42 architecture documentation. Use when user says 'write arc42', 'update the architecture documentation', 'fill out chapter 5', 'arc42 chapter', 'architecture docs', or 'document our building blocks'. Do NOT use for ADRs (use document-decision — ADRs belong inside arc42 chapter 9) or user-facing feature docs (use document-feature).
Sync documentation with code changes. Scans for README, CLAUDE.md, docs/ pages, and skills that reference behavior the current branch modifies, and updates or flags them. Use when user says 'update docs', 'sync documentation', 'is our documentation current', 'docs are stale', or 'update READMEs after this refactor'. Do NOT use for writing a fresh feature doc (use document-feature) or a new ADR (use document-decision).