[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74FV6SN237QJ9GK55DTWR2Q":3,"skill-same:01M74FV6SN237QJ9GK55DTWR2Q":61},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":13,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M74FV6SN237QJ9GK55DTWR2Q","writing-plans",null,"Write implementation plans: bite-sized tasks, paths, code.","lzy18001500226\u002FMoSim","lzy18001500226","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F152623587?v=4","01M71ZMEX36NK05B642131DEEK","01M71ZMEXSMX72KPVNJ572G0CM",0,"MIT","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: writing-plans\ndescription: \"Write implementation plans: bite-sized tasks, paths, code.\"\nversion: 1.1.0\nauthor: Hermes Agent (adapted from obra\u002Fsuperpowers)\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [planning, design, implementation, workflow, documentation]\n    related_skills: [subagent-driven-development, test-driven-development, requesting-code-review]\n---\n\n# Writing Implementation Plans\n\n## Overview\n\nWrite comprehensive implementation plans assuming the implementer has zero context for the codebase and questionable taste. Document everything they need: which files to touch, complete code, testing commands, docs to check, how to verify. Give them bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.\n\nAssume the implementer is a skilled developer but knows almost nothing about the toolset or problem domain. Assume they don't know good test design very well.\n\n**Core principle:** A good plan makes implementation obvious. If someone has to guess, the plan is incomplete.\n\n## When to Use\n\n**Always use before:**\n- Implementing multi-step features\n- Breaking down complex requirements\n- Delegating to subagents via subagent-driven-development\n\n**Don't skip when:**\n- Feature seems simple (assumptions cause bugs)\n- You plan to implement it yourself (future you needs guidance)\n- Working alone (documentation matters)\n\n## Bite-Sized Task Granularity\n\n**Each task = 2-5 minutes of focused work.**\n\nEvery step is one action:\n- \"Write the failing test\" — step\n- \"Run it to make sure it fails\" — step\n- \"Implement the minimal code to make the test pass\" — step\n- \"Run the tests and make sure they pass\" — step\n- \"Commit\" — step\n\n**Too big:**\n```markdown\n### Task 1: Build authentication system\n[50 lines of code across 5 files]\n```\n\n**Right size:**\n```markdown\n### Task 1: Create User model with email field\n[10 lines, 1 file]\n\n### Task 2: Add password hash field to User\n[8 lines, 1 file]\n\n### Task 3: Create password hashing utility\n[15 lines, 1 file]\n```\n\n## Plan Document Structure\n\n### Header (Required)\n\nEvery plan MUST start with:\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Hermes:** Use subagent-driven-development skill to implement this plan task-by-task.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies\u002Flibraries]\n\n---\n```\n\n### Task Structure\n\nEach task follows this format:\n\n````markdown\n### Task N: [Descriptive Name]\n\n**Objective:** What this task accomplishes (one sentence)\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Fnew_file.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:45-67` (line numbers if known)\n- Test: `tests\u002Fpath\u002Fto\u002Ftest_file.py`\n\n**Step 1: Write failing test**\n\n```python\ndef test_specific_behavior():\n    result = function(input)\n    assert result == expected\n```\n\n**Step 2: Run test to verify failure**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -v`\nExpected: FAIL — \"function not defined\"\n\n**Step 3: Write minimal implementation**\n\n```python\ndef function(input):\n    return expected\n```\n\n**Step 4: Run test to verify pass**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -v`\nExpected: PASS\n\n**Step 5: Commit**\n\n```bash\ngit add tests\u002Fpath\u002Ftest.py src\u002Fpath\u002Ffile.py\ngit commit -m \"feat: add specific feature\"\n```\n````\n\n## Writing Process\n\n### Step 1: Understand Requirements\n\nRead and understand:\n- Feature requirements\n- Design documents or user description\n- Acceptance criteria\n- Constraints\n\n### Step 2: Explore the Codebase\n\nUse Hermes tools to understand the project:\n\n```python\n# Understand project structure\nsearch_files(\"*.py\", target=\"files\", path=\"src\u002F\")\n\n# Look at similar features\nsearch_files(\"similar_pattern\", path=\"src\u002F\", file_glob=\"*.py\")\n\n# Check existing tests\nsearch_files(\"*.py\", target=\"files\", path=\"tests\u002F\")\n\n# Read key files\nread_file(\"src\u002Fapp.py\")\n```\n\n### Step 3: Design Approach\n\nDecide:\n- Architecture pattern\n- File organization\n- Dependencies needed\n- Testing strategy\n\n### Step 4: Write Tasks\n\nCreate tasks in order:\n1. Setup\u002Finfrastructure\n2. Core functionality (TDD for each)\n3. Edge cases\n4. Integration\n5. Cleanup\u002Fdocumentation\n\n### Step 5: Add Complete Details\n\nFor each task, include:\n- **Exact file paths** (not \"the config file\" but `src\u002Fconfig\u002Fsettings.py`)\n- **Complete code examples** (not \"add validation\" but the actual code)\n- **Exact commands** with expected output\n- **Verification steps** that prove the task works\n\n### Step 6: Review the Plan\n\nCheck:\n- [ ] Tasks are sequential and logical\n- [ ] Each task is bite-sized (2-5 min)\n- [ ] File paths are exact\n- [ ] Code examples are complete (copy-pasteable)\n- [ ] Commands are exact with expected output\n- [ ] No missing context\n- [ ] DRY, YAGNI, TDD principles applied\n\n### Step 7: Save the Plan\n\n```bash\nmkdir -p docs\u002Fplans\n# Save plan to docs\u002Fplans\u002FYYYY-MM-DD-feature-name.md\ngit add docs\u002Fplans\u002F\ngit commit -m \"docs: add implementation plan for [feature]\"\n```\n\n## Principles\n\n### DRY (Don't Repeat Yourself)\n\n**Bad:** Copy-paste validation in 3 places\n**Good:** Extract validation function, use everywhere\n\n### YAGNI (You Aren't Gonna Need It)\n\n**Bad:** Add \"flexibility\" for future requirements\n**Good:** Implement only what's needed now\n\n```python\n# Bad — YAGNI violation\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n        self.preferences = {}  # Not needed yet!\n        self.metadata = {}     # Not needed yet!\n\n# Good — YAGNI\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n```\n\n### TDD (Test-Driven Development)\n\nEvery task that produces code should include the full TDD cycle:\n1. Write failing test\n2. Run to verify failure\n3. Write minimal code\n4. Run to verify pass\n\nSee `test-driven-development` skill for details.\n\n### Frequent Commits\n\nCommit after every task:\n```bash\ngit add [files]\ngit commit -m \"type: description\"\n```\n\n## Common Mistakes\n\n### Vague Tasks\n\n**Bad:** \"Add authentication\"\n**Good:** \"Create User model with email and password_hash fields\"\n\n### Incomplete Code\n\n**Bad:** \"Step 1: Add validation function\"\n**Good:** \"Step 1: Add validation function\" followed by the complete function code\n\n### Missing Verification\n\n**Bad:** \"Step 3: Test it works\"\n**Good:** \"Step 3: Run `pytest tests\u002Ftest_auth.py -v`, expected: 3 passed\"\n\n### Missing File Paths\n\n**Bad:** \"Create the model file\"\n**Good:** \"Create: `src\u002Fmodels\u002Fuser.py`\"\n\n## Execution Handoff\n\nAfter saving the plan, offer the execution approach:\n\n**\"Plan complete and saved. Ready to execute using subagent-driven-development — I'll dispatch a fresh subagent per task with two-stage review (spec compliance then code quality). Shall I proceed?\"**\n\nWhen executing, use the `subagent-driven-development` skill:\n- Fresh `delegate_task` per task with full context\n- Spec compliance review after each task\n- Code quality review after spec passes\n- Proceed only when both reviews approve\n\n## Remember\n\n```\nBite-sized tasks (2-5 min each)\nExact file paths\nComplete code (copy-pasteable)\nExact commands with expected output\nVerification steps\nDRY, YAGNI, TDD\nFrequent commits\n```\n\n**A good plan makes implementation obvious.**\n","# Writing Implementation Plans\n\n## Overview\n\nWrite comprehensive implementation plans assuming the implementer has zero context for the codebase and questionable taste. Document everything they need: which files to touch, complete code, testing commands, docs to check, how to verify. Give them bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.\n\nAssume the implementer is a skilled developer but knows almost nothing about the toolset or problem domain. Assume they don't know good test design very well.\n\n**Core principle:** A good plan makes implementation obvious. If someone has to guess, the plan is incomplete.\n\n## When to Use\n\n**Always use before:**\n- Implementing multi-step features\n- Breaking down complex requirements\n- Delegating to subagents via subagent-driven-development\n\n**Don't skip when:**\n- Feature seems simple (assumptions cause bugs)\n- You plan to implement it yourself (future you needs guidance)\n- Working alone (documentation matters)\n\n## Bite-Sized Task Granularity\n\n**Each task = 2-5 minutes of focused work.**\n\nEvery step is one action:\n- \"Write the failing test\" — step\n- \"Run it to make sure it fails\" — step\n- \"Implement the minimal code to make the test pass\" — step\n- \"Run the tests and make sure they pass\" — step\n- \"Commit\" — step\n\n**Too big:**\n```markdown\n### Task 1: Build authentication system\n[50 lines of code across 5 files]\n```\n\n**Right size:**\n```markdown\n### Task 1: Create User model with email field\n[10 lines, 1 file]\n\n### Task 2: Add password hash field to User\n[8 lines, 1 file]\n\n### Task 3: Create password hashing utility\n[15 lines, 1 file]\n```\n\n## Plan Document Structure\n\n### Header (Required)\n\nEvery plan MUST start with:\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Hermes:** Use subagent-driven-development skill to implement this plan task-by-task.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies\u002Flibraries]\n\n---\n```\n\n### Task Structure\n\nEach task follows this format:\n\n````markdown\n### Task N: [Descriptive Name]\n\n**Objective:** What this task accomplishes (one sentence)\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Fnew_file.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:45-67` (line numbers if known)\n- Test: `tests\u002Fpath\u002Fto\u002Ftest_file.py`\n\n**Step 1: Write failing test**\n\n```python\ndef test_specific_behavior():\n    result = function(input)\n    assert result == expected\n```\n\n**Step 2: Run test to verify failure**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -v`\nExpected: FAIL — \"function not defined\"\n\n**Step 3: Write minimal implementation**\n\n```python\ndef function(input):\n    return expected\n```\n\n**Step 4: Run test to verify pass**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_specific_behavior -v`\nExpected: PASS\n\n**Step 5: Commit**\n\n```bash\ngit add tests\u002Fpath\u002Ftest.py src\u002Fpath\u002Ffile.py\ngit commit -m \"feat: add specific feature\"\n```\n````\n\n## Writing Process\n\n### Step 1: Understand Requirements\n\nRead and understand:\n- Feature requirements\n- Design documents or user description\n- Acceptance criteria\n- Constraints\n\n### Step 2: Explore the Codebase\n\nUse Hermes tools to understand the project:\n\n```python\n# Understand project structure\nsearch_files(\"*.py\", target=\"files\", path=\"src\u002F\")\n\n# Look at similar features\nsearch_files(\"similar_pattern\", path=\"src\u002F\", file_glob=\"*.py\")\n\n# Check existing tests\nsearch_files(\"*.py\", target=\"files\", path=\"tests\u002F\")\n\n# Read key files\nread_file(\"src\u002Fapp.py\")\n```\n\n### Step 3: Design Approach\n\nDecide:\n- Architecture pattern\n- File organization\n- Dependencies needed\n- Testing strategy\n\n### Step 4: Write Tasks\n\nCreate tasks in order:\n1. Setup\u002Finfrastructure\n2. Core functionality (TDD for each)\n3. Edge cases\n4. Integration\n5. Cleanup\u002Fdocumentation\n\n### Step 5: Add Complete Details\n\nFor each task, include:\n- **Exact file paths** (not \"the config file\" but `src\u002Fconfig\u002Fsettings.py`)\n- **Complete code examples** (not \"add validation\" but the actual code)\n- **Exact commands** with expected output\n- **Verification steps** that prove the task works\n\n### Step 6: Review the Plan\n\nCheck:\n- [ ] Tasks are sequential and logical\n- [ ] Each task is bite-sized (2-5 min)\n- [ ] File paths are exact\n- [ ] Code examples are complete (copy-pasteable)\n- [ ] Commands are exact with expected output\n- [ ] No missing context\n- [ ] DRY, YAGNI, TDD principles applied\n\n### Step 7: Save the Plan\n\n```bash\nmkdir -p docs\u002Fplans\n# Save plan to docs\u002Fplans\u002FYYYY-MM-DD-feature-name.md\ngit add docs\u002Fplans\u002F\ngit commit -m \"docs: add implementation plan for [feature]\"\n```\n\n## Principles\n\n### DRY (Don't Repeat Yourself)\n\n**Bad:** Copy-paste validation in 3 places\n**Good:** Extract validation function, use everywhere\n\n### YAGNI (You Aren't Gonna Need It)\n\n**Bad:** Add \"flexibility\" for future requirements\n**Good:** Implement only what's needed now\n\n```python\n# Bad — YAGNI violation\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n        self.preferences = {}  # Not needed yet!\n        self.metadata = {}     # Not needed yet!\n\n# Good — YAGNI\nclass User:\n    def __init__(self, name, email):\n        self.name = name\n        self.email = email\n```\n\n### TDD (Test-Driven Development)\n\nEvery task that produces code should include the full TDD cycle:\n1. Write failing test\n2. Run to verify failure\n3. Write minimal code\n4. Run to verify pass\n\nSee `test-driven-development` skill for details.\n\n### Frequent Commits\n\nCommit after every task:\n```bash\ngit add [files]\ngit commit -m \"type: description\"\n```\n\n## Common Mistakes\n\n### Vague Tasks\n\n**Bad:** \"Add authentication\"\n**Good:** \"Create User model with email and password_hash fields\"\n\n### Incomplete Code\n\n**Bad:** \"Step 1: Add validation function\"\n**Good:** \"Step 1: Add validation function\" followed by the complete function code\n\n### Missing Verification\n\n**Bad:** \"Step 3: Test it works\"\n**Good:** \"Step 3: Run `pytest tests\u002Ftest_auth.py -v`, expected: 3 passed\"\n\n### Missing File Paths\n\n**Bad:** \"Create the model file\"\n**Good:** \"Create: `src\u002Fmodels\u002Fuser.py`\"\n\n## Execution Handoff\n\nAfter saving the plan, offer the execution approach:\n\n**\"Plan complete and saved. Ready to execute using subagent-driven-development — I'll dispatch a fresh subagent per task with two-stage review (spec compliance then code quality). Shall I proceed?\"**\n\nWhen executing, use the `subagent-driven-development` skill:\n- Fresh `delegate_task` per task with full context\n- Spec compliance review after each task\n- Code quality review after spec passes\n- Proceed only when both reviews approve\n\n## Remember\n\n```\nBite-sized tasks (2-5 min each)\nExact file paths\nComplete code (copy-pasteable)\nExact commands with expected output\nVerification steps\nDRY, YAGNI, TDD\nFrequent commits\n```\n\n**A good plan makes implementation obvious.**\n",{"name":5,"author":23,"license":14,"version":24,"metadata":25,"platforms":37,"description":7},"Hermes Agent (adapted from obra\u002Fsuperpowers)","1.1.0",{"hermes":26},{"tags":27,"related_skills":33},[28,29,30,31,32],"planning","design","implementation","workflow","documentation",[34,35,36],"subagent-driven-development","test-driven-development","requesting-code-review",[38,39,40],"linux","macos","windows","main","e0ec177d00f087cb04e90206b2f7d3aa2f5a1350","References\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fwriting-plans","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim","https:\u002F\u002Fgithub.com\u002Flzy18001500226","2026-08-31 23:29:00",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add lzy18001500226\u002FMoSim --skill writing-plans",{"tool":53,"command":54},"bunx","bunx skills add lzy18001500226\u002FMoSim --skill writing-plans",{"tool":56,"command":57},"pnpm","pnpm dlx skills add lzy18001500226\u002FMoSim --skill writing-plans","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",true,[],[62,72,80,88,96,104],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":71},"01M78RK6JGRPTD3TDSMTQWDQ9P","skill-installer","Install Codex skills into $CODEX_HOME\u002Fskills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":71},"01M78RK29KVRDQXSMVZX1GQTJN","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":71},"01M78RJPF3210Y5DA9VJ6JMMG6","openai-docs","Use for Codex models\u002Fpricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs\u002Fproducts and ChatGPT Work. Also use for model choice\u002Fmigration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat\u002FWork\u002FCodex comparisons. Do not use for generic app\u002Fsoftware tasks that merely mention Codex.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FSKILL.md",[],[],{"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":66,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":71},"01M78RJH7X67C5AY8ZVS7RQNWJ","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":71},"01M78RBBAYMJ6T3ZMAYHCFM6G7","skill-creator-cc","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":112},"01M76VV9V2R9FZTVGMJZV7Y996","prd-writing-guide","Write complete, unambiguous PRDs that development teams can implement without guesswork. Includes requirement discovery framework, structured documentation methodology, completeness checklists, and common pitfall avoidance. Use when: writing new PRDs, reviewing PRD drafts, validating requirement completeness, preparing for engineering handoff. Triggers: 'write PRD', '写PRD', '产品需求文档', '需求文档', '需求规格', '需求评审', '完善需求', 'create requirements doc', 'product requirements', 'feature spec', 'requirements document'. Anti-triggers: 'technical design doc', 'architecture design', 'implementation plan', 'API design', '架构设计', '技术方案', '实现方案', '接口设计'.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FSKILL.md",[],[],"2026-11-12 13:55:43"]