[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE65D0A6JGM0T7WWNHTG12":3,"skill-same:01M6AE65D0A6JGM0T7WWNHTG12":114},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":27,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6AE65D0A6JGM0T7WWNHTG12","develop-web-game",null,"Use when Codex is building or iterating on a web game (HTML\u002FJS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots\u002Ftext, and review console errors with render_game_to_text.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fdevelop-web-game\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fdevelop-web-game\u002FSKILL.md",[19,24],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"web game","web","develop","develop web game","game","when","testing","inspect","errors","render","input","html","short","text","loop","openai","console","run","development","test","playwright","implement","codex","review","screenshots","2026-11-10 10:12:30",false,"---\nname: \"develop-web-game\"\ndescription: \"Use when Codex is building or iterating on a web game (HTML\u002FJS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots\u002Ftext, and review console errors with render_game_to_text.\"\nmetadata:\n  author: openai\n---\n\n\n# Develop Web Game\n\nBuild games in small steps and validate every change. Treat each iteration as: implement → act → pause → observe → adjust.\n\n## Skill paths (set once)\n\n```bash\nexport CODEX_HOME=\"${CODEX_HOME:-$HOME\u002F.codex}\"\nexport WEB_GAME_CLIENT=\"$CODEX_HOME\u002Fskills\u002Fdevelop-web-game\u002Fscripts\u002Fweb_game_playwright_client.js\"\nexport WEB_GAME_ACTIONS=\"$CODEX_HOME\u002Fskills\u002Fdevelop-web-game\u002Freferences\u002Faction_payloads.json\"\n```\n\nUser-scoped skills install under `$CODEX_HOME\u002Fskills` (default: `~\u002F.codex\u002Fskills`).\n\n## Workflow\n\n1. **Pick a goal.** Define a single feature or behavior to implement.\n2. **Implement small.** Make the smallest change that moves the game forward.\n3. **Ensure integration points.** Provide a single canvas and `window.render_game_to_text` so the test loop can read state.\n4. **Add `window.advanceTime(ms)`.** Strongly prefer a deterministic step hook so the Playwright script can advance frames reliably; without it, automated tests can be flaky.\n5. **Initialize progress.md.** If `progress.md` exists, read it first and confirm the original user prompt is recorded at the top (prefix with `Original prompt:`). Also note any TODOs and suggestions left by the previous agent. If missing, create it and write `Original prompt: \u003Cprompt>` at the top before appending updates.\n6. **Verify Playwright availability.** Ensure `playwright` is available (local dependency or global install). If unsure, check `npx` first.\n7. **Run the Playwright test script.** You must run `$WEB_GAME_CLIENT` after each meaningful change; do not invent a new client unless required.\n8. **Use the payload reference.** Base actions on `$WEB_GAME_ACTIONS` to avoid guessing keys.\n9. **Inspect state.** Capture screenshots and text state after each burst.\n10. **Inspect screenshots.** Open the latest screenshot, verify expected visuals, fix any issues, and rerun the script. Repeat until correct.\n11. **Verify controls and state (multi-step focus).** Exhaustively exercise all important interactions. For each, think through the full multi-step sequence it implies (cause → intermediate states → outcome) and verify the entire chain works end-to-end. Confirm `render_game_to_text` reflects the same state shown on screen. If anything is off, fix and rerun.\n    Examples of important interactions: move, jump, shoot\u002Fattack, interact\u002Fuse, select\u002Fconfirm\u002Fcancel in menus, pause\u002Fresume, restart, and any special abilities or puzzle actions defined by the request. Multi-step examples: shooting an enemy should reduce its health; when health reaches 0 it should disappear and update the score; collecting a key should unlock a door and allow level progression.\n12. **Check errors.** Review console errors and fix the first new issue before continuing.\n13. **Reset between scenarios.** Avoid cross-test state when validating distinct features.\n14. **Iterate with small deltas.** Change one variable at a time (frames, inputs, timing, positions), then repeat steps 7–13 until stable.\n\nExample command (actions required):\n```\nnode \"$WEB_GAME_CLIENT\" --url http:\u002F\u002Flocalhost:5173 --actions-file \"$WEB_GAME_ACTIONS\" --click-selector \"#start-btn\" --iterations 3 --pause-ms 250\n```\n\nExample actions (inline JSON):\n```json\n{\n  \"steps\": [\n    { \"buttons\": [\"left_mouse_button\"], \"frames\": 2, \"mouse_x\": 120, \"mouse_y\": 80 },\n    { \"buttons\": [], \"frames\": 6 },\n    { \"buttons\": [\"right\"], \"frames\": 8 },\n    { \"buttons\": [\"space\"], \"frames\": 4 }\n  ]\n}\n```\n\n## Test Checklist\n\nTest any new features added for the request and any areas your logic changes could affect. Identify issues, fix them, and re-run the tests to confirm they’re resolved.\n\nExamples of things to test:\n- Primary movement\u002Finteraction inputs (e.g., move, jump, shoot, confirm\u002Fselect).\n- Win\u002Flose or success\u002Ffail transitions.\n- Score\u002Fhealth\u002Fresource changes.\n- Boundary conditions (collisions, walls, screen edges).\n- Menu\u002Fpause\u002Fstart flow if present.\n- Any special actions tied to the request (powerups, combos, abilities, puzzles, timers).\n\n## Test Artifacts to Review\n\n- Latest screenshots from the Playwright run.\n- Latest `render_game_to_text` JSON output.\n- Console error logs (fix the first new error before continuing).\nYou must actually open and visually inspect the latest screenshots after running the Playwright script, not just generate them. Ensure everything that should be visible on screen is actually visible. Go beyond the start screen and capture gameplay screenshots that cover all newly added features. Treat the screenshots as the source of truth; if something is missing, it is missing in the build. If you suspect a headless\u002FWebGL capture issue, rerun the Playwright script in headed mode and re-check. Fix and rerun in a tight loop until the screenshots and text state look correct. Once fixes are verified, re-test all important interactions and controls, confirm they work, and ensure your changes did not introduce regressions. If they did, fix them and rerun everything in a loop until interactions, text state, and controls all work as expected. Be exhaustive in testing controls; broken games are not acceptable.\n\n## Core Game Guidelines\n\n### Canvas + Layout\n- Prefer a single canvas centered in the window.\n\n### Visuals\n- Keep on-screen text minimal; show controls on a start\u002Fmenu screen rather than overlaying them during play.\n- Avoid overly dark scenes unless the design calls for it. Make key elements easy to see.\n- Draw the background on the canvas itself instead of relying on CSS backgrounds.\n\n### Text State Output (render_game_to_text)\nExpose a `window.render_game_to_text` function that returns a concise JSON string representing the current game state. The text should include enough information to play the game without visuals.\n\nMinimal pattern:\n```js\nfunction renderGameToText() {\n  const payload = {\n    mode: state.mode,\n    player: { x: state.player.x, y: state.player.y, r: state.player.r },\n    entities: state.entities.map((e) => ({ x: e.x, y: e.y, r: e.r })),\n    score: state.score,\n  };\n  return JSON.stringify(payload);\n}\nwindow.render_game_to_text = renderGameToText;\n```\n\nKeep the payload succinct and biased toward on-screen\u002Finteractive elements. Prefer current, visible entities over full history.\nInclude a clear coordinate system note (origin and axis directions), and encode all player-relevant state: player position\u002Fvelocity, active obstacles\u002Fenemies, collectibles, timers\u002Fcooldowns, score, and any mode\u002Fstate flags needed to make correct decisions. Avoid large histories; only include what's currently relevant and visible.\n\n### Time Stepping Hook\nProvide a deterministic time-stepping hook so the Playwright client can advance the game in controlled increments. Expose `window.advanceTime(ms)` (or a thin wrapper that forwards to your game update loop) and have the game loop use it when present.\nThe Playwright test script uses this hook to step frames deterministically during automated testing.\n\nMinimal pattern:\n```js\nwindow.advanceTime = (ms) => {\n  const steps = Math.max(1, Math.round(ms \u002F (1000 \u002F 60)));\n  for (let i = 0; i \u003C steps; i++) update(1 \u002F 60);\n  render();\n};\n```\n\n### Fullscreen Toggle\n- Use a single key (prefer `f`) to toggle fullscreen on\u002Foff.\n- Allow `Esc` to exit fullscreen.\n- When fullscreen toggles, resize the canvas\u002Frendering so visuals and input mapping stay correct.\n\n## Progress Tracking\n\nCreate a `progress.md` file if it doesn't exist, and append TODOs, notes, gotchas, and loose ends as you go so another agent can pick up seamlessly.\nIf a `progress.md` file already exists, read it first, including the original user prompt at the top (you may be continuing another agent's work). Do not overwrite the original prompt; preserve it.\nUpdate `progress.md` after each meaningful chunk of work (feature added, bug found, test run, or decision made).\nAt the end of your work, leave TODOs and suggestions for the next agent in `progress.md`.\n\n## Playwright Prerequisites\n\n- Prefer a local `playwright` dependency if the project already has it.\n- If unsure whether Playwright is available, check for `npx`:\n  ```\n  command -v npx >\u002Fdev\u002Fnull 2>&1\n  ```\n- If `npx` is missing, install Node\u002Fnpm and then install Playwright globally:\n  ```\n  npm install -g @playwright\u002Fmcp@latest\n  ```\n- Do not switch to `@playwright\u002Ftest` unless explicitly asked; stick to the client script.\n\n## Scripts\n\n- `$WEB_GAME_CLIENT` (installed default: `$CODEX_HOME\u002Fskills\u002Fdevelop-web-game\u002Fscripts\u002Fweb_game_playwright_client.js`) — Playwright-based action loop with virtual-time stepping, screenshot capture, and console error buffering. You must pass an action burst via `--actions-file`, `--actions-json`, or `--click`.\n\n## References\n\n- `$WEB_GAME_ACTIONS` (installed default: `$CODEX_HOME\u002Fskills\u002Fdevelop-web-game\u002Freferences\u002Faction_payloads.json`) — example action payloads (keyboard + mouse, per-frame capture). Use these to build your burst.\n","# Develop Web Game\n\nBuild games in small steps and validate every change. Treat each iteration as: implement → act → pause → observe → adjust.\n\n## Skill paths (set once)\n\n```bash\nexport CODEX_HOME=\"${CODEX_HOME:-$HOME\u002F.codex}\"\nexport WEB_GAME_CLIENT=\"$CODEX_HOME\u002Fskills\u002Fdevelop-web-game\u002Fscripts\u002Fweb_game_playwright_client.js\"\nexport WEB_GAME_ACTIONS=\"$CODEX_HOME\u002Fskills\u002Fdevelop-web-game\u002Freferences\u002Faction_payloads.json\"\n```\n\nUser-scoped skills install under `$CODEX_HOME\u002Fskills` (default: `~\u002F.codex\u002Fskills`).\n\n## Workflow\n\n1. **Pick a goal.** Define a single feature or behavior to implement.\n2. **Implement small.** Make the smallest change that moves the game forward.\n3. **Ensure integration points.** Provide a single canvas and `window.render_game_to_text` so the test loop can read state.\n4. **Add `window.advanceTime(ms)`.** Strongly prefer a deterministic step hook so the Playwright script can advance frames reliably; without it, automated tests can be flaky.\n5. **Initialize progress.md.** If `progress.md` exists, read it first and confirm the original user prompt is recorded at the top (prefix with `Original prompt:`). Also note any TODOs and suggestions left by the previous agent. If missing, create it and write `Original prompt: \u003Cprompt>` at the top before appending updates.\n6. **Verify Playwright availability.** Ensure `playwright` is available (local dependency or global install). If unsure, check `npx` first.\n7. **Run the Playwright test script.** You must run `$WEB_GAME_CLIENT` after each meaningful change; do not invent a new client unless required.\n8. **Use the payload reference.** Base actions on `$WEB_GAME_ACTIONS` to avoid guessing keys.\n9. **Inspect state.** Capture screenshots and text state after each burst.\n10. **Inspect screenshots.** Open the latest screenshot, verify expected visuals, fix any issues, and rerun the script. Repeat until correct.\n11. **Verify controls and state (multi-step focus).** Exhaustively exercise all important interactions. For each, think through the full multi-step sequence it implies (cause → intermediate states → outcome) and verify the entire chain works end-to-end. Confirm `render_game_to_text` reflects the same state shown on screen. If anything is off, fix and rerun.\n    Examples of important interactions: move, jump, shoot\u002Fattack, interact\u002Fuse, select\u002Fconfirm\u002Fcancel in menus, pause\u002Fresume, restart, and any special abilities or puzzle actions defined by the request. Multi-step examples: shooting an enemy should reduce its health; when health reaches 0 it should disappear and update the score; collecting a key should unlock a door and allow level progression.\n12. **Check errors.** Review console errors and fix the first new issue before continuing.\n13. **Reset between scenarios.** Avoid cross-test state when validating distinct features.\n14. **Iterate with small deltas.** Change one variable at a time (frames, inputs, timing, positions), then repeat steps 7–13 until stable.\n\nExample command (actions required):\n```\nnode \"$WEB_GAME_CLIENT\" --url http:\u002F\u002Flocalhost:5173 --actions-file \"$WEB_GAME_ACTIONS\" --click-selector \"#start-btn\" --iterations 3 --pause-ms 250\n```\n\nExample actions (inline JSON):\n```json\n{\n  \"steps\": [\n    { \"buttons\": [\"left_mouse_button\"], \"frames\": 2, \"mouse_x\": 120, \"mouse_y\": 80 },\n    { \"buttons\": [], \"frames\": 6 },\n    { \"buttons\": [\"right\"], \"frames\": 8 },\n    { \"buttons\": [\"space\"], \"frames\": 4 }\n  ]\n}\n```\n\n## Test Checklist\n\nTest any new features added for the request and any areas your logic changes could affect. Identify issues, fix them, and re-run the tests to confirm they’re resolved.\n\nExamples of things to test:\n- Primary movement\u002Finteraction inputs (e.g., move, jump, shoot, confirm\u002Fselect).\n- Win\u002Flose or success\u002Ffail transitions.\n- Score\u002Fhealth\u002Fresource changes.\n- Boundary conditions (collisions, walls, screen edges).\n- Menu\u002Fpause\u002Fstart flow if present.\n- Any special actions tied to the request (powerups, combos, abilities, puzzles, timers).\n\n## Test Artifacts to Review\n\n- Latest screenshots from the Playwright run.\n- Latest `render_game_to_text` JSON output.\n- Console error logs (fix the first new error before continuing).\nYou must actually open and visually inspect the latest screenshots after running the Playwright script, not just generate them. Ensure everything that should be visible on screen is actually visible. Go beyond the start screen and capture gameplay screenshots that cover all newly added features. Treat the screenshots as the source of truth; if something is missing, it is missing in the build. If you suspect a headless\u002FWebGL capture issue, rerun the Playwright script in headed mode and re-check. Fix and rerun in a tight loop until the screenshots and text state look correct. Once fixes are verified, re-test all important interactions and controls, confirm they work, and ensure your changes did not introduce regressions. If they did, fix them and rerun everything in a loop until interactions, text state, and controls all work as expected. Be exhaustive in testing controls; broken games are not acceptable.\n\n## Core Game Guidelines\n\n### Canvas + Layout\n- Prefer a single canvas centered in the window.\n\n### Visuals\n- Keep on-screen text minimal; show controls on a start\u002Fmenu screen rather than overlaying them during play.\n- Avoid overly dark scenes unless the design calls for it. Make key elements easy to see.\n- Draw the background on the canvas itself instead of relying on CSS backgrounds.\n\n### Text State Output (render_game_to_text)\nExpose a `window.render_game_to_text` function that returns a concise JSON string representing the current game state. The text should include enough information to play the game without visuals.\n\nMinimal pattern:\n```js\nfunction renderGameToText() {\n  const payload = {\n    mode: state.mode,\n    player: { x: state.player.x, y: state.player.y, r: state.player.r },\n    entities: state.entities.map((e) => ({ x: e.x, y: e.y, r: e.r })),\n    score: state.score,\n  };\n  return JSON.stringify(payload);\n}\nwindow.render_game_to_text = renderGameToText;\n```\n\nKeep the payload succinct and biased toward on-screen\u002Finteractive elements. Prefer current, visible entities over full history.\nInclude a clear coordinate system note (origin and axis directions), and encode all player-relevant state: player position\u002Fvelocity, active obstacles\u002Fenemies, collectibles, timers\u002Fcooldowns, score, and any mode\u002Fstate flags needed to make correct decisions. Avoid large histories; only include what's currently relevant and visible.\n\n### Time Stepping Hook\nProvide a deterministic time-stepping hook so the Playwright client can advance the game in controlled increments. Expose `window.advanceTime(ms)` (or a thin wrapper that forwards to your game update loop) and have the game loop use it when present.\nThe Playwright test script uses this hook to step frames deterministically during automated testing.\n\nMinimal pattern:\n```js\nwindow.advanceTime = (ms) => {\n  const steps = Math.max(1, Math.round(ms \u002F (1000 \u002F 60)));\n  for (let i = 0; i \u003C steps; i++) update(1 \u002F 60);\n  render();\n};\n```\n\n### Fullscreen Toggle\n- Use a single key (prefer `f`) to toggle fullscreen on\u002Foff.\n- Allow `Esc` to exit fullscreen.\n- When fullscreen toggles, resize the canvas\u002Frendering so visuals and input mapping stay correct.\n\n## Progress Tracking\n\nCreate a `progress.md` file if it doesn't exist, and append TODOs, notes, gotchas, and loose ends as you go so another agent can pick up seamlessly.\nIf a `progress.md` file already exists, read it first, including the original user prompt at the top (you may be continuing another agent's work). Do not overwrite the original prompt; preserve it.\nUpdate `progress.md` after each meaningful chunk of work (feature added, bug found, test run, or decision made).\nAt the end of your work, leave TODOs and suggestions for the next agent in `progress.md`.\n\n## Playwright Prerequisites\n\n- Prefer a local `playwright` dependency if the project already has it.\n- If unsure whether Playwright is available, check for `npx`:\n  ```\n  command -v npx >\u002Fdev\u002Fnull 2>&1\n  ```\n- If `npx` is missing, install Node\u002Fnpm and then install Playwright globally:\n  ```\n  npm install -g @playwright\u002Fmcp@latest\n  ```\n- Do not switch to `@playwright\u002Ftest` unless explicitly asked; stick to the client script.\n\n## Scripts\n\n- `$WEB_GAME_CLIENT` (installed default: `$CODEX_HOME\u002Fskills\u002Fdevelop-web-game\u002Fscripts\u002Fweb_game_playwright_client.js`) — Playwright-based action loop with virtual-time stepping, screenshot capture, and console error buffering. You must pass an action burst via `--actions-file`, `--actions-json`, or `--click`.\n\n## References\n\n- `$WEB_GAME_ACTIONS` (installed default: `$CODEX_HOME\u002Fskills\u002Fdevelop-web-game\u002Freferences\u002Faction_payloads.json`) — example action payloads (keyboard + mouse, per-frame capture). Use these to build your burst.\n",{"name":5,"metadata":58,"description":7},{"author":43},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fdevelop-web-game",3931,"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-14 06:14:46",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add davila7\u002Fclaude-code-templates --skill develop-web-game",{"tool":75,"command":76},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill develop-web-game",{"tool":78,"command":79},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill develop-web-game","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fdevelop-web-game\u002FSKILL.md",true,[83,89,95,99,104,108],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"agents\u002Fopenai.yaml","REFERENCE","参考文档",299,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fdevelop-web-game\u002Fagents\u002Fopenai.yaml",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Fgame-small.svg","ASSET","资产文件",2706,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fdevelop-web-game\u002Fassets\u002Fgame-small.svg",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"assets\u002Fgame.png",2234,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fdevelop-web-game\u002Fassets\u002Fgame.png",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",10776,{"path":105,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Faction_payloads.json",141,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fdevelop-web-game\u002Freferences\u002Faction_payloads.json",{"path":109,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Fweb_game_playwright_client.js","SCRIPT","脚本",9963,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fdevelop-web-game\u002Fscripts\u002Fweb_game_playwright_client.js",[115,143,170,203,235,254],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":119,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":53},"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.","MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[122],{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},[124,125,126,127,128,129,130,131,132,33,133,134,135,136,137,138,139,140,141,142],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":119,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":53},"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",[149],{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},[151,152,153,154,155,156,157,158,159,160,161,33,162,163,164,165,166,167,168,169],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":119,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":185,"publishedAt":53},"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",[176,179,180],{"categoryNo":177,"categoryName":178,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},{"categoryNo":181,"categoryName":182,"taxonomyType":183,"taxonomyTypeDesc":184},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[186,187,188,189,190,191,192,129,193,194,195,196,197,198,199,132,200,201,33,202],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":207,"sourceHtmlUrl":208,"categories":209,"keywords":213,"publishedAt":53},"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.","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",[210],{"categoryNo":211,"categoryName":212,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000009","前端开发",[214,29,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,39,233,129,234],"artifacts builder","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","single-file","ui components",{"skillNo":236,"name":237,"nameZh":6,"description":238,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":239,"sourceHtmlUrl":240,"categories":241,"keywords":244,"publishedAt":53},"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",[242,243],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},{"categoryNo":211,"categoryName":212,"taxonomyType":22,"taxonomyTypeDesc":23},[245,34,246,247,48,29,248,223,224,249,250,251,52,129,252,134,253],"webapp testing","webapp","browser","applications","debugging","toolkit","logs","local","behavior",{"skillNo":255,"name":256,"nameZh":6,"description":257,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":258,"sourceHtmlUrl":259,"categories":260,"keywords":268,"publishedAt":53},"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",[261,264,265],{"categoryNo":262,"categoryName":263,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},{"categoryNo":266,"categoryName":267,"taxonomyType":183,"taxonomyTypeDesc":184},"01JBSEEDCAT000000000000036","内容创作者",[269,270,271,272,45,273,274,275,216,276,226,162,277,51,278,40,279,198,280,33,281,282,283,284,285,140,286],"discernment nudge","nudge","interpretation","help","reasoning","data","writing","lookup","content","conversation","up","invoke","you","analysis","claims","argument","assemble","recommendations"]