[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF0XE6R2H9Y3B2VD2TWDT7":3,"skill-same:01M6AF0XE6R2H9Y3B2VD2TWDT7":86},{"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":23,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6AF0XE6R2H9Y3B2VD2TWDT7","doordash-order-playbooks",null,"Named, context-bound saved DoorDash orders (\"post-gym\", \"late-night deploy\") recalled through the DoorDash CLI (dd-cli) with a mandatory cart-diff before any checkout link is handed over. Use when the user names a saved order (\"order my post-gym bowl\", \"the usual\", \"my Friday ramen\"), wants to save the order they just placed as a playbook, or asks to list\u002Fremove saved orders. Persists name→order-uuid playbooks across sessions, catches silent menu\u002Fprice drift on every recall, and self-heals stale playbooks when a restaurant's menu changes. Requires dd-cli (macOS Apple Silicon, waitlist-gated).","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33418,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-order-playbooks\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"doordash order playbooks","DoorDash","write","when","mkdir","cart","silicon","checkout","apple","across","self","delivery","drift","remove","edit","macos","read","command","Bash","playbook","dd","deploy","sessions","automation","cli","2026-11-10 10:12:30",false,"---\nname: doordash-order-playbooks\ndescription: Named, context-bound saved DoorDash orders (\"post-gym\", \"late-night deploy\") recalled through the DoorDash CLI (dd-cli) with a mandatory cart-diff before any checkout link is handed over. Use when the user names a saved order (\"order my post-gym bowl\", \"the usual\", \"my Friday ramen\"), wants to save the order they just placed as a playbook, or asks to list\u002Fremove saved orders. Persists name→order-uuid playbooks across sessions, catches silent menu\u002Fprice drift on every recall, and self-heals stale playbooks when a restaurant's menu changes. Requires dd-cli (macOS Apple Silicon, waitlist-gated).\nallowed-tools: Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit\nmetadata:\n  tags: [DoorDash, Food Delivery, CLI, Saved Orders, Reorder, Automation]\n---\n\n# DoorDash Order Playbooks\n\nSaved orders with names and contexts, recalled safely. A playbook maps a\nhuman name (\"post-gym\", \"late-night deploy\", \"Friday ramen\") to a concrete\nDoorDash order that can be rebuilt with `dd-cli order reorder` — plus enough\nstored detail to **detect drift** (menu changes, price hikes, substitutions)\nbefore the user is ever handed a checkout link.\n\n> Unofficial community skill built on DoorDash's `doordash-oss\u002Fdoordash-cli`.\n> `dd-cli` must be installed, on PATH, and logged in (`dd-cli login`).\n\n## Why this exists\n\n`dd-cli order history` already lists past orders — but Claude has no\ncross-session memory of *which* order is \"the post-gym one\", and plain\nreordering silently accepts whatever the restaurant's menu says *today*:\nsubstituted items, missing items, higher prices. This skill stores the\nmapping AND makes a cart-diff against the stored baseline **mandatory**\nbefore emitting any checkout URL. Silent drift becomes a caught event.\n\n## State\n\nSingle JSON file: `~\u002F.claude\u002Fdd-cli\u002Fplaybooks.json`\n\n```json\n{\n  \"playbooks\": {\n    \"post-gym\": {\n      \"order_uuid\": \"\u003Cuuid from dd-cli order history>\",\n      \"restaurant\": \"Sweetgreen\",\n      \"items_summary\": [\n        { \"name\": \"Harvest Bowl\", \"qty\": 1, \"price\": 13.95 },\n        { \"name\": \"Lemonade\", \"qty\": 1, \"price\": 3.5 }\n      ],\n      \"baseline_total\": 17.45,\n      \"tolerance_pct\": 10,\n      \"contexts\": [\"post-gym\", \"gym\", \"workout\"],\n      \"last_used\": \"2026-07-19\",\n      \"times_used\": 4\n    }\n  },\n  \"preflight\": { \"verified\": false, \"notes\": \"\" }\n}\n```\n\nCreate the directory and file on first use (`mkdir -p ~\u002F.claude\u002Fdd-cli`).\nPrices are pre-fee subtotals — say so when presenting totals.\n\n## Preflight (first use only — REQUIRED)\n\nThis skill assumes `dd-cli order reorder --order-uuid Y` returns a cart-uuid\nthat `cart show` and `order checkout-url` accept. That handoff is\nload-bearing and must be verified empirically once per install:\n\n1. Run `dd-cli order reorder --help` and `dd-cli order checkout-url --help`\n   to confirm flags.\n2. On the first real recall, after running `reorder`, confirm the output\n   contains a cart-uuid and that `dd-cli cart show --cart-uuid \u003Cit>` works.\n3. Record the outcome in `preflight.verified` (+ any format notes in\n   `preflight.notes`) so future sessions skip this step.\n\nIf the handoff does NOT work as assumed, fall back to rebuilding the cart\nmanually (`dd-cli search` → `cart add-items`) and record that in\n`preflight.notes`.\n\n## Flow 1 — Recall (the main flow)\n\nUser says something like \"order my post-gym bowl\" \u002F \"the usual after the gym\":\n\n1. **Match**: fuzzy-match the request against playbook names and `contexts`.\n   Ambiguous → ask. No match → offer Flow 2 (capture) instead.\n2. **Rebuild**: `dd-cli order reorder --order-uuid \u003Cstored uuid>`. Capture\n   the cart-uuid from the output.\n3. **MANDATORY diff**: run `dd-cli cart show --cart-uuid \u003Ccart-uuid>` and\n   compare against the stored `items_summary` + `baseline_total`:\n\n   | | Stored | Current |\n   |---|---|---|\n   | Harvest Bowl | $13.95 | $14.95 ⬆ |\n   | Lemonade | $3.50 | ❌ missing |\n   | **Subtotal** | **$17.45** | **$14.95** |\n\n   Present the diff table to the user. Never skip this step, even when\n   everything matches — say \"matches your baseline\" explicitly.\n4. **Gate**: if items are missing\u002Fsubstituted, or the subtotal exceeds\n   `baseline_total` by more than `tolerance_pct`, STOP and ask the user how\n   to proceed (accept, edit cart via `cart remove-item`\u002F`cart add-items`, or\n   abort). Do NOT hand over a checkout link silently.\n5. **Checkout**: only after the diff is shown (and approved when the gate\n   tripped): `dd-cli order checkout-url --cart-uuid \u003Ccart-uuid>`. Hand the\n   URL to the user — payment always happens on the DoorDash page, by the\n   human.\n6. **Update**: bump `last_used` \u002F `times_used`; if the user accepted new\n   prices, offer to refresh `items_summary` and `baseline_total`.\n\n## Flow 2 — Capture\n\nAfter ANY completed order (via playbook or bespoke), offer once — don't nag:\n\"Want to save this as a playbook?\" If yes:\n\n1. `dd-cli order history` — take the most recent order's uuid.\n2. Ask for a name and optional context words (\"when should I suggest this?\").\n3. Write the entry with `items_summary` and `baseline_total` from the cart\n   that was just built (or from the history entry if it shows detail).\n4. Default `tolerance_pct`: 10.\n\n## Flow 3 — Staleness \u002F self-heal\n\nWhen `order reorder` fails or the diff shows the restaurant no longer offers\nthe stored items:\n\n1. Tell the user the playbook is stale and why.\n2. `dd-cli search --query \"\u003Crestaurant name>\"` — confirm the restaurant still\n   exists on DoorDash. Gone → offer to retire the playbook or find a\n   replacement.\n3. Rebuild an equivalent cart (`cart add-items`, navigating with `--help` as\n   needed), confirm with the user, and after a successful checkout-url\n   handoff refresh the playbook's `order_uuid` from `dd-cli order history`.\n\n## Rules\n\n- **Never emit a checkout URL without showing the diff first.** This is the\n  contract of the skill.\n- Read uuids from real command output; never fabricate or guess them.\n- One capture offer per order, max. Respect a \"no\".\n- Totals you can verify are pre-fee subtotals; final totals (fees, tip, tax)\n  appear only on the DoorDash payment page. Say so.\n- If `dd-cli` reports auth\u002Fwaitlist errors, stop and tell the user to run\n  `dd-cli login` — don't retry in a loop.\n","# DoorDash Order Playbooks\n\nSaved orders with names and contexts, recalled safely. A playbook maps a\nhuman name (\"post-gym\", \"late-night deploy\", \"Friday ramen\") to a concrete\nDoorDash order that can be rebuilt with `dd-cli order reorder` — plus enough\nstored detail to **detect drift** (menu changes, price hikes, substitutions)\nbefore the user is ever handed a checkout link.\n\n> Unofficial community skill built on DoorDash's `doordash-oss\u002Fdoordash-cli`.\n> `dd-cli` must be installed, on PATH, and logged in (`dd-cli login`).\n\n## Why this exists\n\n`dd-cli order history` already lists past orders — but Claude has no\ncross-session memory of *which* order is \"the post-gym one\", and plain\nreordering silently accepts whatever the restaurant's menu says *today*:\nsubstituted items, missing items, higher prices. This skill stores the\nmapping AND makes a cart-diff against the stored baseline **mandatory**\nbefore emitting any checkout URL. Silent drift becomes a caught event.\n\n## State\n\nSingle JSON file: `~\u002F.claude\u002Fdd-cli\u002Fplaybooks.json`\n\n```json\n{\n  \"playbooks\": {\n    \"post-gym\": {\n      \"order_uuid\": \"\u003Cuuid from dd-cli order history>\",\n      \"restaurant\": \"Sweetgreen\",\n      \"items_summary\": [\n        { \"name\": \"Harvest Bowl\", \"qty\": 1, \"price\": 13.95 },\n        { \"name\": \"Lemonade\", \"qty\": 1, \"price\": 3.5 }\n      ],\n      \"baseline_total\": 17.45,\n      \"tolerance_pct\": 10,\n      \"contexts\": [\"post-gym\", \"gym\", \"workout\"],\n      \"last_used\": \"2026-07-19\",\n      \"times_used\": 4\n    }\n  },\n  \"preflight\": { \"verified\": false, \"notes\": \"\" }\n}\n```\n\nCreate the directory and file on first use (`mkdir -p ~\u002F.claude\u002Fdd-cli`).\nPrices are pre-fee subtotals — say so when presenting totals.\n\n## Preflight (first use only — REQUIRED)\n\nThis skill assumes `dd-cli order reorder --order-uuid Y` returns a cart-uuid\nthat `cart show` and `order checkout-url` accept. That handoff is\nload-bearing and must be verified empirically once per install:\n\n1. Run `dd-cli order reorder --help` and `dd-cli order checkout-url --help`\n   to confirm flags.\n2. On the first real recall, after running `reorder`, confirm the output\n   contains a cart-uuid and that `dd-cli cart show --cart-uuid \u003Cit>` works.\n3. Record the outcome in `preflight.verified` (+ any format notes in\n   `preflight.notes`) so future sessions skip this step.\n\nIf the handoff does NOT work as assumed, fall back to rebuilding the cart\nmanually (`dd-cli search` → `cart add-items`) and record that in\n`preflight.notes`.\n\n## Flow 1 — Recall (the main flow)\n\nUser says something like \"order my post-gym bowl\" \u002F \"the usual after the gym\":\n\n1. **Match**: fuzzy-match the request against playbook names and `contexts`.\n   Ambiguous → ask. No match → offer Flow 2 (capture) instead.\n2. **Rebuild**: `dd-cli order reorder --order-uuid \u003Cstored uuid>`. Capture\n   the cart-uuid from the output.\n3. **MANDATORY diff**: run `dd-cli cart show --cart-uuid \u003Ccart-uuid>` and\n   compare against the stored `items_summary` + `baseline_total`:\n\n   | | Stored | Current |\n   |---|---|---|\n   | Harvest Bowl | $13.95 | $14.95 ⬆ |\n   | Lemonade | $3.50 | ❌ missing |\n   | **Subtotal** | **$17.45** | **$14.95** |\n\n   Present the diff table to the user. Never skip this step, even when\n   everything matches — say \"matches your baseline\" explicitly.\n4. **Gate**: if items are missing\u002Fsubstituted, or the subtotal exceeds\n   `baseline_total` by more than `tolerance_pct`, STOP and ask the user how\n   to proceed (accept, edit cart via `cart remove-item`\u002F`cart add-items`, or\n   abort). Do NOT hand over a checkout link silently.\n5. **Checkout**: only after the diff is shown (and approved when the gate\n   tripped): `dd-cli order checkout-url --cart-uuid \u003Ccart-uuid>`. Hand the\n   URL to the user — payment always happens on the DoorDash page, by the\n   human.\n6. **Update**: bump `last_used` \u002F `times_used`; if the user accepted new\n   prices, offer to refresh `items_summary` and `baseline_total`.\n\n## Flow 2 — Capture\n\nAfter ANY completed order (via playbook or bespoke), offer once — don't nag:\n\"Want to save this as a playbook?\" If yes:\n\n1. `dd-cli order history` — take the most recent order's uuid.\n2. Ask for a name and optional context words (\"when should I suggest this?\").\n3. Write the entry with `items_summary` and `baseline_total` from the cart\n   that was just built (or from the history entry if it shows detail).\n4. Default `tolerance_pct`: 10.\n\n## Flow 3 — Staleness \u002F self-heal\n\nWhen `order reorder` fails or the diff shows the restaurant no longer offers\nthe stored items:\n\n1. Tell the user the playbook is stale and why.\n2. `dd-cli search --query \"\u003Crestaurant name>\"` — confirm the restaurant still\n   exists on DoorDash. Gone → offer to retire the playbook or find a\n   replacement.\n3. Rebuild an equivalent cart (`cart add-items`, navigating with `--help` as\n   needed), confirm with the user, and after a successful checkout-url\n   handoff refresh the playbook's `order_uuid` from `dd-cli order history`.\n\n## Rules\n\n- **Never emit a checkout URL without showing the diff first.** This is the\n  contract of the skill.\n- Read uuids from real command output; never fabricate or guess them.\n- One capture offer per order, max. Respect a \"no\".\n- Totals you can verify are pre-fee subtotals; final totals (fees, tip, tax)\n  appear only on the DoorDash payment page. Say so.\n- If `dd-cli` reports auth\u002Fwaitlist errors, stop and tell the user to run\n  `dd-cli login` — don't retry in a loop.\n",{"name":5,"metadata":54,"description":7,"allowed-tools":61},{"tags":55},[25,56,57,58,59,60],"Food Delivery","CLI","Saved Orders","Reorder","Automation","Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-order-playbooks",3926,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-12 14:45:56",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add davila7\u002Fclaude-code-templates --skill doordash-order-playbooks",{"tool":78,"command":79},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill doordash-order-playbooks",{"tool":81,"command":82},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill doordash-order-playbooks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdoordash\u002Fdoordash-order-playbooks\u002FSKILL.md",true,[],[87,114,141,174,209,233],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":94,"publishedAt":49},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[93],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[95,96,97,98,99,100,101,102,103,27,104,105,106,107,108,109,110,111,112,113],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":49},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[120],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[122,123,124,125,126,127,128,129,130,131,132,27,133,134,135,136,137,138,139,140],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":156,"publishedAt":49},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[147,150,151],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[157,158,159,160,161,162,163,100,164,165,166,167,168,169,170,103,171,172,27,173],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":179,"sourceHtmlUrl":180,"categories":181,"keywords":185,"publishedAt":49},"01M6AFY6F7CC2BBZP1QD6VTNVC","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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[182],{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,100,208],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":213,"sourceHtmlUrl":214,"categories":215,"keywords":220,"publishedAt":49},"01M6AFWF33SFV9Z3SF4PEEE4BF","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\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[216,219],{"categoryNo":217,"categoryName":218,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},[221,222,223,224,225,187,226,196,197,227,228,229,230,100,231,105,232],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":237,"sourceHtmlUrl":238,"categories":239,"keywords":247,"publishedAt":49},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[240,243,244],{"categoryNo":241,"categoryName":242,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":245,"categoryName":246,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000036","内容创作者",[248,249,250,251,252,253,254,255,189,256,199,133,257,258,259,260,261,169,262,27,263,264,265,266,267,111,268],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]