[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DR42RC7ENW8P94831JR9HD":3,"skill-same:01M7DR42RC7ENW8P94831JR9HD":57},{"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":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7DR42RC7ENW8P94831JR9HD","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.\"","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\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: unknown\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},"unknown","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","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Ftechnical-tutorials",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill technical-tutorials",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill technical-tutorials",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill technical-tutorials","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftechnical-tutorials\u002FSKILL.md",true,[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"README.md","REFERENCE","参考文档",2276,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftechnical-tutorials\u002FREADME.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]