26건 · 관련도순
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when drafting or revising internal technical design docs, review notes, architecture writeups, or sharing posts in Chinese, especially when the tone should stay evidence-backed, calm, and suitable for peers or leaders rather than marketing or literary writing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a substantial technical manual for one exact system version. Organize authoritative sources, record offline inputs and outputs, explain behavior with figures, and audit the text and supporting evidence for consistency.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
A skill for technical writing. This skill should be used when users want to write a technical article.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, organize, name, edit, or review Enterprise developer documentation, specifications, and technical instructions; ground claims in current source and finish with a plain-language cleanup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plans, drafts, and refines technical tutorials for developers. Use when writing step-by-step guides or getting-started walkthroughs backed by working code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Applies an ASD-STE100-derived register to operator and procedural text. Use when writing runbooks or steps. Do not use for docstrings, ADRs, or rationale.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write clear, concise, and accurate technical documentation including API references, user guides, tutorials, changelogs, and architecture docs, tailored to the target audience. Use when the user requests technical writing or provides relevant inputs for this workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build documentation websites with Docusaurus. Use when a user asks to create a documentation site, build a developer portal, set up API docs, create a knowledge base, add versioned documentation, build a static docs site with search, create a blog alongside docs, or migrate from GitBook or ReadTheDocs. Covers project setup, docs structure, versioning, custom pages, blog, Algolia search, MDX components, and deployment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The craft of communicating technical concepts clearly to developers. Developer communications isn't marketing—it's about building trust through transparency, accuracy, and genuine utility. The best devrel content helps developers solve real problems. This skill covers technical documentation, developer tutorials, API references, changelog writing, developer blog posts, and developer community engagement. Great developer communications treats developers as peers, not leads to convert. Use when "documentation, docs, tutorial, getting started, API reference, changelog, release notes, developer guide, devrel, developer relations, code examples, SDK docs, README, documentation, devrel, tutorials, api-docs, developer-experience, technical-writing, getting-started, changelogs" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Legendary blog writing that makes readers forget they're reading. This skill combines the narrative mastery of Paul Graham's essays, the technical accessibility of Julia Evans, the conversational wit of Wait But Why, and the viral mechanics of James Clear. Great blog posts don't inform—they transform. They take complex ideas and make them feel obvious. They turn strangers into superfans. They get shared not because someone should read them, but because someone needs to read them. This skill adapts to any topic: cybersecurity that reads like a thriller, AI explainers that feel like conversations, marketing insights that make you screenshot every paragraph, and coding tutorials that make you excited to build. Use when "write a blog post, blog post about, write an article, create content about, explain this topic, write about, long-form content, thought leadership, technical blog, how-to article, tutorial post, educational content, industry analysis, opinion piece, newsletter content, make this engaging, write for developers, explain like, writing, blog, content, articles, long-form, storytelling, technical-writing, thought-leadership, educational, tutorials, explainers, engagement" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rigorous engineering orchestrator ported from Lauren Tan's pstack (poteto-mode): reads your task, picks one of 23 playbooks (bug fix, feature, refactoring, perf, investigation, prototype, babysit, shipping, autonomous run, orchestrate, and more), routes to bundled procedures (how, why, architect, arena, swarm, interrogate, unslop, technical-writing, show-me-your-work, tdd, and others), and applies 24 engineering principles. Self-contained: no plugin install, no sibling skills required, works with any agent that reads skills.sh-format SKILL.md files. Use whenever a task needs rigor: nontrivial code changes, architecture decisions, debugging, reviews, PRs, long autonomous runs, or "work like poteto", "poteto-mode", "pstack".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate and improve GitHub Well-Architected Framework (WAF) documentation under the content/ folder for architectural correctness, decision quality, explicit trade-offs, and actionable guidance. Use this when reviewing pull requests, markdown files, or draft content in content/ to ensure recommendations are technically sound, context-aware, and guide readers toward correct architecture and design decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Technical documentation expert for clear, concise, user-friendly documentation and tutorials
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writes, rewrites, and reviews Chinese technical documentation, product copy, and UI microcopy using ruanyf/document-style-guide, STE-inspired Chinese methods for procedural passages, and separate product and UI extensions. Use for 中文技术写作, README, API documentation, 操作指南, 安装部署说明, 故障排查文档, 运维 Runbook, 工具描述, Agent 指令文案, 产品介绍, 功能说明, 界面文案, 按钮, 空状态, and 错误提示 when the task concerns meaning, structure, or wording. Delegates requested formatting checks to daftai-chinese-copywriting. Pure punctuation or spacing tasks belong to that skill; personal essays and author-voice articles do not belong here.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write technical documentation that matches the measured profile of professionally-written docs. Carries the craft rules derived from 114k words of pre-2022 documentation (SQLite, PostgreSQL, Python, Django, Rust, Go, Pro Git, nginx), the per-Diátaxis-type numeric targets, and the copywriting register for page leads. Use when drafting or rewriting any documentation prose, or when a page is factually right but reads as machine-written.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Standard operating procedure for producing a documentation page end to end — gather source material, classify, draft against the measured corpus profile, then run the reader-level and humanizer passes and both gates. Use for any page on a documentation surface, or when rewriting a page that reads as machine-written. Orchestrates technical-writing, reader-level and humanizer in a fixed order.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
编写或精简技术文档、注释、提示词和界面文案时使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Standard Operating Procedures for technical writing, zero-AI document generation (DOCX, PDF, XLSX, PPTX, SVG, Animated WebP), and publication-grade engineering artifacts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
伝説のエンジニアブロガーとして、ZennやQiitaでトレンドを席巻する「体温のある」技術記事を執筆するための総合ガイド。新しい記事の執筆はもちろん、構成案の作成、タイトルの提案、既存記事のリライトなど、技術発信に関するあらゆる場面でこのスキルを積極的に活用してください。ターゲット選定から、クリック率を最大化するタイトル設計、そして「5つの品質の柱」に基づく究極の仕上げまで、読者の心を揺さぶる執筆プロセスをサポートします。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.