'tutorials' 검색 결과

SEO-friendly article writing, audit, and humanization workflow for Markdown content. Use when creating, outlining, editing, auditing, rewriting, or quality-checking blog posts, tutorials, comparisons, listicles, explainers, FAQ sections, excerpts, SEO titles, meta descriptions, tags, or Google-friendly content briefs that need clear topics, natural keyword use, on-page SEO review, reader-friendly prose, and iterative optimization.

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

Generate Marp-compatible slide decks from structured JSON schema. Converts context into presentations for tech talks, sprint demos, and tutorials.

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

Write, restructure, classify, and review documentation with the Diataxis framework. Use when the user asks to create, improve, audit, or reorganize documentation of any kind: knowledge bases, help centers, onboarding guides, process docs, manuals, runbooks, product or API docs, tutorials, how-to guides, references, explanations. Also use when the user mentions Diataxis, docs taxonomy, or documentation architecture, or asks why a document feels confusing. Also use for Simplified Technical English (ASD-STE100) or controlled-language rewrites of English technical docs. Not for marketing, legal, sales, press, or fiction writing unless the user wants a Diataxis-style analysis.

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

Classify, write, and audit documentation per Diátaxis (diataxis.fr) — the four-quadrant method (tutorials · how-to guides · reference · explanation). Encodes the compass as a decision procedure, each quadrant's contract as hard rules, and an executable mixed-mode audit. Project-agnostic; the per-repo doc-location mapping lives in a repo rule of the project's own (kolu: `.apm/instructions/diataxis.instructions.md`). Use when writing any user-facing doc, structuring a docs site, or auditing existing docs for mixed modes.

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

Community knowledge from bivector.net - GA tutorials, discussions, and best practices

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

Use when the primary outcome is authoring, rewriting, summarizing, or validating user-facing documentation without implementation comparison or required source attribution, including READMEs, tutorials, API docs, GitLab Markdown, source-faithful summaries, and audience-specific prose.

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

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

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

Generates SEO and AEO optimized blog posts from source content. Supports feature announcements, product launches, thought leadership, cookbooks/tutorials, report conversions, and news analysis. Outputs complete posts with TLDR, FAQ, schema markup, and internal linking recommendations.

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

Use when you want an SEO and AEO optimized blog post from source material, including feature announcements, launches, tutorials, or thought leadership.

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

Scout ONE external surface of the TouchDesigner community for what's HYPED in 2025-2026 that could become a tdmcp tool. Use when a td-trend-scout sub-agent is assigned a surface (community-showcase, tutorials, generative-ai, hardware-interactive, or vfx-aesthetics) during the tdmcp-hype-scout harness — produces `_workspace/hype-scout/01_scout_<surface>.md` with cited trend candidates ranked by hype intensity, recency, and build-ease in tdmcp.

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

Scout the TouchDesigner community for what's HYPED right now — community showcases, recent tutorials, generative-AI bridges, hardware interaction trends, visual-aesthetic trends of 2025-2026 — then propose tdmcp tools that ride those trends AND are easy to build. Use whenever the user wants to brainstorm new feature ideas based on what's trending in TouchDesigner, asks for 'hype' or 'trending' features, asks 'what are people doing in TD right now / what's hot / what's hype', wants tools inspired by community trends, asks to scout TD trends/aesthetics/integrations, or says things like 'ideias hype', 'novas ideias', 'o que está em alta', 'criar ferramentas para o que está bombando', 'tendências do TouchDesigner'. Also for follow-ups: refresh, rescout one surface, re-rank under another profile, deepen a trend, or filter for buildable-easy items. This is an EXTERNAL trend ideation harness — complementary to tdmcp-feature-discovery (which is INTERNAL gap analysis). It produces `_workspace/hype-scout/HYPE_TOOL_BACKLOG.md` ranked by Hype × Build-Ease; it does NOT build. Once a feature is chosen from the backlog, hand it to tdmcp-pipeline.

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

Generates comprehensive documentation from code, APIs, and specifications. Creates API documentation, developer guides, architecture docs, and user manuals with examples and tutorials.

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

Master orchestrator for B2B SaaS content creation and the editorial production system behind it. Use this skill to produce blog articles, whitepapers, case studies, video scripts, newsletters and ghostwritten thought leadership, to develop content strategy, and to run the publishing line itself — content briefs, editorial calendars and production capacity, review and approval workflow, subject-matter-expert access, the style guide, an AI-drafting policy, and a content inventory with owners. Also triggers on: blog, article, copywriting, edit this copy, improve this landing page copy, fix this headline, tighten this paragraph, rewrite without losing our voice, case study, whitepaper, newsletter, video script, ghostwriting, content calendar, editorial, thought leadership, content strategy, content brief, content operations, content ops, editorial workflow, managing editor, who reviews this, our content pipeline is stuck, content is stuck in review, content audit, content inventory, content governance, style guide, house style, SME interview, expert interview, freelance writers, AI content policy, how much content can we actually produce. Also owns the customer academy and customer education: online courses, onboarding curriculum, tutorials, certification programs, digital credentials and badges, exam and pass-mark design, course freshness when the product UI changes, and whether the academy should sit behind a login. Triggers on: customer academy, customer education, online course, course library, learning path, curriculum, tutorial, certification program, certified users, digital badge, Open Badges, recertification, exam, pass mark, LMS, Skilljar, our tutorial shows the old UI, our course is out of date, should the academy be gated, do certified customers renew better.

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

Research-grounded workflow for designing, reviewing, and improving video game user interfaces, including HUDs, menus, navigation, focus states, onboarding/tutorials, objective tracking, input prompts, readability, accessibility, and destructive-action flows. Use when asked how to make good game UI, critique a game UI or HUD, propose UI/UX guidelines, design menu or gameplay interfaces, compare HUD vs diegetic/spatial presentation, create a UI design brief, or run a usability/accessibility review for PC, console, mobile, or VR games.

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

Audit, classify, validate, and scaffold documentation using the Diataxis framework (Tutorials, How-to guides, Reference, Explanation). Use when user mentions "diataxis", "documentation framework", "quadrant", "doc audit", "doc coverage", "collapsed document", "tutorial vs how-to", "quadrant purity", "documentation types", or wants to classify docs by type.

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

Technical documentation expert for clear, concise, user-friendly documentation and tutorials

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

Judges whether a user's input suits the Vibe Creating style of video-prompt writing, and when it does, distills single-scene prompts, multi-shot descriptions, emotional imagery, or mixed input into prompts that are easier for a video model to generate from — while preserving any user-specified dialogue, voiceover, music, sound effects, and other hard constraints. Use when a user wants to turn an idea, story, feeling, or rough/over-specified prompt into a strong text-to-video prompt (Seedance, Sora, Kling, Veo, Runway, etc.), or asks to "rewrite", "improve", "clean up", or "vibe-ify" a video prompt. Do NOT use for long narrative films that need precise word-for-word dialogue sync, industrial shot lists meant to be executed verbatim, or functional/UI demos and step-by-step tutorials.

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

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.

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

Write, rewrite, review, and organize developer-facing documentation for web software projects. Use when creating or improving README files, docs homepages, quickstarts, tutorials, how-to guides, API/reference pages, conceptual explanations, migration guides, or troubleshooting content for frontend, backend, full-stack, SDK, API, or framework-based web products. This skill applies strong information architecture, task-first page structure, clear voice, runnable examples, version and prerequisite hygiene, accessibility rules, and docs-as-code maintenance habits. Do not use it for marketing copy, legal text, or non-technical customer-support articles.

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

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

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

Native video analysis using Google Gemini API. Upload and analyze video files — describe scenes, extract text/UI, answer questions about content, transcribe speech, identify objects and actions. Use when: (1) User sends a video file and wants it analyzed, (2) Video summarization or description needed, (3) Extracting text, UI elements, or information from screen recordings, (4) Answering questions about video content, (5) Comparing multiple videos, (6) Analyzing tutorials, demos, or walkthroughs.

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

Transform learning content (like YouTube transcripts, articles, tutorials) into actionable implementation plans using the Ship-Learn-Next framework. Use when user wants to turn advice, lessons, or educational content into concrete action steps, reps, or a learning quest.

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

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

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

Reference for Astro — the core web framework the gatOS docs site (under site/) is built on. Use this when authoring or editing pages in site/, working with .astro/.md/.mdx files, content collections, the astro.config.mjs, or component/JSX-in-Markdown mechanics. Covers Astro component anatomy, using components in MDX, content collections, frontmatter, imports, expressions, and the build/dev commands — enough to work the site without leaving the repo. Pair with the `starlight` skill (the docs theme + its components) and the `tutorials` skill (the gatOS house style).

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