원클릭으로 Manus에서 모든 스킬 실행

docs-tutorial

스타4

포크1

업데이트2026년 7월 3일 12:21

Write a tutorial for newcomers learning a topic in a ZIO library. Tutorials teach concepts step-by-step in a linear path for learning-oriented, not task-oriented, purposes. Use when writing comprehensive learning guides.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

zio

zio/zio-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Tutorial: Conceptual Overview

A tutorial is learning-oriented — it builds mental models for newcomers encountering a topic for the first time. It is not a reference page (exhaustive API) or how-to guide (task completion).

Core Properties

Targets newcomers: assume no prior knowledge of the topic
Linear path: no branching, no "alternatively" — one path, followed to completion
One concept per section: each section introduces exactly one new idea
Annotated code: every code block followed by line-by-line bullet explanation
Intermediate output: show results after meaningful steps so learner can verify progress
Warm tone: "Welcome", "Let's", "notice that", "try changing X to see Y"
Present tense: "we learn", "we see", "we observe"
Recap at end: "What You've Learned" mirrors the opening learning objectives

7-Section Structure

Introduction — who it's for, learning objectives, section outline
Background / Big Picture (optional) — conceptual framing, no code
Concept sections (3–6) — one concept each, code + annotation + output. When companion examples are requested, each section's code block stays an inline mdoc block (auto-rendered output is required here — mdoc:embed cannot show it), but the corresponding companion .scala file must copy that code verbatim, not re-derive it from the prose.
Putting It Together — complete runnable example combining all concepts. When companion examples are requested, do not paste this code inline — write it directly to CompleteExample.scala and embed it with mdoc:embed (output rendering isn't needed here, so embedding the file directly eliminates the duplication entirely).
Running the Examples — one ### per example: narrative, embedded source, observe note, run command. CompleteExample.scala is already embedded in "Putting It Together" — do not embed its source a second time here; give it narrative + observe note + run command only.
What You've Learned — bullet recap mirroring learning objectives
Where to Go Next — links to how-to guides and reference pages

Quality Gate

Before submitting, work through CHECKLIST.md — 38 items across Content Quality, Technical Accuracy, Companion Examples, Running the Examples, and Style and Integration.

이 저장소의 다른 Skills

같은 저장소

docs-how-to-guide

zio/zio-skills

Write a how-to guide for practitioners accomplishing a specific task with a ZIO library. Guides are goal-oriented and task-focused, not pedagogical. Use when writing step-by-step practical guides.

2026-07-034

docs-mdoc-conventions

zio/zio-skills

Reference for mdoc code block modifiers and Docusaurus admonitions used in ZIO documentation. Use when writing or reviewing documentation with Scala code examples.

2026-07-014

docs-module-ref

zio/zio-skills

Write reference documentation for a module containing multiple related data types. Use when documenting a cohesive domain model (e.g. http-model, resource-management) where types work together as a system.

2026-06-304

docs-data-type-ref

zio/zio-skills

Write reference documentation for a specific ZIO data type. Research the type, write comprehensive documentation with examples, verify mdoc compilation, and integrate into docs.

2026-06-294

docs-integrate

zio/zio-skills

Integration checklist for new ZIO docs pages. Handles sidebar wiring, index.md linking, and compilation gate (mdoc + Docusaurus build). Cross-referencing is handled separately by the integrate workflow (Phase 2).

2026-06-274

docs-reduce-redundancy

zio/zio-skills

Remove redundant content from documentation. Use when sections repeat information unnecessarily, type definitions appear multiple times, concepts are introduced more than once, or transition words clutter meaning. Reduces cognitive load through deduplication and strategic cross-referencing.

2026-06-274

name	docs-tutorial
description	Write a tutorial for newcomers learning a topic in a ZIO library. Tutorials teach concepts step-by-step in a linear path for learning-oriented, not task-oriented, purposes. Use when writing comprehensive learning guides.
allowed_tools	Read, Glob, Grep, Bash

Tutorial: Conceptual Overview

A tutorial is learning-oriented — it builds mental models for newcomers encountering a topic for the first time. It is not a reference page (exhaustive API) or how-to guide (task completion).

Core Properties

Targets newcomers: assume no prior knowledge of the topic
Linear path: no branching, no "alternatively" — one path, followed to completion
One concept per section: each section introduces exactly one new idea
Annotated code: every code block followed by line-by-line bullet explanation
Intermediate output: show results after meaningful steps so learner can verify progress
Warm tone: "Welcome", "Let's", "notice that", "try changing X to see Y"
Present tense: "we learn", "we see", "we observe"
Recap at end: "What You've Learned" mirrors the opening learning objectives

7-Section Structure

Introduction — who it's for, learning objectives, section outline
Background / Big Picture (optional) — conceptual framing, no code
Concept sections (3–6) — one concept each, code + annotation + output. When companion examples are requested, each section's code block stays an inline mdoc block (auto-rendered output is required here — mdoc:embed cannot show it), but the corresponding companion .scala file must copy that code verbatim, not re-derive it from the prose.
Putting It Together — complete runnable example combining all concepts. When companion examples are requested, do not paste this code inline — write it directly to CompleteExample.scala and embed it with mdoc:embed (output rendering isn't needed here, so embedding the file directly eliminates the duplication entirely).
Running the Examples — one ### per example: narrative, embedded source, observe note, run command. CompleteExample.scala is already embedded in "Putting It Together" — do not embed its source a second time here; give it narrative + observe note + run command only.
What You've Learned — bullet recap mirroring learning objectives
Where to Go Next — links to how-to guides and reference pages

Quality Gate

Before submitting, work through CHECKLIST.md — 38 items across Content Quality, Technical Accuracy, Companion Examples, Running the Examples, and Style and Integration.