Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Pick a real API/SDK/tool and write a getting-started TUTORIAL (a learning-oriented Diátaxis type — NOT a how-to or reference) that takes a developer from zero to a working result. Requirements: minimize TIME-TO-FIRST-SUCCESS (get to a runnable 'hello world' fast), include COMPLETE, RUNNABLE code (every snippet must actually work — broken code destroys trust), no marketing fluff, and an authentic developer voice. Then write a short reflection: who's the audience, what friction did you remove, and how you'd verify the code stays working over time.
Complete, runnable, accurate code that takes a beginner zero->success; it's a true tutorial (learning-oriented), not a reference dump.
Friction minimized; the developer reaches a first working result quickly; unnecessary steps removed.
Authentic, concise, no marketing fluff; respects the reader's intelligence.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A tutorial that actually works ## Goal Pick a real API/SDK/tool and write a getting-started TUTORIAL (a learning-oriented Diátaxis type — NOT a how-to or reference) that takes a developer from zero to a working result. Requirements: minimize TIME-TO-FIRST-SUCCESS (get to a runnable 'hello world' fast), include COMPLETE, RUNNABLE code (every snippet must actually work — broken code destroys trust), no marketing fluff, and an authentic developer voice. Then write a short reflection: who's the audience, what friction did you remove, and how you'd verify the code stays working over time. ## Acceptance criteria - [ ] Working tutorial: Complete, runnable, accurate code that takes a beginner zero->success; it's a true tutorial (learning-oriented), not a reference dump. - [ ] Time-to-first-success: Friction minimized; the developer reaches a first working result quickly; unnecessary steps removed. - [ ] Developer voice: Authentic, concise, no marketing fluff; respects the reader's intelligence. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.