[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF3P6M197319XJN39KP55K":3,"skill-same:01M6AF3P6M197319XJN39KP55K":87},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6AF3P6M197319XJN39KP55K","git-context-controller",null,"Git Context Controller (GCC) - Manages agent memory as a versioned file system under .GCC\u002F. This skill should be used when working on multi-step projects that benefit from structured memory persistence, milestone tracking, branching for alternative approaches, and cross-session context recovery. Triggers on \u002Fgcc commands or natural language like 'commit this progress', 'branch to try an alternative', 'merge results', 'recover context'.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33332,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fgit-context-controller\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],"git","controller","git context controller","context","branch","when","for","multi","as","triggers","milestone","natural language","session context","session","memory","system","projects","persistence","file","agent memory","merge","commit","2026-11-10 10:12:30",false,"---\nname: git-context-controller\ndescription: \"Git Context Controller (GCC) - Manages agent memory as a versioned file system under .GCC\u002F. This skill should be used when working on multi-step projects that benefit from structured memory persistence, milestone tracking, branching for alternative approaches, and cross-session context recovery. Triggers on \u002Fgcc commands or natural language like 'commit this progress', 'branch to try an alternative', 'merge results', 'recover context'.\"\n---\n\n# Git Context Controller (GCC)\n\n## Overview\n\nGCC transforms agent memory from a passive token stream into a structured, versioned file system under `.GCC\u002F`. Inspired by Git, it provides four operations — COMMIT, BRANCH, MERGE, CONTEXT — to persist milestones, explore alternatives in isolation, synthesize results, and recover historical context efficiently.\n\n## Initialization\n\nOn first use, check if `.GCC\u002F` exists in the project root. If not, run `scripts\u002Fgcc_init.sh` to create the directory structure:\n\n```\n.GCC\u002F\n├── main.md          # Global roadmap and objectives\n├── metadata.yaml    # Infrastructure state (branches, file tree, config)\n├── commit.md        # Commit history for main branch\n├── log.md           # OTA execution log for main branch\n└── branches\u002F        # Isolated workspaces for experiments\n    └── \u003Cbranch-name>\u002F\n        ├── commit.md\n        ├── log.md\n        └── summary.md\n```\n\nFor detailed file format specifications, read `references\u002Ffile_formats.md`.\n\n## Configuration\n\nGCC behavior is controlled via `metadata.yaml`:\n\n- `proactive_commits: true` — Automatically suggest commits after completing coherent sub-tasks\n- `proactive_commits: false` — Only commit when explicitly requested\n\nToggle with: \"enable\u002Fdisable proactive commits\" or by editing `metadata.yaml`.\n\n## Commands\n\n### COMMIT\n\nPersist a milestone on the current branch.\n\n**Triggers**: `\u002Fgcc commit \u003Csummary>`, \"commit this progress\", \"save this milestone\", \"checkpoint\"\n\n**Procedure**:\n1. Read the current branch's `commit.md` to determine the next commit number\n2. Append a new entry to `commit.md` with:\n   - Sequential ID (e.g., `[C004]`)\n   - Date (UTC ISO 8601)\n   - Current branch name\n   - Branch purpose (from `summary.md` if on a branch, or from `main.md`)\n   - Previous progress summary (1-2 sentences from last commit)\n   - This commit's contribution (detailed technical description with files touched)\n3. Append an OTA entry to `log.md` recording the commit action\n4. Update `metadata.yaml` file tree if files were created\u002Fmodified\n5. If on main branch, update milestones section in `main.md`\n\n**Proactive behavior**: When `proactive_commits: true`, suggest a commit after:\n- Completing a function, module, or coherent unit of work\n- Fixing a bug and verifying the fix\n- Finishing a research\u002Fexploration phase with conclusions\n- Any point where losing context would mean re-doing significant work\n\n### BRANCH\n\nCreate an isolated workspace for exploring an alternative approach.\n\n**Triggers**: `\u002Fgcc branch \u003Cname>`, \"branch to try...\", \"explore alternative...\", \"experiment with...\"\n\n**Procedure**:\n1. Create `.GCC\u002Fbranches\u002F\u003Cbranch-name>\u002F` directory\n2. Create `summary.md` with: purpose, parent branch, creation date, key hypotheses\n3. Create empty `commit.md` and `log.md` for the branch\n4. Update `metadata.yaml` to register the new branch\n5. Update `main.md` Active Branches section\n6. Log the branch creation in the parent branch's `log.md`\n\nFrom this point, all COMMITs and OTA logs go to the branch-specific files until a MERGE or explicit branch switch.\n\n### MERGE\n\nIntegrate a completed branch back into the main flow.\n\n**Triggers**: `\u002Fgcc merge \u003Cbranch>`, \"merge results from...\", \"integrate the experiment\", \"branch X is done\"\n\n**Procedure**:\n1. Read the branch's `summary.md` and `commit.md` to understand outcomes\n2. Append a synthesis commit to main's `commit.md` summarizing:\n   - What was tried\n   - What was learned\n   - What is being integrated (or why the branch is being abandoned)\n3. Update `main.md`:\n   - Add milestone entry with branch results\n   - Remove from Active Branches\n   - Update objectives if applicable\n4. Update `metadata.yaml`: set branch status to `merged` or `abandoned`\n5. Log the merge in main's `log.md`\n\n### CONTEXT\n\nRetrieve historical memory at different resolution levels.\n\n**Triggers**: `\u002Fgcc context \u003Cflag>`, \"what did we do on...\", \"recover context\", \"show me the history\", \"where were we\"\n\n**Flags**:\n\n- `--branch [name]` — Read `summary.md` and latest commits for a specific branch (or current branch if no name). Provides high-level understanding of what happened and why.\n\n- `--log [n]` — Read last N entries (default 20) from the current branch's `log.md`. Provides fine-grained OTA traces for debugging or resuming interrupted work.\n\n- `--metadata` — Read `metadata.yaml` to recover project structure: file tree, dependencies, active branches, configuration.\n\n- `--full` — Read `main.md` for the complete project roadmap, all milestones, and active branches. Use for cross-session recovery or handoff to another agent.\n\nWhen no flag is specified, default to `--branch` for the current active branch.\n\n## OTA Logging\n\nThroughout all work (not just during explicit commands), maintain the OTA execution log:\n\n1. **Observation**: What was noticed or discovered\n2. **Thought**: Reasoning about what to do next\n3. **Action**: What action was taken\n\nAppend entries to the active branch's `log.md`. Keep a maximum of 50 entries; when exceeding, remove the oldest entries. Each entry includes a sequential ID, timestamp, and branch name.\n\nLog OTA entries at meaningful decision points — not every single action, but significant observations, strategy changes, and outcomes.\n\n## Cross-Session Recovery\n\nWhen starting a new session on an existing project with `.GCC\u002F`:\n\n1. Read `metadata.yaml` to understand project state and active branches\n2. Read `main.md` for the global roadmap and objectives\n3. Read the active branch's latest commits and log entries\n4. Resume work with full context of what was accomplished and what remains\n\n## Natural Language Mapping\n\n| User says | Command |\n|---|---|\n| \"save\u002Fcheckpoint\u002Fpersist this\" | COMMIT |\n| \"try a different approach\" | BRANCH |\n| \"that experiment worked, integrate it\" | MERGE |\n| \"where were we?\" \u002F \"what's the status?\" | CONTEXT --full |\n| \"what happened on branch X?\" | CONTEXT --branch X |\n| \"show recent activity\" | CONTEXT --log |\n| \"what files do we have?\" | CONTEXT --metadata |\n| \"enable\u002Fdisable auto-commits\" | Toggle `proactive_commits` in metadata.yaml |\n","# Git Context Controller (GCC)\n\n## Overview\n\nGCC transforms agent memory from a passive token stream into a structured, versioned file system under `.GCC\u002F`. Inspired by Git, it provides four operations — COMMIT, BRANCH, MERGE, CONTEXT — to persist milestones, explore alternatives in isolation, synthesize results, and recover historical context efficiently.\n\n## Initialization\n\nOn first use, check if `.GCC\u002F` exists in the project root. If not, run `scripts\u002Fgcc_init.sh` to create the directory structure:\n\n```\n.GCC\u002F\n├── main.md          # Global roadmap and objectives\n├── metadata.yaml    # Infrastructure state (branches, file tree, config)\n├── commit.md        # Commit history for main branch\n├── log.md           # OTA execution log for main branch\n└── branches\u002F        # Isolated workspaces for experiments\n    └── \u003Cbranch-name>\u002F\n        ├── commit.md\n        ├── log.md\n        └── summary.md\n```\n\nFor detailed file format specifications, read `references\u002Ffile_formats.md`.\n\n## Configuration\n\nGCC behavior is controlled via `metadata.yaml`:\n\n- `proactive_commits: true` — Automatically suggest commits after completing coherent sub-tasks\n- `proactive_commits: false` — Only commit when explicitly requested\n\nToggle with: \"enable\u002Fdisable proactive commits\" or by editing `metadata.yaml`.\n\n## Commands\n\n### COMMIT\n\nPersist a milestone on the current branch.\n\n**Triggers**: `\u002Fgcc commit \u003Csummary>`, \"commit this progress\", \"save this milestone\", \"checkpoint\"\n\n**Procedure**:\n1. Read the current branch's `commit.md` to determine the next commit number\n2. Append a new entry to `commit.md` with:\n   - Sequential ID (e.g., `[C004]`)\n   - Date (UTC ISO 8601)\n   - Current branch name\n   - Branch purpose (from `summary.md` if on a branch, or from `main.md`)\n   - Previous progress summary (1-2 sentences from last commit)\n   - This commit's contribution (detailed technical description with files touched)\n3. Append an OTA entry to `log.md` recording the commit action\n4. Update `metadata.yaml` file tree if files were created\u002Fmodified\n5. If on main branch, update milestones section in `main.md`\n\n**Proactive behavior**: When `proactive_commits: true`, suggest a commit after:\n- Completing a function, module, or coherent unit of work\n- Fixing a bug and verifying the fix\n- Finishing a research\u002Fexploration phase with conclusions\n- Any point where losing context would mean re-doing significant work\n\n### BRANCH\n\nCreate an isolated workspace for exploring an alternative approach.\n\n**Triggers**: `\u002Fgcc branch \u003Cname>`, \"branch to try...\", \"explore alternative...\", \"experiment with...\"\n\n**Procedure**:\n1. Create `.GCC\u002Fbranches\u002F\u003Cbranch-name>\u002F` directory\n2. Create `summary.md` with: purpose, parent branch, creation date, key hypotheses\n3. Create empty `commit.md` and `log.md` for the branch\n4. Update `metadata.yaml` to register the new branch\n5. Update `main.md` Active Branches section\n6. Log the branch creation in the parent branch's `log.md`\n\nFrom this point, all COMMITs and OTA logs go to the branch-specific files until a MERGE or explicit branch switch.\n\n### MERGE\n\nIntegrate a completed branch back into the main flow.\n\n**Triggers**: `\u002Fgcc merge \u003Cbranch>`, \"merge results from...\", \"integrate the experiment\", \"branch X is done\"\n\n**Procedure**:\n1. Read the branch's `summary.md` and `commit.md` to understand outcomes\n2. Append a synthesis commit to main's `commit.md` summarizing:\n   - What was tried\n   - What was learned\n   - What is being integrated (or why the branch is being abandoned)\n3. Update `main.md`:\n   - Add milestone entry with branch results\n   - Remove from Active Branches\n   - Update objectives if applicable\n4. Update `metadata.yaml`: set branch status to `merged` or `abandoned`\n5. Log the merge in main's `log.md`\n\n### CONTEXT\n\nRetrieve historical memory at different resolution levels.\n\n**Triggers**: `\u002Fgcc context \u003Cflag>`, \"what did we do on...\", \"recover context\", \"show me the history\", \"where were we\"\n\n**Flags**:\n\n- `--branch [name]` — Read `summary.md` and latest commits for a specific branch (or current branch if no name). Provides high-level understanding of what happened and why.\n\n- `--log [n]` — Read last N entries (default 20) from the current branch's `log.md`. Provides fine-grained OTA traces for debugging or resuming interrupted work.\n\n- `--metadata` — Read `metadata.yaml` to recover project structure: file tree, dependencies, active branches, configuration.\n\n- `--full` — Read `main.md` for the complete project roadmap, all milestones, and active branches. Use for cross-session recovery or handoff to another agent.\n\nWhen no flag is specified, default to `--branch` for the current active branch.\n\n## OTA Logging\n\nThroughout all work (not just during explicit commands), maintain the OTA execution log:\n\n1. **Observation**: What was noticed or discovered\n2. **Thought**: Reasoning about what to do next\n3. **Action**: What action was taken\n\nAppend entries to the active branch's `log.md`. Keep a maximum of 50 entries; when exceeding, remove the oldest entries. Each entry includes a sequential ID, timestamp, and branch name.\n\nLog OTA entries at meaningful decision points — not every single action, but significant observations, strategy changes, and outcomes.\n\n## Cross-Session Recovery\n\nWhen starting a new session on an existing project with `.GCC\u002F`:\n\n1. Read `metadata.yaml` to understand project state and active branches\n2. Read `main.md` for the global roadmap and objectives\n3. Read the active branch's latest commits and log entries\n4. Resume work with full context of what was accomplished and what remains\n\n## Natural Language Mapping\n\n| User says | Command |\n|---|---|\n| \"save\u002Fcheckpoint\u002Fpersist this\" | COMMIT |\n| \"try a different approach\" | BRANCH |\n| \"that experiment worked, integrate it\" | MERGE |\n| \"where were we?\" \u002F \"what's the status?\" | CONTEXT --full |\n| \"what happened on branch X?\" | CONTEXT --branch X |\n| \"show recent activity\" | CONTEXT --log |\n| \"what files do we have?\" | CONTEXT --metadata |\n| \"enable\u002Fdisable auto-commits\" | Toggle `proactive_commits` in metadata.yaml |\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fgit-context-controller",3911,"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-11 21:38:31",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add davila7\u002Fclaude-code-templates --skill git-context-controller",{"tool":67,"command":68},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill git-context-controller",{"tool":70,"command":71},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill git-context-controller","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fgit-context-controller\u002FSKILL.md",true,[75,81],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Ffile_formats.md","REFERENCE","参考文档",3212,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fgit-context-controller\u002Freferences\u002Ffile_formats.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fgcc_init.sh","SCRIPT","脚本",1524,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fgit-context-controller\u002Fscripts\u002Fgcc_init.sh",[88,114,141,174,208,232],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":95,"publishedAt":46},"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",[94],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[96,97,98,99,100,30,101,102,103,29,104,105,106,107,108,109,110,111,112,113],"scoring","pool","wealthville pool scoring","liquidity","which","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":46},"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,29,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":46},"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,30,164,165,166,167,168,169,170,103,171,172,29,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":46},"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,42,199,200,201,202,203,204,205,206,30,207],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":212,"sourceHtmlUrl":213,"categories":214,"keywords":219,"publishedAt":46},"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",[215,218],{"categoryNo":216,"categoryName":217,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},[220,221,222,223,224,187,225,196,197,226,227,228,229,30,230,105,231],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":236,"sourceHtmlUrl":237,"categories":238,"keywords":246,"publishedAt":46},"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",[239,242,243],{"categoryNo":240,"categoryName":241,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":244,"categoryName":245,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000036","内容创作者",[247,248,249,250,251,252,253,254,189,255,42,133,256,257,258,259,260,169,261,29,262,263,264,265,266,111,267],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]