[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JF21MCDYMAC4C54ZPCEXWD":3,"skill-same:01M6JF21MCDYMAC4C54ZPCEXWD":89},{"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":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":74,"install":75,"resources":88},"01M6JF21MCDYMAC4C54ZPCEXWD","development-workflow",null,"Development lifecycle methodologies: TDD, debugging, code review, simplification, and spike prototyping.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fops\u002Fdevelopment-workflow\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"workflow","development workflow","development","code-review","coding-agents","prototyping","simplification","development lifecycle","coding","subagent","plan","lifecycle","code review","code","debugging","windows","linux","spike","review","macos","2026-11-10 10:12:30",false,"---\nname: development-workflow\ndescription: \"Development lifecycle methodologies: TDD, debugging, code review, simplification, and spike prototyping.\"\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [development, methodology, tdd, debugging, code-review, spike, simplification, workflow]\n    related_skills: [plan, subagent-driven-development, external-coding-agents]\n---\n\n# Development Workflow Methodologies\n\nA collection of proven development workflows covering the full lifecycle: from exploration (spikes) through implementation (TDD), verification (code review), cleanup (simplify), and debugging (systematic debugging).\n\n## Workflow Sequence\n\n```\nSpike ──→ TDD ──→ Code Review ──→ Simplify ──→ Deploy\n  │                                          ↑\n  └──→ Bug Found? ──→ Systematic Debugging ──┘\n```\n\nEach phase has an independent skill reference with exact commands, iron laws, and anti-pattern tables:\n\n### 1. Spike — Throwaway Experiments\nWhen to use: Validating feasibility before committing to a real build.\n- **references\u002Fspike.md** for the full workflow\n\n### 2. Test-Driven Development (TDD)\nWhen to use: ANY code change — features, bug fixes, refactoring.\n- RED: Write failing test first, watch it fail\n- GREEN: Write minimal code to pass\n- REFACTOR: Clean up while keeping tests green\n- **references\u002Ftest-driven-development.md** for the full TDD cycle\n\n### 3. Pre-Commit Code Review\nWhen to use: Before every commit after 2+ file edits.\n- Static security scan (secrets, injections, unsafe patterns)\n- Baseline-aware quality gates (tests, linting)\n- Independent reviewer subagent (fail-closed JSON verdict)\n- Auto-fix loop (max 2 cycles)\n- **references\u002Fgithub-code-review.md** for the full pipeline\n\n### 4. Simplify Code — Parallel Cleanup\nWhen to use: When the user says \"simplify\" or \"clean up my changes\".\n- Three parallel reviewers: Reuse, Quality, Efficiency\n- Aggregates findings, applies fixes, verifies with tests\n- **references\u002Fsimplify-code.md** for the full process\n\n### 5. Systematic Debugging\nWhen to use: ANY technical bug or test failure.\n- 4 phases: Root Cause Investigation → Pattern Analysis → Hypothesis Testing → Implementation\n- The Rule of Three: stop after 3 failed fixes, question the architecture\n- **references\u002Fsystematic-debugging.md** for the full methodology\n\n## Common Patterns Across All Workflows\n\n### The Iron Law\nEach methodology has a non-negotiable first principle:\n- TDD: \"NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST\"\n- Debugging: \"NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST\"\n- Code Review: \"No agent should verify its own work\"\n\n### Rationalizations vs Reality\nAll five skills include a table of common excuses and their counters.\n\n### Red Flags\nEach skill lists patterns that indicate you're skipping the process.\n\n### When NOT to Use Each\n- **Spike:** Skip when the answer is already known or the work is production path\n- **TDD:** Skip only for throwaway prototypes, generated code, or config files (ask the user first)\n- **Code Review:** Skip for docs-only or config-only changes\n- **Simplify:** Skip unless the user explicitly asks (it's token-heavy)\n- **Debugging:** Never skip — even simple bugs have root causes\n\n## Hermes Tool Integration\n\nAll workflows use the same Hermes tool primitives:\n\n```\nterminal(\"git diff\")              # Get changes\nterminal(\"pytest ...\")            # Run tests\nterminal(\"ruff check .\")          # Lint\nterminal(\"git log --oneline\")     # Check history\nsearch_files(\"error_string\")      # Find errors\nread_file(\"src\u002Fproblematic.py\")   # Read code\n```","# Development Workflow Methodologies\n\nA collection of proven development workflows covering the full lifecycle: from exploration (spikes) through implementation (TDD), verification (code review), cleanup (simplify), and debugging (systematic debugging).\n\n## Workflow Sequence\n\n```\nSpike ──→ TDD ──→ Code Review ──→ Simplify ──→ Deploy\n  │                                          ↑\n  └──→ Bug Found? ──→ Systematic Debugging ──┘\n```\n\nEach phase has an independent skill reference with exact commands, iron laws, and anti-pattern tables:\n\n### 1. Spike — Throwaway Experiments\nWhen to use: Validating feasibility before committing to a real build.\n- **references\u002Fspike.md** for the full workflow\n\n### 2. Test-Driven Development (TDD)\nWhen to use: ANY code change — features, bug fixes, refactoring.\n- RED: Write failing test first, watch it fail\n- GREEN: Write minimal code to pass\n- REFACTOR: Clean up while keeping tests green\n- **references\u002Ftest-driven-development.md** for the full TDD cycle\n\n### 3. Pre-Commit Code Review\nWhen to use: Before every commit after 2+ file edits.\n- Static security scan (secrets, injections, unsafe patterns)\n- Baseline-aware quality gates (tests, linting)\n- Independent reviewer subagent (fail-closed JSON verdict)\n- Auto-fix loop (max 2 cycles)\n- **references\u002Fgithub-code-review.md** for the full pipeline\n\n### 4. Simplify Code — Parallel Cleanup\nWhen to use: When the user says \"simplify\" or \"clean up my changes\".\n- Three parallel reviewers: Reuse, Quality, Efficiency\n- Aggregates findings, applies fixes, verifies with tests\n- **references\u002Fsimplify-code.md** for the full process\n\n### 5. Systematic Debugging\nWhen to use: ANY technical bug or test failure.\n- 4 phases: Root Cause Investigation → Pattern Analysis → Hypothesis Testing → Implementation\n- The Rule of Three: stop after 3 failed fixes, question the architecture\n- **references\u002Fsystematic-debugging.md** for the full methodology\n\n## Common Patterns Across All Workflows\n\n### The Iron Law\nEach methodology has a non-negotiable first principle:\n- TDD: \"NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST\"\n- Debugging: \"NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST\"\n- Code Review: \"No agent should verify its own work\"\n\n### Rationalizations vs Reality\nAll five skills include a table of common excuses and their counters.\n\n### Red Flags\nEach skill lists patterns that indicate you're skipping the process.\n\n### When NOT to Use Each\n- **Spike:** Skip when the answer is already known or the work is production path\n- **TDD:** Skip only for throwaway prototypes, generated code, or config files (ask the user first)\n- **Code Review:** Skip for docs-only or config-only changes\n- **Simplify:** Skip unless the user explicitly asks (it's token-heavy)\n- **Debugging:** Never skip — even simple bugs have root causes\n\n## Hermes Tool Integration\n\nAll workflows use the same Hermes tool primitives:\n\n```\nterminal(\"git diff\")              # Get changes\nterminal(\"pytest ...\")            # Run tests\nterminal(\"ruff check .\")          # Lint\nterminal(\"git log --oneline\")     # Check history\nsearch_files(\"error_string\")      # Find errors\nread_file(\"src\u002Fproblematic.py\")   # Read code\n```",{"name":5,"author":56,"license":14,"version":57,"metadata":58,"platforms":66,"description":7},"Hermes Agent","1.0.0",{"hermes":59},{"tags":60,"related_skills":63},[33,61,62,45,34,48,37,31],"methodology","tdd",[41,64,65],"subagent-driven-development","external-coding-agents",[47,50,46],"master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fops\u002Fdevelopment-workflow",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add S3YED\u002Fappie-kit --skill development-workflow",{"tool":81,"command":82},"bunx","bunx skills add S3YED\u002Fappie-kit --skill development-workflow",{"tool":84,"command":85},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill development-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fops\u002Fdevelopment-workflow\u002FSKILL.md",true,[],[90,122,155,179,207,226],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":103,"publishedAt":51},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[96,99,102],{"categoryNo":97,"categoryName":98,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":100,"categoryName":101,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":134,"publishedAt":51},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[128,131],{"categoryNo":129,"categoryName":130,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":132,"categoryName":133,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师",[135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":163,"publishedAt":51},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[161,162],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":132,"categoryName":133,"taxonomyType":28,"taxonomyTypeDesc":29},[136,164,140,165,166,167,142,168,169,170,171,172,173,41,40,174,175,176,177,178],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","edit","install","input","lock","source",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":189,"publishedAt":51},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[185,188],{"categoryNo":186,"categoryName":187,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[190,191,192,50,193,47,46,194,195,196,197,198,199,200,201,202,203,204,205,206],"deployment","vercel deployment","vercel","cli","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":214,"publishedAt":51},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[213],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[215,216,217,218,49,62,31,219,45,44,220,221,222,223,224,37,225],"workflows","quality","software","software quality workflows","commit","debugger","pre-commit","investigation","code simplification","user","for",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":237,"publishedAt":51},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[232,233,236],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":234,"categoryName":235,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[238,239,240,241,242,243,244,245,50,246,247,142,248,46,249,44,250,251,252,253],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","patterns","test-driven-development"]