[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M719RZNAM39YVMBNMT209D52":3,"skill-same:01M719RZNAM39YVMBNMT209D52":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M719RZNAM39YVMBNMT209D52","using-superpowers",null,"Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions","dahaliztupe-sketch\u002FKalmeron-Two","dahaliztupe-sketch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F271085317?v=4","01M719765Q83P08JCQ1SWNQR0N","01M719766HQBGF44W90MPJKTD2",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32],"superpowers","using superpowers","conversation","tool","how to","use","when","how","find","questions","2026-11-10 10:12:30",false,"---\nname: using-superpowers\ndescription: Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions\n---\n\n\u003CSUBAGENT-STOP>\nIf you were dispatched as a subagent to execute a specific task, skip this skill.\n\u003C\u002FSUBAGENT-STOP>\n\n\u003CEXTREMELY-IMPORTANT>\nIf you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.\n\nIF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.\n\nThis is not negotiable. This is not optional. You cannot rationalize your way out of this.\n\u003C\u002FEXTREMELY-IMPORTANT>\n\n## Instruction Priority\n\nSuperpowers skills override default system prompt behavior, but **user instructions always take precedence**:\n\n1. **User's explicit instructions** (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority\n2. **Superpowers skills** — override default system behavior where they conflict\n3. **Default system prompt** — lowest priority\n\nIf CLAUDE.md, GEMINI.md, or AGENTS.md says \"don't use TDD\" and a skill says \"always use TDD,\" follow the user's instructions. The user is in control.\n\n## How to Access Skills\n\n**In Claude Code:** Use the `Skill` tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.\n\n**In Copilot CLI:** Use the `skill` tool. Skills are auto-discovered from installed plugins. The `skill` tool works the same as Claude Code's `Skill` tool.\n\n**In Gemini CLI:** Skills activate via the `activate_skill` tool. Gemini loads skill metadata at session start and activates the full content on demand.\n\n**In other environments:** Check your platform's documentation for how skills are loaded.\n\n## Platform Adaptation\n\nSkills use Claude Code tool names. Non-CC platforms: see `references\u002Fcopilot-tools.md` (Copilot CLI), `references\u002Fcodex-tools.md` (Codex) for tool equivalents. Gemini CLI users get the tool mapping loaded automatically via GEMINI.md.\n\n# Using Skills\n\n## The Rule\n\n**Invoke relevant or requested skills BEFORE any response or action.** Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.\n\n```dot\ndigraph skill_flow {\n    \"User message received\" [shape=doublecircle];\n    \"About to EnterPlanMode?\" [shape=doublecircle];\n    \"Already brainstormed?\" [shape=diamond];\n    \"Invoke brainstorming skill\" [shape=box];\n    \"Might any skill apply?\" [shape=diamond];\n    \"Invoke Skill tool\" [shape=box];\n    \"Announce: 'Using [skill] to [purpose]'\" [shape=box];\n    \"Has checklist?\" [shape=diamond];\n    \"Create TodoWrite todo per item\" [shape=box];\n    \"Follow skill exactly\" [shape=box];\n    \"Respond (including clarifications)\" [shape=doublecircle];\n\n    \"About to EnterPlanMode?\" -> \"Already brainstormed?\";\n    \"Already brainstormed?\" -> \"Invoke brainstorming skill\" [label=\"no\"];\n    \"Already brainstormed?\" -> \"Might any skill apply?\" [label=\"yes\"];\n    \"Invoke brainstorming skill\" -> \"Might any skill apply?\";\n\n    \"User message received\" -> \"Might any skill apply?\";\n    \"Might any skill apply?\" -> \"Invoke Skill tool\" [label=\"yes, even 1%\"];\n    \"Might any skill apply?\" -> \"Respond (including clarifications)\" [label=\"definitely not\"];\n    \"Invoke Skill tool\" -> \"Announce: 'Using [skill] to [purpose]'\";\n    \"Announce: 'Using [skill] to [purpose]'\" -> \"Has checklist?\";\n    \"Has checklist?\" -> \"Create TodoWrite todo per item\" [label=\"yes\"];\n    \"Has checklist?\" -> \"Follow skill exactly\" [label=\"no\"];\n    \"Create TodoWrite todo per item\" -> \"Follow skill exactly\";\n}\n```\n\n## Red Flags\n\nThese thoughts mean STOP—you're rationalizing:\n\n| Thought | Reality |\n|---------|---------|\n| \"This is just a simple question\" | Questions are tasks. Check for skills. |\n| \"I need more context first\" | Skill check comes BEFORE clarifying questions. |\n| \"Let me explore the codebase first\" | Skills tell you HOW to explore. Check first. |\n| \"I can check git\u002Ffiles quickly\" | Files lack conversation context. Check for skills. |\n| \"Let me gather information first\" | Skills tell you HOW to gather information. |\n| \"This doesn't need a formal skill\" | If a skill exists, use it. |\n| \"I remember this skill\" | Skills evolve. Read current version. |\n| \"This doesn't count as a task\" | Action = task. Check for skills. |\n| \"The skill is overkill\" | Simple things become complex. Use it. |\n| \"I'll just do this one thing first\" | Check BEFORE doing anything. |\n| \"This feels productive\" | Undisciplined action wastes time. Skills prevent this. |\n| \"I know what that means\" | Knowing the concept ≠ using the skill. Invoke it. |\n\n## Skill Priority\n\nWhen multiple skills could apply, use this order:\n\n1. **Process skills first** (brainstorming, debugging) - these determine HOW to approach the task\n2. **Implementation skills second** (frontend-design, mcp-builder) - these guide execution\n\n\"Let's build X\" → brainstorming first, then implementation skills.\n\"Fix this bug\" → debugging first, then domain-specific skills.\n\n## Skill Types\n\n**Rigid** (TDD, debugging): Follow exactly. Don't adapt away discipline.\n\n**Flexible** (patterns): Adapt principles to context.\n\nThe skill itself tells you which.\n\n## User Instructions\n\nInstructions say WHAT, not HOW. \"Add X\" or \"Fix Y\" doesn't mean skip workflows.\n\n---\n\n## Available Skills Reference (Kalmeron — 2026-05-10)\n\n**Total: ~128 skills** across categories. Key categories:\n\n### Session Start (Always Read First)\n- `openwolf-memory` — start every session with .wolf\u002Fanatomy.md + cerebrum.md\n- `token-optimization` — read anatomy first, save ~30K tokens per session\n- `memory-persistence` — how to update .wolf\u002F memory files and hooks\n- `CLAUDE.md` (root) — project rules, patterns, architecture\n\n### OpenWolf Hooks (.wolf\u002Fhooks\u002F)\n- `session-start.sh` — orient in 200 tokens, surface bugs\u002Frules\n- `session-end.sh` — capture learnings before closing\n- `pre-commit.sh` — quality gates: tsc + i18n + route conflicts\n- `learn-from-error.sh` — log a new bug to buglog.json\n- `memory-persist.sh` — append a learning to cerebrum.md\n- `scan-anatomy.sh` — refresh token estimates in anatomy.md\n\n### Security (SAST — Run before releases)\n- `sast-orchestrator` — runs all 13 SAST skill checks in parallel\n- `sast-sql-injection`, `sast-xss`, `sast-rce`, `sast-ssrf`, `sast-idor`\n- `sast-xxe`, `sast-ssti`, `sast-jwt`, `sast-path-traversal`, `sast-file-upload`\n- `sast-broken-auth`, `sast-missing-auth`, `sast-graphql`\n- CI gate: `.github\u002Fworkflows\u002Fsast-skill.yml` (auto-runs on app\u002Fapi\u002F* changes)\n\n### Infrastructure (VoltAgent-style)\n- `firebase-patterns` — Firestore\u002FAuth\u002FStorage (Kalmeron-specific)\n- `vercel-deployment` — Next.js deployment & optimization\n- `stripe-integration` — Payment integration (Stripe + Fawry context)\n- `auth0-patterns` — Enterprise SSO alternative to Firebase Auth\n- `sentry-monitoring` — Error tracking & performance\n\n### Professional Workflow (ECC-inspired)\n- `pro-workflow` — full development loop: plan→read→edit→check→verify→commit\n- `parallelization` — batch independent operations, SAST parallel patterns\n- `verification-loops` — evidence before assertions, run commands then report\n- `token-optimization` — anatomy-first reading, targeted grep strategies\n- `memory-persistence` — .wolf\u002F memory system, when and what to persist\n\n### Kalmeron-Specific\n- `kalmeron-firestore-patterns` — Mandatory Firestore patterns (userId scoping, limit)\n- `kalmeron-i18n-workflow` — i18n mandatory workflow (ar.json + en.json)\n- `kalmeron-route-guide` — Route placement (dashboard vs root app\u002F)\n- `kalmeron-agent-builder` — Adding\u002Fextending agents\n- `kalmeron-ui-polish` — UI quality for Arabic-first screens\n\n### Process & Workflow\n- `brainstorming` — before any creative\u002Ffeature work\n- `systematic-debugging` — before fixing bugs\n- `verification-before-completion` — before claiming work is done\n- `writing-plans` — for multi-step tasks\n- `tdd` — test-driven development\n- `subagent-driven-development` — parallel subagent execution\n\n### C-Suite Advisory (34 skills)\n- `c-level-advisor\u002Fchief-of-staff` — orchestration entry point\n- `c-level-advisor\u002Fboard-meeting` — structured multi-role deliberation\n- Individual advisors: `ceo`, `cto`, `cfo`, `coo`, `cmo`, `clo`, `chro`, `cso`\n\n### Egyptian Business Seeds (17)\n- `kalmeron-seeds\u002Fceo-egypt`, `cto-egypt`, `cfo-egypt`, etc.\n\n### Product & Design\n- `impeccable` — UI\u002FUX mastery\n- `frontend-design` — production-grade frontend\n- `product-skills\u002F*` — 15 PM toolkit skills\n- `ux-audit` — walkthrough-based UX testing\n\n### Finance\n- `finance-skills\u002Ffinancial-analyst`\n- `finance-skills\u002Fsaas-metrics-coach`\n- `finance-skills\u002Fbusiness-investment-advisor`\n","\u003CSUBAGENT-STOP>\nIf you were dispatched as a subagent to execute a specific task, skip this skill.\n\u003C\u002FSUBAGENT-STOP>\n\n\u003CEXTREMELY-IMPORTANT>\nIf you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.\n\nIF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.\n\nThis is not negotiable. This is not optional. You cannot rationalize your way out of this.\n\u003C\u002FEXTREMELY-IMPORTANT>\n\n## Instruction Priority\n\nSuperpowers skills override default system prompt behavior, but **user instructions always take precedence**:\n\n1. **User's explicit instructions** (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority\n2. **Superpowers skills** — override default system behavior where they conflict\n3. **Default system prompt** — lowest priority\n\nIf CLAUDE.md, GEMINI.md, or AGENTS.md says \"don't use TDD\" and a skill says \"always use TDD,\" follow the user's instructions. The user is in control.\n\n## How to Access Skills\n\n**In Claude Code:** Use the `Skill` tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.\n\n**In Copilot CLI:** Use the `skill` tool. Skills are auto-discovered from installed plugins. The `skill` tool works the same as Claude Code's `Skill` tool.\n\n**In Gemini CLI:** Skills activate via the `activate_skill` tool. Gemini loads skill metadata at session start and activates the full content on demand.\n\n**In other environments:** Check your platform's documentation for how skills are loaded.\n\n## Platform Adaptation\n\nSkills use Claude Code tool names. Non-CC platforms: see `references\u002Fcopilot-tools.md` (Copilot CLI), `references\u002Fcodex-tools.md` (Codex) for tool equivalents. Gemini CLI users get the tool mapping loaded automatically via GEMINI.md.\n\n# Using Skills\n\n## The Rule\n\n**Invoke relevant or requested skills BEFORE any response or action.** Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.\n\n```dot\ndigraph skill_flow {\n    \"User message received\" [shape=doublecircle];\n    \"About to EnterPlanMode?\" [shape=doublecircle];\n    \"Already brainstormed?\" [shape=diamond];\n    \"Invoke brainstorming skill\" [shape=box];\n    \"Might any skill apply?\" [shape=diamond];\n    \"Invoke Skill tool\" [shape=box];\n    \"Announce: 'Using [skill] to [purpose]'\" [shape=box];\n    \"Has checklist?\" [shape=diamond];\n    \"Create TodoWrite todo per item\" [shape=box];\n    \"Follow skill exactly\" [shape=box];\n    \"Respond (including clarifications)\" [shape=doublecircle];\n\n    \"About to EnterPlanMode?\" -> \"Already brainstormed?\";\n    \"Already brainstormed?\" -> \"Invoke brainstorming skill\" [label=\"no\"];\n    \"Already brainstormed?\" -> \"Might any skill apply?\" [label=\"yes\"];\n    \"Invoke brainstorming skill\" -> \"Might any skill apply?\";\n\n    \"User message received\" -> \"Might any skill apply?\";\n    \"Might any skill apply?\" -> \"Invoke Skill tool\" [label=\"yes, even 1%\"];\n    \"Might any skill apply?\" -> \"Respond (including clarifications)\" [label=\"definitely not\"];\n    \"Invoke Skill tool\" -> \"Announce: 'Using [skill] to [purpose]'\";\n    \"Announce: 'Using [skill] to [purpose]'\" -> \"Has checklist?\";\n    \"Has checklist?\" -> \"Create TodoWrite todo per item\" [label=\"yes\"];\n    \"Has checklist?\" -> \"Follow skill exactly\" [label=\"no\"];\n    \"Create TodoWrite todo per item\" -> \"Follow skill exactly\";\n}\n```\n\n## Red Flags\n\nThese thoughts mean STOP—you're rationalizing:\n\n| Thought | Reality |\n|---------|---------|\n| \"This is just a simple question\" | Questions are tasks. Check for skills. |\n| \"I need more context first\" | Skill check comes BEFORE clarifying questions. |\n| \"Let me explore the codebase first\" | Skills tell you HOW to explore. Check first. |\n| \"I can check git\u002Ffiles quickly\" | Files lack conversation context. Check for skills. |\n| \"Let me gather information first\" | Skills tell you HOW to gather information. |\n| \"This doesn't need a formal skill\" | If a skill exists, use it. |\n| \"I remember this skill\" | Skills evolve. Read current version. |\n| \"This doesn't count as a task\" | Action = task. Check for skills. |\n| \"The skill is overkill\" | Simple things become complex. Use it. |\n| \"I'll just do this one thing first\" | Check BEFORE doing anything. |\n| \"This feels productive\" | Undisciplined action wastes time. Skills prevent this. |\n| \"I know what that means\" | Knowing the concept ≠ using the skill. Invoke it. |\n\n## Skill Priority\n\nWhen multiple skills could apply, use this order:\n\n1. **Process skills first** (brainstorming, debugging) - these determine HOW to approach the task\n2. **Implementation skills second** (frontend-design, mcp-builder) - these guide execution\n\n\"Let's build X\" → brainstorming first, then implementation skills.\n\"Fix this bug\" → debugging first, then domain-specific skills.\n\n## Skill Types\n\n**Rigid** (TDD, debugging): Follow exactly. Don't adapt away discipline.\n\n**Flexible** (patterns): Adapt principles to context.\n\nThe skill itself tells you which.\n\n## User Instructions\n\nInstructions say WHAT, not HOW. \"Add X\" or \"Fix Y\" doesn't mean skip workflows.\n\n---\n\n## Available Skills Reference (Kalmeron — 2026-05-10)\n\n**Total: ~128 skills** across categories. Key categories:\n\n### Session Start (Always Read First)\n- `openwolf-memory` — start every session with .wolf\u002Fanatomy.md + cerebrum.md\n- `token-optimization` — read anatomy first, save ~30K tokens per session\n- `memory-persistence` — how to update .wolf\u002F memory files and hooks\n- `CLAUDE.md` (root) — project rules, patterns, architecture\n\n### OpenWolf Hooks (.wolf\u002Fhooks\u002F)\n- `session-start.sh` — orient in 200 tokens, surface bugs\u002Frules\n- `session-end.sh` — capture learnings before closing\n- `pre-commit.sh` — quality gates: tsc + i18n + route conflicts\n- `learn-from-error.sh` — log a new bug to buglog.json\n- `memory-persist.sh` — append a learning to cerebrum.md\n- `scan-anatomy.sh` — refresh token estimates in anatomy.md\n\n### Security (SAST — Run before releases)\n- `sast-orchestrator` — runs all 13 SAST skill checks in parallel\n- `sast-sql-injection`, `sast-xss`, `sast-rce`, `sast-ssrf`, `sast-idor`\n- `sast-xxe`, `sast-ssti`, `sast-jwt`, `sast-path-traversal`, `sast-file-upload`\n- `sast-broken-auth`, `sast-missing-auth`, `sast-graphql`\n- CI gate: `.github\u002Fworkflows\u002Fsast-skill.yml` (auto-runs on app\u002Fapi\u002F* changes)\n\n### Infrastructure (VoltAgent-style)\n- `firebase-patterns` — Firestore\u002FAuth\u002FStorage (Kalmeron-specific)\n- `vercel-deployment` — Next.js deployment & optimization\n- `stripe-integration` — Payment integration (Stripe + Fawry context)\n- `auth0-patterns` — Enterprise SSO alternative to Firebase Auth\n- `sentry-monitoring` — Error tracking & performance\n\n### Professional Workflow (ECC-inspired)\n- `pro-workflow` — full development loop: plan→read→edit→check→verify→commit\n- `parallelization` — batch independent operations, SAST parallel patterns\n- `verification-loops` — evidence before assertions, run commands then report\n- `token-optimization` — anatomy-first reading, targeted grep strategies\n- `memory-persistence` — .wolf\u002F memory system, when and what to persist\n\n### Kalmeron-Specific\n- `kalmeron-firestore-patterns` — Mandatory Firestore patterns (userId scoping, limit)\n- `kalmeron-i18n-workflow` — i18n mandatory workflow (ar.json + en.json)\n- `kalmeron-route-guide` — Route placement (dashboard vs root app\u002F)\n- `kalmeron-agent-builder` — Adding\u002Fextending agents\n- `kalmeron-ui-polish` — UI quality for Arabic-first screens\n\n### Process & Workflow\n- `brainstorming` — before any creative\u002Ffeature work\n- `systematic-debugging` — before fixing bugs\n- `verification-before-completion` — before claiming work is done\n- `writing-plans` — for multi-step tasks\n- `tdd` — test-driven development\n- `subagent-driven-development` — parallel subagent execution\n\n### C-Suite Advisory (34 skills)\n- `c-level-advisor\u002Fchief-of-staff` — orchestration entry point\n- `c-level-advisor\u002Fboard-meeting` — structured multi-role deliberation\n- Individual advisors: `ceo`, `cto`, `cfo`, `coo`, `cmo`, `clo`, `chro`, `cso`\n\n### Egyptian Business Seeds (17)\n- `kalmeron-seeds\u002Fceo-egypt`, `cto-egypt`, `cfo-egypt`, etc.\n\n### Product & Design\n- `impeccable` — UI\u002FUX mastery\n- `frontend-design` — production-grade frontend\n- `product-skills\u002F*` — 15 PM toolkit skills\n- `ux-audit` — walkthrough-based UX testing\n\n### Finance\n- `finance-skills\u002Ffinancial-analyst`\n- `finance-skills\u002Fsaas-metrics-coach`\n- `finance-skills\u002Fbusiness-investment-advisor`\n",{"name":5,"description":7},"main","13d9afadbb6a87d6209fe4bd6ca2bbe4553119ac",".agents\u002Fskills\u002Fusing-superpowers",0,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two","https:\u002F\u002Fkalmeron-two.vercel.app","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch","2026-10-05 12:24:53",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add dahaliztupe-sketch\u002FKalmeron-Two --skill using-superpowers",{"tool":52,"command":53},"bunx","bunx skills add dahaliztupe-sketch\u002FKalmeron-Two --skill using-superpowers",{"tool":55,"command":56},"pnpm","pnpm dlx skills add dahaliztupe-sketch\u002FKalmeron-Two --skill using-superpowers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",true,[60,66,70],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fcodex-tools.md","REFERENCE","参考文档",4070,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fusing-superpowers\u002Freferences\u002Fcodex-tools.md",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fcopilot-tools.md",2193,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fusing-superpowers\u002Freferences\u002Fcopilot-tools.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fgemini-tools.md",1494,"https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fusing-superpowers\u002Freferences\u002Fgemini-tools.md",[75,88,112,131,160,191],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":83,"publishedAt":33},"01M719SWYD9RGS97HJ69PXWY62","add-new-agent","خطوات تفصيليّة لإضافة وكيل ذكاء اصطناعي جديد إلى منصّة Kalmeron من الفكرة إلى الإنتاج","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002FSKILL.md",[82],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[84,85,86,87],"add","add new agent","new","new agent",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":105,"publishedAt":33},"01M719SSKNBA7T5NS7V6DP0PX4","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[94,97,100],{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":98,"categoryName":99,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[106,107,86,29,108,109,110,28,111],"writing skills","writing","work","editing","deployment","Existing",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":120,"publishedAt":33},"01M719SRFDNKA3044QD3FYZ05R","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[118,119],{"categoryNo":98,"categoryName":99,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},[121,107,122,123,124,125,29,28,126,127,128,129,130],"writing plans","plans","code","requirements","you","for","task","multi","spec","multi-step task",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":143,"publishedAt":33},"01M719SPN5FM1JYJSR9DGJQPZ0","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[137,140],{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":141,"categoryName":142,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000032","设计师",[144,145,146,147,148,149,150,151,152,153,154,123,126,155,156,157,28,29,158,159],"web design","web design guidelines","web","design","guidelines","review","accessibility","ux","audit","compliance","check","vercel","interface","web interface guidelines","best practices","file",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":164,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":171,"publishedAt":33},"01M719SK11T05QYVPTWWYMYY5B","vitest","Set up Vitest testing in any project — detects project type (Cloudflare Workers, React, Node), generates vitest.config.ts, test setup, utilities, and sample tests. Also covers mocking patterns, coverage config, workspace setup, and Jest migration. Trigger with 'set up vitest', 'add tests', 'configure vitest', 'migrate from jest', 'vitest config', 'add unit tests', or 'testing setup'.","MIT","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvitest\u002FSKILL.md",[167,168],{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":169,"categoryName":170,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[162,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190],"cloudflare","cloudflare workers","config","node","sample","react","jest","migrate","configure","Utilities","up","testing","workspace setup","project","unit","SET","coverage","test setup","patterns",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":33},"01M719SGV9R1N88QWAB7Y925HD","verification-loops","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Requires running verification commands and confirming output before making any success claims. Evidence before assertions always.","https:\u002F\u002Fgithub.com\u002Fdahaliztupe-sketch\u002FKalmeron-Two\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverification-loops\u002FSKILL.md",[],[198,199,200,201,28,202,203,204,205,206,207,208,108,209,210,29],"loops","verification","verification loops","claim","assertions","prs","complete","evidence","running","commands","about","claims","output"]