'tutorials' 검색 결과

메모, 녹취록, 조사 자료로 블로그 글, 가이드, 뉴스레터 등 긴 글을 작성합니다. 기존 문체와 브랜드 방침에 맞춰 구성을 잡고 제공된 근거로 주장을 뒷받침합니다.

• 메모나 녹취록을 기사로 정리
• 브랜드 문체에 맞춘 글 작성
• 실용적인 가이드와 튜토리얼 집필

Find Claude Academy learning resources that closely match questions about using Claude, its features, or team adoption. It supplements direct answers with a small selection of relevant courses, tutorials, worked examples, or product learning hubs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find resources for getting started with Claude
• Learn how to use a specific Claude feature
• Choose learning materials for team adoption

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing documentation for an undocumented feature
• Creating tutorials and practical guides
• Preparing module references and explanations

Find explanations, tutorials, configuration guidance, and code examples in official documentation for Microsoft technologies. Choose documentation sources for Azure, .NET, VS Code, GitHub, Aspire, and Agent Framework based on where the relevant material is published.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find official explanations and setup instructions
• Look up code examples for a specific language
• Research VS Code settings or extension APIs

Edit videos through conversation, from transcription and take selection to cuts, color adjustments, animated overlays, and subtitles. Confirm an editing plan, review a checked preview, and refine the result before the final render.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Select the best takes for a presentation video
• Trim tutorials and add subtitles
• Shape interviews or travel footage

Create and refine Jupyter notebooks for experiments, exploratory analysis, or tutorials. Bundled templates help organize runnable code and short explanations into clear steps, while validation guidance supports notebooks that others can read and rerun.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting a notebook for an experiment
• Turning scripts or notes into a structured notebook
• Creating a step-by-step teaching notebook

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add explanations to public functions and classes
• Create API specifications and reference pages
• Build a documentation site

Creates step-by-step tutorials and educational content from code. Transforms complex concepts into progressive learning experiences with hands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials, or concept explanations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Search all Japanese NLP resources (libraries, models, datasets, tutorials, dictionaries, Hugging Face). Accepts keywords or natural language questions in any language. Use whenever the user asks which Japanese NLP resource to use, or wants to find one: tokenizers / morphological analyzers, BERT or LLM models, embeddings, NER, text classification, datasets / corpora, dictionaries, tutorials, or Hugging Face models. Trigger phrases include '日本語の形態素解析ライブラリ', 'おすすめの日本語tokenizer', '日本語BERTモデル', '日本語の感情分析データセット', '日本語LLM 一覧', 'which Japanese embedding model', 'Japanese NER library'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diátaxis-driven documentation for AI coding agents: write, improve, or audit tutorials, how-tos, reference, explanation, and developer docs (README, CONTRIBUTING, ADRs). Detects the docs stack; gates on the outline before writing prose; verifies every claim against the code before it ships. Triggers on "absolute docs", "write docs", "write a tutorial", "write a README", "document this", "improve this doc", "audit our docs".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive blog writing skill that handles technical blog posts, personal voice writing, brain dump transformation, and category-aware AEO-optimized content. Use when: (1) writing, editing, or proofreading a blog article or post, (2) transforming unstructured brain dumps into polished posts, (3) writing in specific personal voices (Jarad, Nick Nisi), (4) creating category-aware technology/company/product posts, (5) building tutorials, deep dives, postmortems, benchmarks, or architecture posts, (6) writing engineering blogs, dev blogs, programming blogs, coding tutorials, or documentation posts. Triggers: blog post, blog writing, technical blog, dev tutorial, brain dump, article, content writing, developer article, engineering blog, programming blog, coding tutorial, documentation post, technical writing, blog editing, proofreading, developer content

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Restructure and enrich the tdmcp documentation site for artists — categorized/collapsible sidebar (EN+PT), interactive goal-based guide home, new step-by-step tutorials, copy-prompt/level-badge components. Use whenever the user asks to make the docs more interactive, easier to navigate, better organized, add categories/subcategories, add tutorials, improve docs UX/IA, or for follow-ups: re-run, continue, fix QA findings, add one more tutorial, re-organize a section, or update the docs structure. NOT for syncing docs with a release (tdmcp-docs-roadmap-update) or cookbook entries (tdmcp-cookbook-examples).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to create step-by-step technical tutorials, quickstarts, or code walkthroughs. Trigger phrases include "tutorial," "quickstart," "getting started guide," "walkthrough," "step by step," "how to guide," "hands-on guide," or "code tutorial."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Workflow Phase 10 — orchestrator for documentation work. Surveys the diff, routes any page on a documentation surface through `technical-writer`, standalone technical reference through the `documentation` skill, tutorials through `technical-tutorials`, and all other prose body work (inline docs, README updates, user-facing copy) through the `prose` skill (which mandates `humanizer` and conditionally `copywriting`). Verifies completeness and marks phase done.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft or revise English prose for any brief — documentation body, intake problem statements, spec context, RCA summaries, marketing copy, README sections, PR descriptions. Mandatorily invokes `Skill(humanizer)` as the final pass on every draft. Conditionally invokes `copywriting` for persuasive register, `documentation` for reference docs, `technical-tutorials` for tutorials. Used when any phase needs human-readable prose written or rewritten. Composition only — research and register-picking happen in the caller's context.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Author tutorial-style documentation for the gatOS Astro/Starlight docs site (under site/) — the progressive `guides/` series that teaches writing flight-computer / autopilot programs against the gatOS /sim filesystem and its HTTP /v1 mirror. Use this when asked to write, add, or revise a gatOS tutorial or guide, plan the tutorial curriculum, or turn a /sim feature into a lesson. Covers the house style, Starlight/MDX mechanics, the dual-transport (/sim file + HTTP) presentation convention, the reusable code-snippet library, and the beginner→advanced tutorial ladder. Pairs with the `gatos` skill (how the sim works) and docs/TUTORIAL_DATA_REFERENCE.md (the data tutorials are built from).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to create, scaffold, or edit Jupyter notebooks (`.ipynb`) for experiments, explorations, or tutorials; prefer the bundled templates and helper script for reproducible notebook structure and safer editing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates step-by-step tutorials and educational content from code. Transforms complex concepts into progressive learning experiences with hands-on examples. Use PROACTIVELY for onboarding guides, feature tutorials, or concept explanations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Edit existing footage into vlogs, tutorials, demos, or short social clips. This skill guides segment selection, cutting, overlays, audio additions, and platform-specific framing, with final pacing and polish handled in a traditional video editor.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn long recordings into short highlight clips
• Build a vlog from raw camera footage
• Add text overlays and narration to product demos

웹 앱의 조작 과정을 커서와 자막이 포함된 WebM 영상으로 기록합니다. 화면 조사와 리허설을 거쳐 입력, 클릭, 스크롤을 보기 편한 속도로 촬영합니다.

• 새 기능의 사용 과정을 영상으로 소개
• 처음 사용하는 사람을 위한 안내 영상 제작
• 문서에 조작 영상 추가

제공된 글 예시나 브랜드 문체에 맞춰 기사, 가이드, 뉴스레터를 작성합니다. 메모와 조사 자료를 글로 정리하고 기존 원고의 구성과 근거도 검토합니다.

• 메모나 녹취록을 기사로 정리
• 브랜드 문체로 가이드 작성
• 기존 원고의 구성과 근거 검토