8.4K skills · sorted by relevance
Write, review, and refactor modern C++ using the C++ Core Guidelines. Covers type safety, automatic resource cleanup, class design, exceptions, concurrency, and naming conventions, with examples and a checklist for identifying unsafe or inconsistent code.
Build and update Paperclip interfaces using shared rules for colors, typography, status indicators, layouts, and interactions. Reuse existing components and keep the component catalog and showcase page aligned with new or changed interface elements.
Review documentation and prose against the Vercel Writing Guidelines, checking voice, tone, formatting, and structure. Findings identify files and line numbers, using a bundled guideline snapshot as the default reference for repeatable reviews.
Find Apple interface design guidance for planning apps across iOS, macOS, visionOS, watchOS, and tvOS. This catalogue entry points to a bundle of 14 skills covering design foundations, interface components, interaction patterns, inputs, and technologies.
Use Reasonix to build or improve a Python command-line interface for existing software. The workflow covers source analysis, interactive commands, JSON output, tests, documentation, and installation checks using the software’s own backend where possible.
Build Python workflows that constrain language model output using text patterns and grammar rules. Generate structured JSON, restrict classifications to allowed labels, extract information, and combine reusable generation steps with loops and tool selection.
Review documentation and prose against the latest Writing Guidelines. Provide files or a file pattern, and the skill checks the retrieved rules and returns concise findings with file names and line numbers.
Build Python workflows that constrain language model output using text patterns and grammar rules. Generate structured JSON, restrict classifications to allowed labels, extract information, and combine reusable generation steps with loops and tool selection.
Write, review, and edit developer documentation for SDKs, libraries, and frameworks. Organize guides, API references, and code examples around readers’ tasks, checking technical claims against source code and official documentation while following the destination site’s conventions.
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.
Helps users get started with Onchain OS, find OKX.AI role registration guidance, or reach support resources. It identifies the purpose of a question and routes it to the appropriate guide.
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.
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.
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.
Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable. Produces a multi-page website (default), a single-page interactive site, a Microsoft Word document, a PowerPoint deck, or a LaTeX/PDF. Use whenever a user has a stress-test result, ambiguity audit, or "where will this be litigated" scenarios and wants to publish, present, or share them. Triggers on "publish the audit," "make a report from this," "turn this into a website / deck / brief / Word doc," "make a Netlify site," "build slides of these ambiguities," "render the scenarios," "package this stress test," "produce a LaTeX version," and similar. Pairs with the ambiguity-stress-test skill (the underlying analysis) but works on any structured or semi-structured ambiguity analysis. Visual design is opinionated but the user can override colors, fonts, and brand label. Most formats need Python and a writable filesystem; single-file HTML works where the host has neither.
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.
Reconstructed reference notes on EU and UK medical-device software, built from six sources captured 2026-10-13: MDCG 2019-11 rev.1 (June 2025), MDCG 2020-6 (April 2020), MDCG 2020-13 (July 2020), MDCG 2020-7 (April 2020), MDCG 2020-8 (April 2020), and the MHRA software-applications guidance (2023-07-01) with its stand-alone software PDF. Use for SaMD qualification and classification, legacy-device clinical evidence, the clinical evaluation assessment report, the PMCF plan, and the PMCF evaluation report, under EU MDCG guidance or UK MHRA guidance. SCOPE LIMITS: EU MDR and UK MHRA device software only; no IEC 62304, ISO 13485, or ISO 14971 text; no MDR or IVDR regulation body text; MDCG guidance is not legally binding; MHRA guidance is UK-specific; synthesized notes, not legal advice. LICENCE: Per-document: European Commission reuse policy (Decision 2011/833/EU, CC BY 4.0, attribution and indication of changes) for the MDCG documents; Open Government Licence v3.0 for the MHRA guidance; reconstructed notes with attribution; official PDFs not redistributed.
The English summary is being prepared. Showing the original description.
Design discovery, directories, and guilds for agent swarms at scale. Use when agents need to find each other on a shared surface: capability indices, yellow-pages directories, whois/phonebook routing, reputation-aware discovery, and guild structures that scope trust. Covers the canonical prior art (FIPA Directory Facilitator, Contract Net, Chord/DHT, DNS-SD/Consul, EigenTrust, Greif's merchant guilds) and the failure modes (read-poverty, Sybil reset, Goodhart on rank, directory staleness, cold-start). Triggers: "agents can't find each other", "who owns this file/skill", "route a question to the right agent", "capability registry", "agent reputation", "guild / federation of fleets". NOT for issuing identities, granting authority, or automatically assigning work from a directory entry.
The English summary is being prepared. Showing the original description.
Turn notes, transcripts, or research into polished articles, guides, tutorials, and newsletters. Use supplied writing examples or brand guidance to maintain a consistent voice, organize a clear argument, and support factual claims with provided evidence.
Build end-to-end tests that operate Windows desktop apps through pywinauto and Windows UI Automation, an interface for accessing screen controls. Covers stable element selection, waits, failure screenshots, test isolation, and CI setup for native applications.
Draft articles, guides, and newsletters in a voice drawn from supplied examples or brand guidance. Turn notes and research into structured prose, or revise existing drafts for clearer pacing, stronger evidence, and consistent style.
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.