1.6K skills · sorted by relevance
Build desktop applications with GPUI Kit, a Rust framework. Guides setup, component selection, state management, themes, and background work, and explains UI integration tests that simulate input and check component behavior.
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.
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.
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.
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.
業務システムの操作手順書を構造化して作成するスキル。STEPフォーマット （Specific/Target/Expected/Proceed）による手順記述、ANSI Z535準拠の 注意・警告分類、トラブルシューティングガイドを含む包括的な操作マニュアルを 生成する。Use when creating operations manuals, standard operating procedures (SOP), user guides, or system operation guides. Triggers: "operations manual", "操作マニュアル", "手順書作成", "SOP", "操作手順", "standard operating procedure", "ユーザーガイド", "作業手順書", "運用マニュアル"
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.
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.
Create, fill, and reformat PDFs for branded documents, digital guides, and reports. Use shared design settings and a choice of 15 cover styles to shape the document’s appearance around a consistent visual system.
Turn source code into project documentation, from a README with installation steps and examples to API references, architecture diagrams, developer guides, and changelogs. Match the scope and comment format to the project's size and programming language.
Route Remotion tasks to the relevant specialist guides, from creating videos and projects to captions, maps, and rendering. It also guides Studio preview setup, package upgrades, and troubleshooting when working inside Codex.
Organize API documentation work from endpoint discovery to OpenAPI specifications, developer guides, and tested code examples. The workflow also covers interactive documentation, documentation sites, and maintenance, helping select the phases and supporting skills needed for a task.
Write and review OpenSEO website copy, including blog posts, guides, feature pages, and FAQs. Shape content around the reader's task, preserve an existing author's voice, remove promotional filler, and verify product claims against the code.
Design and review desktop interfaces built with GPUI Kit. Applies rules for layouts, colors, components, interaction states, and interface wording, with checks for keyboard access, focus behavior, and accessibility before finishing the work.
Navigate a smart contract security knowledge base in a suggested reading order. Find guides covering audit preparation, vulnerability patterns, code searches, reproduction tests, reporting, case studies, and AI tools without losing track of the next topic.
Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as ai-sdk.dev and chat-sdk.dev. Use for getting-started guides, tutorials, API references, conceptual explanations, integration guides, migration guides, troubleshooting, and code examples.
The English summary is being prepared. Showing the original description.
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment, research synthesis, interview transcripts, research reports, running studies with AI, or explicitly mentions Cookiy AI. Also trigger when users want to talk to customers, conduct discovery research, create a study or survey, analyze interview data, run AI-moderated interviews, or collect survey responses. Covers the full lifecycle: planning studies, creating discussion guides, running AI-moderated interviews (real or synthetic) via Cookiy, designing and distributing surveys, and synthesizing results into reports.
The English summary is being prepared. Showing the original description.
Guides the agent to reference official MathWorks Documentation and Help. Determine correct function syntax and workflows from user guides when deeper context is needed. Minimize iterations and repetitive trial and error. Use this skill to: Identify correct syntax and configuration details. Retrieve relevant, version-specific (or release-specific) information from official documentation. Consult user guides when conceptual or workflow context is needed. Apply best practices.
The English summary is being prepared. Showing the original description.
Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation. Use when creating OpenAPI/Swagger specs, generating SDKs, writing user guides, creating README files, documenting architecture, writing design specs, creating ADRs, writing migration guides, or generating changelogs from git commits. Handles versioning, examples, developer experience, and user-facing documentation.
The English summary is being prepared. Showing the original description.
Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as ai-sdk.dev and chat-sdk.dev. Use for getting-started guides, tutorials, API references, conceptual explanations, integration guides, migration guides, troubleshooting, and code examples.
The English summary is being prepared. Showing the original description.
Reconstructed reference notes on US NRC software assurance guidance for digital computer software in nuclear power plant safety systems, built from seven public-domain sources (Regulatory Guide 1.168 Revision 2, July 2013; Regulatory Guides 1.169, 1.170, 1.171, 1.172, and 1.173 Revision 1, July 2013; NUREG-0800 Branch Technical Position 7-14 Revision 6, August 2016; pinned 2026-10-12). Use for software life cycle process questions, software requirements specifications, software configuration management plans, verification and validation with reviews and audits, test documentation and unit testing, and what NRC staff examine in a BTP 7-14 software review of plans, implementation, and design outputs. SCOPE LIMITS: NRC Regulatory Guides and the BTP 7-14 staff review position only; the endorsed IEEE standards (IEEE Std 603-1991, 7-4.3.2-2003, 828-2005, 829-2008, 830-1998, 1008-1987, 1012-2004, 1028-2008, 1074-2006), IEC 60880, IEC 61513, IEC 62138, and IAEA guides are cited by designation and edition only, with no standard text; RG 1.152 Rev 4, BTP 7-18, BTP 7-19, other SRP Chapter 7 sections, and NUREG/CR contractor reports are outside the pack; reflects the pinned 2013 and 2016 editions, not later agency actions; synthesized reference notes, not legal or licensing advice and not a substitute for the source documents. LICENCE: Public Domain (US Government work, 17 U.S.C. § 105).
The English summary is being prepared. Showing the original description.
Guides implementation of signup confirmations, password resets, and other application emails through Mailtrap. Covers API authentication, verified sending domains, separate testing environments that capture messages without delivery, and handling failed send requests.
Create missing documentation for a feature, module, or whole project. Use Diataxis, a framework that separates tutorials, practical guides, reference information, and explanations, to organize documents around what readers need to learn or accomplish.
Design APIs and interfaces between modules with clear inputs, outputs, naming, and errors. The skill guides compatible extensions, input validation, and retry handling so callers can use interfaces consistently without accidentally repeating state-changing operations.