[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A8TXF2ZX86TWW484CZR2C8":3,"skill-same:01M7A8TXF2ZX86TWW484CZR2C8":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7A8TXF2ZX86TWW484CZR2C8","technical-tutorials",null,"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.\"","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Ftechnical-tutorials\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: technical-tutorials\ndescription: 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.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Ftechnical-tutorials\nsource_repo: jonathimer\u002Fdevmarketing-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Technical Tutorials\n## When to Use\n\nUse this skill when you need 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.\".\n\n\nThis skill helps you create step-by-step tutorials that actually work. Covers prerequisite handling, progressive complexity, troubleshooting sections, and creating those satisfying \"it works!\" moments.\n\n---\n\n## Before You Start\n\n**Load your audience context first.** Read `.agents\u002Fdeveloper-audience-context.md` to understand:\n\n- Developer skill level (beginner, intermediate, senior)\n- Tech stack familiarity (what can you assume they know?)\n- Environment (macOS, Linux, Windows, cloud)\n- Why they're learning (job, side project, curiosity)\n\nIf the context file doesn't exist, run the `developer-audience-context` skill first.\n\n---\n\n## Tutorial Types\n\n| Type | Length | Purpose | Example |\n|------|--------|---------|---------|\n| **Quickstart** | 5-10 min | First success ASAP | \"Make your first API call\" |\n| **Tutorial** | 20-45 min | Learn a concept deeply | \"Build a REST API with Node.js\" |\n| **Workshop** | 1-3 hours | Comprehensive project | \"Build a full-stack app\" |\n| **Code walkthrough** | Varies | Explain existing code | \"Understanding our SDK architecture\" |\n\n---\n\n## The Tutorial Structure\n\n### Anatomy of a Great Tutorial\n\n```\n1. Title & Meta\n   - What you'll build\n   - Time estimate\n   - Prerequisites\n\n2. Overview\n   - What you'll learn\n   - Final result preview\n\n3. Prerequisites Check\n   - Environment setup\n   - Verification commands\n\n4. The Build (Progressive Steps)\n   - Step 1: Simplest foundation\n   - Step 2: Add one concept\n   - Step 3: Add complexity\n   - [Checkpoint: \"It works!\" moment]\n   - Step 4: Continue building\n   - ...\n   - [Final checkpoint]\n\n5. What You Built\n   - Recap\n   - Complete code\n\n6. Troubleshooting\n   - Common errors\n   - Debugging tips\n\n7. Next Steps\n   - Where to go from here\n   - Related tutorials\n```\n\n---\n\n## Prerequisites Handling\n\n### The Prerequisites Section\n\nBe explicit. Don't make developers guess what they need.\n\n```markdown\n## Prerequisites\n\nBefore starting, make sure you have:\n\n| Requirement | Version | Check Command |\n|-------------|---------|---------------|\n| Node.js | 18+ | `node --version` |\n| npm | 9+ | `npm --version` |\n| Git | Any | `git --version` |\n\nYou should also be comfortable with:\n- Basic JavaScript (variables, functions, async\u002Fawait)\n- Command line basics (cd, mkdir, running commands)\n- REST API concepts (HTTP methods, JSON)\n\n**New to any of these?** Check out [link to prerequisite tutorial].\n```\n\n### Environment Setup Section\n\nMake setup foolproof:\n\n```markdown\n## Setting Up Your Environment\n\n### 1. Create Project Directory\n\n\\`\\`\\`bash\nmkdir my-awesome-project\ncd my-awesome-project\n\\`\\`\\`\n\n### 2. Initialize the Project\n\n\\`\\`\\`bash\nnpm init -y\n\\`\\`\\`\n\nYou should see output like:\n\\`\\`\\`json\n{\n  \"name\": \"my-awesome-project\",\n  \"version\": \"1.0.0\",\n  ...\n}\n\\`\\`\\`\n\n### 3. Install Dependencies\n\n\\`\\`\\`bash\nnpm install express dotenv\n\\`\\`\\`\n\n### 4. Verify Installation\n\n\\`\\`\\`bash\nnode -e \"require('express'); console.log('Express installed!')\"\n\\`\\`\\`\n\nExpected output: `Express installed!`\n```\n\n---\n\n## Progressive Complexity\n\n### The Layer Cake Approach\n\nBuild up in understandable layers:\n\n| Layer | What It Does | Example |\n|-------|--------------|---------|\n| **1. Skeleton** | Minimum viable code that runs | \"Hello World\" server |\n| **2. Core feature** | Primary functionality | Add one API endpoint |\n| **3. Real data** | Replace hardcoded values | Connect to database |\n| **4. Error handling** | Production-ready patterns | Add try\u002Fcatch, validation |\n| **5. Polish** | Nice-to-haves | Logging, config, tests |\n\n### Show Progress, Not Perfection\n\n**Wrong approach** (overwhelming):\n```javascript\n\u002F\u002F Here's the complete file with everything\nconst express = require('express');\nconst { Pool } = require('pg');\nconst helmet = require('helmet');\nconst rateLimit = require('express-rate-limit');\nconst winston = require('winston');\n\u002F\u002F ... 200 more lines\n```\n\n**Right approach** (progressive):\n\n**Step 1: Basic server**\n```javascript\nconst express = require('express');\nconst app = express();\n\napp.get('\u002F', (req, res) => {\n  res.send('Hello World!');\n});\n\napp.listen(3000, () => {\n  console.log('Server running on http:\u002F\u002Flocalhost:3000');\n});\n```\n\n**Step 2: Add your first route**\n```javascript\n\u002F\u002F Add this below your existing route\napp.get('\u002Fapi\u002Fusers', (req, res) => {\n  res.json([{ id: 1, name: 'Jane' }]);\n});\n```\n\n---\n\n## Copy-Paste Friendly Code\n\n### The Copy-Paste Checklist\n\nEvery code block must pass these tests:\n\n| Test | How to Verify |\n|------|---------------|\n| **Runs standalone** | Copy into new file, execute, it works |\n| **Imports included** | All `require`\u002F`import` statements present |\n| **No undefined variables** | No references to code from other steps without showing it |\n| **Environment agnostic** | Works on Mac\u002FLinux\u002FWindows |\n| **Comments explain why** | Not what (code shows what), but why |\n\n### Code Block Patterns\n\n**File context is critical:**\n\n```javascript\n\u002F\u002F server.js - Add this to your existing file\nconst rateLimit = require('express-rate-limit');\n\n\u002F\u002F Add this BEFORE your routes\nconst limiter = rateLimit({\n  windowMs: 15 * 60 * 1000, \u002F\u002F 15 minutes\n  max: 100 \u002F\u002F limit each IP to 100 requests per window\n});\n\napp.use(limiter);\n```\n\n**Show file structure:**\n\n```\nmy-project\u002F\n├── src\u002F\n│   ├── index.js      ← You're editing this\n│   ├── routes\u002F\n│   │   └── users.js\n│   └── db\u002F\n│       └── connection.js\n├── package.json\n└── .env\n```\n\n**Highlight changes in context:**\n\n```javascript\n\u002F\u002F src\u002Findex.js\nconst express = require('express');\nconst app = express();\n\n\u002F\u002F ✅ ADD THIS: Import your new route\nconst userRoutes = require('.\u002Froutes\u002Fusers');\n\n\u002F\u002F ✅ ADD THIS: Use the route\napp.use('\u002Fapi\u002Fusers', userRoutes);\n\napp.listen(3000);\n```\n\n---\n\n## \"It Works!\" Moments\n\n### Checkpoints Create Motivation\n\nEvery 3-5 steps, give developers a win:\n\n```markdown\n## Checkpoint: Test Your API\n\nLet's make sure everything works before continuing.\n\n**Start your server:**\n\\`\\`\\`bash\nnode server.js\n\\`\\`\\`\n\n**In a new terminal, test the endpoint:**\n\\`\\`\\`bash\ncurl http:\u002F\u002Flocalhost:3000\u002Fapi\u002Fusers\n\\`\\`\\`\n\n**You should see:**\n\\`\\`\\`json\n[{\"id\": 1, \"name\": \"Jane\"}]\n\\`\\`\\`\n\n🎉 **It works!** Your API is returning data.\n\nIf you don't see this output, check the [Troubleshooting](#troubleshooting) section.\n```\n\n### Visual Confirmation\n\nWhen possible, show what success looks like:\n\n| Output Type | How to Show |\n|-------------|-------------|\n| **Terminal output** | Code block with expected text |\n| **Browser result** | Screenshot or description |\n| **API response** | Formatted JSON |\n| **Logs** | Code block with log output |\n\n---\n\n## Troubleshooting Sections\n\n### Common Error Template\n\n```markdown\n## Troubleshooting\n\n### \"Error: Cannot find module 'express'\"\n\n**Cause:** Dependencies weren't installed.\n\n**Fix:**\n\\`\\`\\`bash\nnpm install\n\\`\\`\\`\n\n---\n\n### \"EADDRINUSE: address already in use :::3000\"\n\n**Cause:** Another process is using port 3000.\n\n**Fix (macOS\u002FLinux):**\n\\`\\`\\`bash\n# Find the process\nlsof -i :3000\n\n# Kill it (replace PID with actual number)\nkill -9 PID\n\\`\\`\\`\n\n**Or use a different port:**\n\\`\\`\\`javascript\napp.listen(process.env.PORT || 3001);\n\\`\\`\\`\n\n---\n\n### \"SyntaxError: Unexpected token\"\n\n**Cause:** Likely a typo or missing bracket.\n\n**Debug steps:**\n1. Check the line number in the error\n2. Look for missing `,`, `}`, or `)`\n3. Verify all strings are closed with matching quotes\n```\n\n### Proactive Error Prevention\n\nAdd warnings before common pitfalls:\n\n```markdown\n⚠️ **Windows users:** Use `set` instead of `export`:\n\\`\\`\\`bash\n# macOS\u002FLinux\nexport API_KEY=your_key\n\n# Windows Command Prompt\nset API_KEY=your_key\n\n# Windows PowerShell\n$env:API_KEY = Read-Host -AsSecureString \"API key\"\n\\`\\`\\`\n```\n\n---\n\n## Tutorial Templates\n\n### Quickstart Template (5-10 minutes)\n\n```markdown\n# [Product] Quickstart: [What You'll Do] in 5 Minutes\n\nGet [specific outcome] in under 5 minutes.\n\n## Prerequisites\n\n- [Requirement 1]\n- [Requirement 2]\n\n## Step 1: Install\n\n\\`\\`\\`bash\nnpm install your-package\n\\`\\`\\`\n\n## Step 2: Configure\n\nCreate a `.env` file:\n\\`\\`\\`\nAPI_KEY=your_key_here\n\\`\\`\\`\n\n## Step 3: Write Code\n\nCreate `index.js`:\n\\`\\`\\`javascript\n\u002F\u002F Complete, working code\n\\`\\`\\`\n\n## Step 4: Run It\n\n\\`\\`\\`bash\nnode index.js\n\\`\\`\\`\n\nExpected output:\n\\`\\`\\`\n[Output here]\n\\`\\`\\`\n\n## 🎉 You Did It!\n\nYou just [accomplished thing].\n\n**Next steps:**\n- [Link to full tutorial]\n- [Link to API docs]\n- [Link to examples repo]\n```\n\n### Full Tutorial Template (20-45 minutes)\n\n```markdown\n# Build a [Thing] with [Technology]\n\nLearn how to [outcome] by building [specific project].\n\n| | |\n|---|---|\n| **Time** | 30 minutes |\n| **Level** | Intermediate |\n| **Prerequisites** | Node.js 18+, basic JavaScript |\n\n## What You'll Build\n\n[Screenshot or diagram of final result]\n\nBy the end, you'll have:\n- ✅ [Capability 1]\n- ✅ [Capability 2]\n- ✅ [Capability 3]\n\n## Prerequisites\n\n### Required Software\n\n| Tool | Version | Verify |\n|------|---------|--------|\n| Node.js | 18+ | `node -v` |\n\n### Required Knowledge\n\n- [Concept 1] — [link to learn]\n- [Concept 2] — [link to learn]\n\n## Step 1: Project Setup\n\n[Setup instructions with verification]\n\n**Checkpoint:** You should see `[expected output]`.\n\n## Step 2: [First Feature]\n\n[Instructions]\n\n**Checkpoint:** Test with `[command]`.\n\n## Step 3: [Second Feature]\n\n[Instructions]\n\n## Step 4: [Third Feature]\n\n[Instructions]\n\n**Checkpoint:** Your app should now [do thing].\n\n## Complete Code\n\nHere's everything together:\n\n\\`\\`\\`javascript\n\u002F\u002F Full final code\n\\`\\`\\`\n\n## Troubleshooting\n\n### [Common Error 1]\n[Solution]\n\n### [Common Error 2]\n[Solution]\n\n## What You Learned\n\n- [Key concept 1]\n- [Key concept 2]\n- [Key concept 3]\n\n## Next Steps\n\n- **Go deeper:** [Link to advanced tutorial]\n- **Explore:** [Link to related feature]\n- **Get help:** [Link to Discord\u002Fcommunity]\n```\n\n---\n\n## Quality Checklist\n\nBefore publishing, verify:\n\n### Code Quality\n- [ ] Every code block runs without modification\n- [ ] All imports\u002Frequires are included\n- [ ] Expected output is shown\n- [ ] Error handling is included\n- [ ] Environment variables use `.env` pattern\n\n### Structure Quality\n- [ ] Prerequisites are explicit\n- [ ] Time estimate is accurate (test it!)\n- [ ] Checkpoints every 3-5 steps\n- [ ] Final complete code is provided\n- [ ] Troubleshooting covers likely errors\n\n### Accessibility\n- [ ] Works on Mac, Linux, AND Windows\n- [ ] Commands work in bash\u002Fzsh\u002FPowerShell\n- [ ] File paths use correct separators\n- [ ] No assumptions about installed tools\n\n---\n\n## Tools\n\n| Tool | Use Case |\n|------|----------|\n| **[Octolens](https:\u002F\u002Foctolens.com)** | Find common questions and errors developers encounter. Monitor Stack Overflow and GitHub issues for troubleshooting content. |\n| **Replit\u002FCodeSandbox** | Embed runnable examples |\n| **Carbon\u002FRay.so** | Beautiful code screenshots |\n| **Excalidraw** | Architecture diagrams |\n| **Terminalizer** | Record terminal sessions |\n| **Loom** | Quick video supplements |\n\n---\n\n## Related Skills\n\n- `developer-audience-context` — Understand skill level and environment\n- `devrel-content` — General technical writing principles\n- `developer-onboarding` — Optimize time to first success\n- `developer-seo` — Get tutorials found via search\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Technical Tutorials\n## When to Use\n\nUse this skill when you need 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.\".\n\n\nThis skill helps you create step-by-step tutorials that actually work. Covers prerequisite handling, progressive complexity, troubleshooting sections, and creating those satisfying \"it works!\" moments.\n\n---\n\n## Before You Start\n\n**Load your audience context first.** Read `.agents\u002Fdeveloper-audience-context.md` to understand:\n\n- Developer skill level (beginner, intermediate, senior)\n- Tech stack familiarity (what can you assume they know?)\n- Environment (macOS, Linux, Windows, cloud)\n- Why they're learning (job, side project, curiosity)\n\nIf the context file doesn't exist, run the `developer-audience-context` skill first.\n\n---\n\n## Tutorial Types\n\n| Type | Length | Purpose | Example |\n|------|--------|---------|---------|\n| **Quickstart** | 5-10 min | First success ASAP | \"Make your first API call\" |\n| **Tutorial** | 20-45 min | Learn a concept deeply | \"Build a REST API with Node.js\" |\n| **Workshop** | 1-3 hours | Comprehensive project | \"Build a full-stack app\" |\n| **Code walkthrough** | Varies | Explain existing code | \"Understanding our SDK architecture\" |\n\n---\n\n## The Tutorial Structure\n\n### Anatomy of a Great Tutorial\n\n```\n1. Title & Meta\n   - What you'll build\n   - Time estimate\n   - Prerequisites\n\n2. Overview\n   - What you'll learn\n   - Final result preview\n\n3. Prerequisites Check\n   - Environment setup\n   - Verification commands\n\n4. The Build (Progressive Steps)\n   - Step 1: Simplest foundation\n   - Step 2: Add one concept\n   - Step 3: Add complexity\n   - [Checkpoint: \"It works!\" moment]\n   - Step 4: Continue building\n   - ...\n   - [Final checkpoint]\n\n5. What You Built\n   - Recap\n   - Complete code\n\n6. Troubleshooting\n   - Common errors\n   - Debugging tips\n\n7. Next Steps\n   - Where to go from here\n   - Related tutorials\n```\n\n---\n\n## Prerequisites Handling\n\n### The Prerequisites Section\n\nBe explicit. Don't make developers guess what they need.\n\n```markdown\n## Prerequisites\n\nBefore starting, make sure you have:\n\n| Requirement | Version | Check Command |\n|-------------|---------|---------------|\n| Node.js | 18+ | `node --version` |\n| npm | 9+ | `npm --version` |\n| Git | Any | `git --version` |\n\nYou should also be comfortable with:\n- Basic JavaScript (variables, functions, async\u002Fawait)\n- Command line basics (cd, mkdir, running commands)\n- REST API concepts (HTTP methods, JSON)\n\n**New to any of these?** Check out [link to prerequisite tutorial].\n```\n\n### Environment Setup Section\n\nMake setup foolproof:\n\n```markdown\n## Setting Up Your Environment\n\n### 1. Create Project Directory\n\n\\`\\`\\`bash\nmkdir my-awesome-project\ncd my-awesome-project\n\\`\\`\\`\n\n### 2. Initialize the Project\n\n\\`\\`\\`bash\nnpm init -y\n\\`\\`\\`\n\nYou should see output like:\n\\`\\`\\`json\n{\n  \"name\": \"my-awesome-project\",\n  \"version\": \"1.0.0\",\n  ...\n}\n\\`\\`\\`\n\n### 3. Install Dependencies\n\n\\`\\`\\`bash\nnpm install express dotenv\n\\`\\`\\`\n\n### 4. Verify Installation\n\n\\`\\`\\`bash\nnode -e \"require('express'); console.log('Express installed!')\"\n\\`\\`\\`\n\nExpected output: `Express installed!`\n```\n\n---\n\n## Progressive Complexity\n\n### The Layer Cake Approach\n\nBuild up in understandable layers:\n\n| Layer | What It Does | Example |\n|-------|--------------|---------|\n| **1. Skeleton** | Minimum viable code that runs | \"Hello World\" server |\n| **2. Core feature** | Primary functionality | Add one API endpoint |\n| **3. Real data** | Replace hardcoded values | Connect to database |\n| **4. Error handling** | Production-ready patterns | Add try\u002Fcatch, validation |\n| **5. Polish** | Nice-to-haves | Logging, config, tests |\n\n### Show Progress, Not Perfection\n\n**Wrong approach** (overwhelming):\n```javascript\n\u002F\u002F Here's the complete file with everything\nconst express = require('express');\nconst { Pool } = require('pg');\nconst helmet = require('helmet');\nconst rateLimit = require('express-rate-limit');\nconst winston = require('winston');\n\u002F\u002F ... 200 more lines\n```\n\n**Right approach** (progressive):\n\n**Step 1: Basic server**\n```javascript\nconst express = require('express');\nconst app = express();\n\napp.get('\u002F', (req, res) => {\n  res.send('Hello World!');\n});\n\napp.listen(3000, () => {\n  console.log('Server running on http:\u002F\u002Flocalhost:3000');\n});\n```\n\n**Step 2: Add your first route**\n```javascript\n\u002F\u002F Add this below your existing route\napp.get('\u002Fapi\u002Fusers', (req, res) => {\n  res.json([{ id: 1, name: 'Jane' }]);\n});\n```\n\n---\n\n## Copy-Paste Friendly Code\n\n### The Copy-Paste Checklist\n\nEvery code block must pass these tests:\n\n| Test | How to Verify |\n|------|---------------|\n| **Runs standalone** | Copy into new file, execute, it works |\n| **Imports included** | All `require`\u002F`import` statements present |\n| **No undefined variables** | No references to code from other steps without showing it |\n| **Environment agnostic** | Works on Mac\u002FLinux\u002FWindows |\n| **Comments explain why** | Not what (code shows what), but why |\n\n### Code Block Patterns\n\n**File context is critical:**\n\n```javascript\n\u002F\u002F server.js - Add this to your existing file\nconst rateLimit = require('express-rate-limit');\n\n\u002F\u002F Add this BEFORE your routes\nconst limiter = rateLimit({\n  windowMs: 15 * 60 * 1000, \u002F\u002F 15 minutes\n  max: 100 \u002F\u002F limit each IP to 100 requests per window\n});\n\napp.use(limiter);\n```\n\n**Show file structure:**\n\n```\nmy-project\u002F\n├── src\u002F\n│   ├── index.js      ← You're editing this\n│   ├── routes\u002F\n│   │   └── users.js\n│   └── db\u002F\n│       └── connection.js\n├── package.json\n└── .env\n```\n\n**Highlight changes in context:**\n\n```javascript\n\u002F\u002F src\u002Findex.js\nconst express = require('express');\nconst app = express();\n\n\u002F\u002F ✅ ADD THIS: Import your new route\nconst userRoutes = require('.\u002Froutes\u002Fusers');\n\n\u002F\u002F ✅ ADD THIS: Use the route\napp.use('\u002Fapi\u002Fusers', userRoutes);\n\napp.listen(3000);\n```\n\n---\n\n## \"It Works!\" Moments\n\n### Checkpoints Create Motivation\n\nEvery 3-5 steps, give developers a win:\n\n```markdown\n## Checkpoint: Test Your API\n\nLet's make sure everything works before continuing.\n\n**Start your server:**\n\\`\\`\\`bash\nnode server.js\n\\`\\`\\`\n\n**In a new terminal, test the endpoint:**\n\\`\\`\\`bash\ncurl http:\u002F\u002Flocalhost:3000\u002Fapi\u002Fusers\n\\`\\`\\`\n\n**You should see:**\n\\`\\`\\`json\n[{\"id\": 1, \"name\": \"Jane\"}]\n\\`\\`\\`\n\n🎉 **It works!** Your API is returning data.\n\nIf you don't see this output, check the [Troubleshooting](#troubleshooting) section.\n```\n\n### Visual Confirmation\n\nWhen possible, show what success looks like:\n\n| Output Type | How to Show |\n|-------------|-------------|\n| **Terminal output** | Code block with expected text |\n| **Browser result** | Screenshot or description |\n| **API response** | Formatted JSON |\n| **Logs** | Code block with log output |\n\n---\n\n## Troubleshooting Sections\n\n### Common Error Template\n\n```markdown\n## Troubleshooting\n\n### \"Error: Cannot find module 'express'\"\n\n**Cause:** Dependencies weren't installed.\n\n**Fix:**\n\\`\\`\\`bash\nnpm install\n\\`\\`\\`\n\n---\n\n### \"EADDRINUSE: address already in use :::3000\"\n\n**Cause:** Another process is using port 3000.\n\n**Fix (macOS\u002FLinux):**\n\\`\\`\\`bash\n# Find the process\nlsof -i :3000\n\n# Kill it (replace PID with actual number)\nkill -9 PID\n\\`\\`\\`\n\n**Or use a different port:**\n\\`\\`\\`javascript\napp.listen(process.env.PORT || 3001);\n\\`\\`\\`\n\n---\n\n### \"SyntaxError: Unexpected token\"\n\n**Cause:** Likely a typo or missing bracket.\n\n**Debug steps:**\n1. Check the line number in the error\n2. Look for missing `,`, `}`, or `)`\n3. Verify all strings are closed with matching quotes\n```\n\n### Proactive Error Prevention\n\nAdd warnings before common pitfalls:\n\n```markdown\n⚠️ **Windows users:** Use `set` instead of `export`:\n\\`\\`\\`bash\n# macOS\u002FLinux\nexport API_KEY=your_key\n\n# Windows Command Prompt\nset API_KEY=your_key\n\n# Windows PowerShell\n$env:API_KEY = Read-Host -AsSecureString \"API key\"\n\\`\\`\\`\n```\n\n---\n\n## Tutorial Templates\n\n### Quickstart Template (5-10 minutes)\n\n```markdown\n# [Product] Quickstart: [What You'll Do] in 5 Minutes\n\nGet [specific outcome] in under 5 minutes.\n\n## Prerequisites\n\n- [Requirement 1]\n- [Requirement 2]\n\n## Step 1: Install\n\n\\`\\`\\`bash\nnpm install your-package\n\\`\\`\\`\n\n## Step 2: Configure\n\nCreate a `.env` file:\n\\`\\`\\`\nAPI_KEY=your_key_here\n\\`\\`\\`\n\n## Step 3: Write Code\n\nCreate `index.js`:\n\\`\\`\\`javascript\n\u002F\u002F Complete, working code\n\\`\\`\\`\n\n## Step 4: Run It\n\n\\`\\`\\`bash\nnode index.js\n\\`\\`\\`\n\nExpected output:\n\\`\\`\\`\n[Output here]\n\\`\\`\\`\n\n## 🎉 You Did It!\n\nYou just [accomplished thing].\n\n**Next steps:**\n- [Link to full tutorial]\n- [Link to API docs]\n- [Link to examples repo]\n```\n\n### Full Tutorial Template (20-45 minutes)\n\n```markdown\n# Build a [Thing] with [Technology]\n\nLearn how to [outcome] by building [specific project].\n\n| | |\n|---|---|\n| **Time** | 30 minutes |\n| **Level** | Intermediate |\n| **Prerequisites** | Node.js 18+, basic JavaScript |\n\n## What You'll Build\n\n[Screenshot or diagram of final result]\n\nBy the end, you'll have:\n- ✅ [Capability 1]\n- ✅ [Capability 2]\n- ✅ [Capability 3]\n\n## Prerequisites\n\n### Required Software\n\n| Tool | Version | Verify |\n|------|---------|--------|\n| Node.js | 18+ | `node -v` |\n\n### Required Knowledge\n\n- [Concept 1] — [link to learn]\n- [Concept 2] — [link to learn]\n\n## Step 1: Project Setup\n\n[Setup instructions with verification]\n\n**Checkpoint:** You should see `[expected output]`.\n\n## Step 2: [First Feature]\n\n[Instructions]\n\n**Checkpoint:** Test with `[command]`.\n\n## Step 3: [Second Feature]\n\n[Instructions]\n\n## Step 4: [Third Feature]\n\n[Instructions]\n\n**Checkpoint:** Your app should now [do thing].\n\n## Complete Code\n\nHere's everything together:\n\n\\`\\`\\`javascript\n\u002F\u002F Full final code\n\\`\\`\\`\n\n## Troubleshooting\n\n### [Common Error 1]\n[Solution]\n\n### [Common Error 2]\n[Solution]\n\n## What You Learned\n\n- [Key concept 1]\n- [Key concept 2]\n- [Key concept 3]\n\n## Next Steps\n\n- **Go deeper:** [Link to advanced tutorial]\n- **Explore:** [Link to related feature]\n- **Get help:** [Link to Discord\u002Fcommunity]\n```\n\n---\n\n## Quality Checklist\n\nBefore publishing, verify:\n\n### Code Quality\n- [ ] Every code block runs without modification\n- [ ] All imports\u002Frequires are included\n- [ ] Expected output is shown\n- [ ] Error handling is included\n- [ ] Environment variables use `.env` pattern\n\n### Structure Quality\n- [ ] Prerequisites are explicit\n- [ ] Time estimate is accurate (test it!)\n- [ ] Checkpoints every 3-5 steps\n- [ ] Final complete code is provided\n- [ ] Troubleshooting covers likely errors\n\n### Accessibility\n- [ ] Works on Mac, Linux, AND Windows\n- [ ] Commands work in bash\u002Fzsh\u002FPowerShell\n- [ ] File paths use correct separators\n- [ ] No assumptions about installed tools\n\n---\n\n## Tools\n\n| Tool | Use Case |\n|------|----------|\n| **[Octolens](https:\u002F\u002Foctolens.com)** | Find common questions and errors developers encounter. Monitor Stack Overflow and GitHub issues for troubleshooting content. |\n| **Replit\u002FCodeSandbox** | Embed runnable examples |\n| **Carbon\u002FRay.so** | Beautiful code screenshots |\n| **Excalidraw** | Architecture diagrams |\n| **Terminalizer** | Record terminal sessions |\n| **Loom** | Quick video supplements |\n\n---\n\n## Related Skills\n\n- `developer-audience-context` — Understand skill level and environment\n- `devrel-content` — General technical writing principles\n- `developer-onboarding` — Optimize time to first success\n- `developer-seo` — Get tutorials found via search\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Ftechnical-tutorials",1782864000000,"jonathimer\u002Fdevmarketing-skills","community","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Ftechnical-tutorials",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add MHassan0000\u002FSkills --skill technical-tutorials",{"tool":45,"command":46},"bunx","bunx skills add MHassan0000\u002FSkills --skill technical-tutorials",{"tool":48,"command":49},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill technical-tutorials","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Ftechnical-tutorials\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"README.md","REFERENCE","参考文档",2276,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Ftechnical-tutorials\u002FREADME.md",[60,67,74,81,90,98],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]