5.1K skills · sorted by relevance
Add subtle vertical guides and small corner squares to web pages using CSS and HTML patterns. Align them with the content width across sections, preserve mobile spacing, and keep the guides from blocking clicks or text selection.
Fetch official documentation from Anthropic and save local snapshots through an MCP tool. Initialize both baseline and current copies, then report the section count and storage path so later refreshes can be compared against the baseline.
Find third-party mentions of Claude Code Ultimate Guide or its author's public projects. Verify evidence, remove duplicate sources, and report mentions by type, then update the relevant tracking catalog after explicit approval.
Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts. Use this skill whenever the user wants to create brand guidelines, document an existing brand, build a brand book, audit an existing style guide for completeness, or produce the artifact that other teams will reference for years. Triggers on style guide, brand guidelines, brand book, brand standards, brand manual, style sheet, brand documentation, brand reference. Also triggers when the brand identity is finished and needs to be documented for handoff to designers, developers, vendors, or future team members.
The English summary is being prepared. Showing the original description.
Tutorial patterns for documentation - learning-oriented guides that teach through guided doing. Use when writing a tutorial, learning guide, getting-started or onboarding guide, beginner/introductory guide, or any learn-by-doing hands-on guide. Builds on the docs-style core writing principles.
The English summary is being prepared. Showing the original description.
How-To guide patterns for documentation - task-oriented guides for users with specific goals. Use when writing a how-to/howto guide, task guide, procedural guide, step-by-step guide, or how-to documentation. Builds on the docs-style core writing principles.
The English summary is being prepared. Showing the original description.
Write, restructure, or review documentation — tutorials, how-to guides, reference pages, concept/explanation docs, API references, READMEs, changelogs, release notes, and troubleshooting guides. Distills documentation craft from Mintlify's guides (compiled from technical writers at Stripe, GitHub, Amplitude, and Anaconda), the Diátaxis framework (including the compass and per-type voice), the Google and Microsoft style guides, Every Page Is Page One, Write the Docs, and Docs for Developers: audience analysis, content-type selection, style and word-level rules, procedure writing, structure for humans and AI agents, code-example standards, page templates (templates.md), mechanical enforcement and llms.txt (mechanics.md), maintenance, and success metrics. Use this skill when the user asks to "write docs", "document this feature", "improve this page", "review these docs", "write a tutorial / how-to / reference page", "structure the docs", "write API documentation", "write a README / changelog", or when authoring any file under a `docs/` tree. For Skmtc docs specifically, this skill governs the *craft* (what makes the page good); the content split between skills, `llms.md`, and the docs tree is governed by `docs/skills/README.md`. Distinct from `skmtc-retro` (captures observations about work) and the `skmtc-*` operational skills (guide doing the work) — this skill guides writing *about* the work for readers.
The English summary is being prepared. Showing the original description.
Define a brand’s tone, visual standards, and messaging, then review content and assets for consistency. Includes tools to check asset names and formats, compare colors, and convert brand guidelines into reusable design settings.
Create a reusable design guide covering colors, typography, layout, and motion. Extract styles from existing sources or start from scratch, then turn the guide into instructions or code for supported video, slide, and design tools.
Review documentation, READMEs, guides, or prose against the good-docs-writing style rules. Receive structured findings with file and line references, quoted passages, and concrete rewrites. Files are edited only when explicitly requested.
Create and update Handsontable guide pages with consistent page metadata, headings, framework-specific examples, and sidebar entries. Follow the documentation site's writing conventions and generate JavaScript examples from TypeScript sources where required.
Create and maintain code comments, API specifications, documentation sites, and user guides. Apply consistent formats, document parameters and errors, validate code examples, and report which parts of the code have been documented.
Assess understanding of medical guidelines through self-assessment and short quizzes, identify priority topics, and plan revision. Study diagnostic criteria and how concepts connect, with guideline versions and sources, within an educational scope that excludes individual patient care.
Organize medical guidelines into structured learning tracks, preview upcoming units, and manage delivery using recorded progress. It also supports investigating duplicate or missed deliveries and planning transitions to new guideline versions using authoritative sources.
Use Plannotator to review plans, code changes, documents, and running local apps in a browser. This reference covers returning feedback to agents, browsing past decisions, sharing guided code reviews, and leaving questions for later replies.
Design a two-page digital guide preview that pairs a cover with a lesson page. Soft beige styling brings together the author, content highlights, a prominent quotation, and step lists for creator-brand promotional materials.
Review web interface code for accessibility, visual design, and interaction issues. This skill checks specified files against interface guidelines and returns concise findings grouped by file, with line numbers to help locate each issue.
Write and edit READMEs, guides, and other documentation using the code as evidence. Improve structure, wording, and terminology while checking related pages and links against the project's contribution process and documentation style guide.
Compare a saved baseline of Anthropic documentation with the current local snapshot, showing added, removed, and modified sections, line changes, and unchanged counts without making a network request.
Turn CHANGELOG.md entries into English and French announcement drafts for LinkedIn, Twitter/X, newsletters, and Slack. Select a release or week, highlight useful changes, and optionally choose the audience, format, and language.
Turn CHANGELOG.md entries into French and English drafts for LinkedIn, Twitter/X, newsletters, and Slack. Select a release or week, highlight changes that matter to users, and optionally save the resulting announcements.
Write how-to guides and tutorials that naturally integrate affiliate product recommendations. Triggers on: "write a how-to guide", "tutorial for [task]", "step by step guide to [goal]", "how to [verb] with [product]", "write a tutorial blog post", "guide on how to [task]", "beginner guide to [topic]", "walkthrough for [product]", "write an educational article", "how do I [task] blog post", "write a tutorial that promotes [product]".
The English summary is being prepared. Showing the original description.
Mines a pull request's review threads for lessons that generalize beyond that PR, reconstructs each against the actual code before deciding, checks whether it is already codified, and routes the genuinely-new, durable ones into Infrahub's internal documentation — `dev/knowledge/`, `dev/guides/`, `dev/guidelines/`, the `AGENTS.md` files, and `.agents/rules/` — proposing edits first and applying only with the user's approval. TRIGGER when: the user wants to turn PR review feedback into durable conventions, guidelines, or rules; capture recurring reviewer comments as internal documentation; or check whether review lessons are reflected in the knowledge/guides/guidelines/AGENTS.md/rules layer. DO NOT TRIGGER when: sweeping a feature's changes for documentation coverage across all layers → use `audit-docs`; extracting knowledge from completed spec directories → `speckit-opsmill-extract`; only replying to or resolving review threads → normal git/gh flow.
The English summary is being prepared. Showing the original description.
Writes and restructures technical documentation - READMEs, tutorials, how-to guides, user guides, architecture docs, onboarding guides, runbooks and SOPs, troubleshooting guides, release notes, and knowledge base articles - grounded in the actual code or product, with commands and examples verified where possible. Use when the user asks to document a project, feature, system, or process, write or fix a README, explain a codebase to new developers, turn notes into a guide, or make existing docs clearer. For endpoint-by-endpoint API reference or OpenAPI specs, use api-documentation-writer; for CLAUDE.md or AGENTS.md files, use claude-md-writer.
The English summary is being prepared. Showing the original description.