home/categories/technical-docs
category focus

Tech Docs

API references and manuals.

2137 skillsall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
technical-docs
854

paper2code

Converts an arxiv paper into a minimal, citation-anchored Python implementation. Trigger when user runs /paper2code with an arxiv URL or paper ID, says "implement this paper", or pastes an arxiv link asking for implementation. Flags all ambiguities honestly. Never invents implementation details not stated in the paper.

PrathamLearnsToCode
PrathamLearnsToCode
documentation
open
technical-docs
852

migrate-component-docs-from-figma

Write or rewrite SEED Design component guideline docs (MDX) by extracting content and images from Figma documentation layers. Use this skill whenever the user wants to create, update, or migrate component documentation from Figma into docs/content/docs/components/, provides a Figma node URL for documentation, or asks to write/update a component guideline page. Also triggers for "write the docs for X component", "create guideline from Figma", "update the MDX for [component]", "가이드라인 문서 작성", or "피그마에서 문서 가져오기".

daangn
daangn
documentation
open
technical-docs
846

create-skill

Create new skills for Claude Code. Use when users ask to create a skill, add a skill, make a new command, build a skill, add a slash command, create a plugin skill, or define a new automation. Trigger phrases include "create a skill", "new skill", "add a skill", "make a command", "build a skill", "I want a skill that", "add slash command", "create automation".

moazbuilds
moazbuilds
documentation
open
technical-docs
844

design-doc

Write a tight, readable design document for a proposed change. Use when asked to write a design doc, spec, or technical proposal.

marin-community
marin-community
documentation
open
technical-docs
844

writing-style

Write in Marin's house style for public and internal text. Use when drafting or revising blog posts, technical reports, documentation, GitHub issues, experiment issues, Discord updates, or other Marin-authored writing.

marin-community
marin-community
documentation
open
technical-docs
841

aris-paper-plan

Generate a structured paper outline from review conclusions and experiment results. Use when user says "写大纲", "paper outline", "plan the paper", "论文规划", or wants to create a paper plan before writing.

OpenLAIR
OpenLAIR
documentation
open
technical-docs
841

inno-experiment-dev

Creates implementation plan, writes project code with judge feedback loop, and submits final experiment run. Use after code-survey in both Idea and Plan branches.

OpenLAIR
OpenLAIR
documentation
open
technical-docs
829

docs-writer-reference

Reference page structure, templates, and writing patterns for src/content/reference/. For components, see /docs-components. For code examples, see /docs-sandpack.

reactjs
reactjs
documentation
open
technical-docs
815

skill-creator

Create or refine KiraClaw/Codex skills as concise SKILL.md packages. Trigger on: "make a skill", "create a skill", "update this skill", "seed skill", "default skill", or when the user wants reusable agent workflow instructions instead of one-off prompt text.

krafton-ai
krafton-ai
documentation
open
technical-docs
814

sandbox-sdk

Build sandboxed applications for secure code execution. Load when building AI code execution, code interpreters, CI/CD systems, interactive dev environments, or executing untrusted code. Covers Sandbox SDK lifecycle, commands, files, code interpreter, and preview URLs. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

cloudflare
cloudflare
documentation
open
technical-docs
813

sync-docs

Synchronize documentation after code changes. Use when user says "update docs", "sync documentation", "update README", "update architecture diagram", or after a significant feature/refactoring is complete.

zevorn
zevorn
documentation
open
technical-docs
812

component-guidelines-docs

Generate comprehensive component guideline documentation for SEED Design System. Use when creating or updating design guideline documentation in ./docs/content/docs/components directory. This skill helps create high-quality documentation similar to action-button.mdx.

daangn
daangn
documentation
open
technical-docs
812

react-docs-generator

Generate React component documentation for SEED Design System. Use when creating new React component docs in ./docs/content/react/components or updating existing implementation documentation. Helps document component APIs, props, installation, and usage examples.

daangn
daangn
documentation
open
technical-docs
812

release

Publish the current R Weekly draft as a new weekly post. Use when an editor invokes /release or asks to "release", "publish", or "create the weekly post" from draft.md. Validates the draft before creating the file in _posts/.

rweekly
rweekly
documentation
open
technical-docs
807

axiom-apple-docs-research

Use when researching Apple frameworks, APIs, or WWDC sessions - provides techniques for retrieving full transcripts, code samples, and documentation using Chrome browser and sosumi.ai

CharlesWiltgen
CharlesWiltgen
documentation
open
technical-docs
807

axiom-foundation-models-ref

Reference — Complete Foundation Models framework guide covering LanguageModelSession, @Generable, @Guide, Tool protocol, streaming, dynamic schemas, built-in use cases, and all WWDC 2025 code examples

CharlesWiltgen
CharlesWiltgen
documentation
open
technical-docs
790

sdk-update

Guide for updating SDKs when REST API changes are made. Use when the user modifies REST API endpoints, request/response models, or the OpenAPI spec.

Apicurio
Apicurio
documentation
open
technical-docs
788

docsupdate-docs

Update and maintain project documentation for local code changes using multi-agent workflow with tech-writer agents. Covers docs/, READMEs, JSDoc, and API documentation.

NeoLabHQ
NeoLabHQ
documentation
open
technical-docs
784

octocode-rfc-generator

Research-driven RFC and design document generator. Use when the user asks to "create an RFC", "write a design doc", "propose a migration", "how should we architect X", "evaluate options for X", "write a technical proposal", "compare approaches", or needs a technical decision document before coding. Outputs a validated RFC with research evidence, alternatives, recommendation, and implementation plan. For planning with implementation, use octocode-plan instead.

bgauryy
bgauryy
documentation
open
technical-docs
776

skill-creator

创建新的 Claude Code 技能,修改和优化已有技能。当用户想从头创建技能、将当前工作流封装为技能、优化已有技能的内容或触发描述时使用此技能。即使用户没有明确说"技能",当他们想把某个重复工作流程固定下来时也应使用。

KroMiose
KroMiose
documentation
open
technical-docs
769

style-guide

MongoDB documentation style rules. Apply when writing or editing rST documentation.

mongodb
mongodb
documentation
open
technical-docs
759

figma-implement-design

Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.

openai
openai
documentation
open
technical-docs
759

google-drive-comments

Write, reply to, and resolve Google Drive comments on Docs, Sheets, Slides, and Drive files with evidence-backed location context. Use when the user asks to leave comments, review a file with comments, respond to comment threads, or resolve Drive comments.

openai
openai
documentation
open
Previous
Page 26 / 90
Next