[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7536XY5ANT51TQWJS7CBYMJ":3,"skill-same:01M7536XY5ANT51TQWJS7CBYMJ":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":45,"commitSha":46,"skillDirectory":47,"forksCount":13,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M7536XY5ANT51TQWJS7CBYMJ","squirrel",null,"Full-cycle AI coding skill: plans, builds, tests, lints, fixes bugs, and writes production-grade docs. Auto-detects project state and adapts its 8-phase pipeline.","ASoudy\u002FAGS","ASoudy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40639702?v=4","01M74G5NTCW8MWDNRTAF303PA1","01M74G5NTZXSE6T0GZR5BCB6V0",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002FAGAS\u002Fskills\u002Fsquirrel\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: squirrel\ndescription: \"Full-cycle AI coding skill: plans, builds, tests, lints, fixes bugs, and writes production-grade docs. Auto-detects project state and adapts its 8-phase pipeline.\"\ncategory: development\nrisk: safe\nsource: community\nsource_repo: flyingsquirrel0419\u002Fsquirrel-skill\nsource_type: community\nlicense: \"Apache-2.0\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fflyingsquirrel0419\u002Fsquirrel-skill\u002Fblob\u002Fmain\u002FLICENSE\"\ndate_added: \"2026-04-29\"\nauthor: flying_squirrel__\ntags: [development, testing, planning, code-review, documentation, ci-cd]\ntools: [claude, cursor, codex, antigravity, gemini, windsurf, opencode, copilot]\n---\n\n# Squirrel — Full-Cycle Software Development Skill\n\n## Overview\n\nSquirrel is a full-cycle AI coding skill that works across 9 AI coding agents. It auto-detects project state (greenfield, in-progress, or mature) and adapts its 8-phase engineering pipeline accordingly. Instead of a one-size-fits-all workflow, it figures out where the project actually is and jumps in at exactly the right point.\n\n## When to Use This Skill\n\n- Use when starting a new project from scratch (greenfield)\n- Use when improving an existing codebase (in-progress or mature)\n- Use when fixing bugs, adding features, or refactoring\n- Use when adding tests, linting, or CI\u002FCD to a project\n- Use when writing production-grade documentation\n- Use when the user says \"build me\", \"fix this\", \"squirrel this project\", or any multi-step development task\n\n## How It Works\n\n### Step 0: Detect Mode\n\nSquirrel classifies the project directory:\n\n| Signal | Mode | Entry Point |\n|--------|------|-------------|\n| Empty directory | Greenfield | All 8 phases from scratch |\n| Source files, no tests\u002Fdocs | In-Progress | Audit first, then improve |\n| Source + tests + CI + README | Mature | Targeted improvements |\n| \"fix this bug \u002F add feature\" | Targeted | Scoped work only |\n\n### The 8-Phase Pipeline\n\n1. **Discover** — Understand the project (audit existing code or gather requirements)\n2. **Plan** — Concrete task list with dependencies and done-criteria\n3. **Build** — Write or modify code (parallel sub-agents when supported)\n4. **Test** — Run existing tests, write new ones, 70%+ coverage target\n5. **Bug Hunt** — Static analysis + manual review\n6. **Polish** — Lint, format, type check, remove dead code\n7. **Document** — README + inline docs (update existing, don't overwrite)\n8. **Ship** — Final checklist: tests green, no secrets, CI configured\n\n### Failure Recovery (3-Strike Rule)\n\n1. **Strike 1:** Fix the specific error. Run tests. Move on.\n2. **Strike 2:** Re-read the code. Try a different approach.\n3. **Strike 3:** STOP. Revert. Document what failed. Ask the user.\n\n## Examples\n\n### Example 1: Build a REST API\n\n```text\n> build me a REST API for a todo app with TypeScript and Express\n```\n\nSquirrel auto-detects greenfield mode and runs all 8 phases.\n\n### Example 2: Fix a bug\n\n```text\n> fix this bug in src\u002Fauth\u002Flogin.py\n```\n\nSquirrel enters targeted mode — abbreviated audit, scoped fix, verify.\n\n### Example 3: Improve existing project\n\n```text\n> squirrel this project — add tests, fix lint errors, write README\n```\n\nSquirrel audits the existing codebase, then applies phases 4-8.\n\n## Best Practices\n\n- Respects existing code — matches naming conventions, test framework, import style, and architecture\n- Reads 2-3 similar files before writing a new one\n- Never suppresses type errors with `as any` or `@ts-ignore`\n- Never deletes failing tests to \"pass\"\n- Never leaves code in a broken state\n\n## Platform Compatibility\n\nSquirrel works on: Claude Code, Codex, Cursor, Antigravity, Gemini CLI, GitHub Copilot, Windsurf, OpenCode, Aider (9 total).\n\nInstall with:\n\n```bash\n# Universal installer\nnpx skills add flyingsquirrel0419\u002Fsquirrel-skill\n\n```\n\n## Limitations\n\n- Does not replace environment-specific validation or expert review\n- CI\u002FCD templates are starting points, not drop-in guarantees\n- Parallel sub-agent execution depends on platform support\n\n## Related Skills\n\n- `@brainstorming` - For planning before implementation\n- `@test-driven-development` - For TDD-oriented workflows\n- `@systematic-debugging` - For methodical problem-solving\n","# Squirrel — Full-Cycle Software Development Skill\n\n## Overview\n\nSquirrel is a full-cycle AI coding skill that works across 9 AI coding agents. It auto-detects project state (greenfield, in-progress, or mature) and adapts its 8-phase engineering pipeline accordingly. Instead of a one-size-fits-all workflow, it figures out where the project actually is and jumps in at exactly the right point.\n\n## When to Use This Skill\n\n- Use when starting a new project from scratch (greenfield)\n- Use when improving an existing codebase (in-progress or mature)\n- Use when fixing bugs, adding features, or refactoring\n- Use when adding tests, linting, or CI\u002FCD to a project\n- Use when writing production-grade documentation\n- Use when the user says \"build me\", \"fix this\", \"squirrel this project\", or any multi-step development task\n\n## How It Works\n\n### Step 0: Detect Mode\n\nSquirrel classifies the project directory:\n\n| Signal | Mode | Entry Point |\n|--------|------|-------------|\n| Empty directory | Greenfield | All 8 phases from scratch |\n| Source files, no tests\u002Fdocs | In-Progress | Audit first, then improve |\n| Source + tests + CI + README | Mature | Targeted improvements |\n| \"fix this bug \u002F add feature\" | Targeted | Scoped work only |\n\n### The 8-Phase Pipeline\n\n1. **Discover** — Understand the project (audit existing code or gather requirements)\n2. **Plan** — Concrete task list with dependencies and done-criteria\n3. **Build** — Write or modify code (parallel sub-agents when supported)\n4. **Test** — Run existing tests, write new ones, 70%+ coverage target\n5. **Bug Hunt** — Static analysis + manual review\n6. **Polish** — Lint, format, type check, remove dead code\n7. **Document** — README + inline docs (update existing, don't overwrite)\n8. **Ship** — Final checklist: tests green, no secrets, CI configured\n\n### Failure Recovery (3-Strike Rule)\n\n1. **Strike 1:** Fix the specific error. Run tests. Move on.\n2. **Strike 2:** Re-read the code. Try a different approach.\n3. **Strike 3:** STOP. Revert. Document what failed. Ask the user.\n\n## Examples\n\n### Example 1: Build a REST API\n\n```text\n> build me a REST API for a todo app with TypeScript and Express\n```\n\nSquirrel auto-detects greenfield mode and runs all 8 phases.\n\n### Example 2: Fix a bug\n\n```text\n> fix this bug in src\u002Fauth\u002Flogin.py\n```\n\nSquirrel enters targeted mode — abbreviated audit, scoped fix, verify.\n\n### Example 3: Improve existing project\n\n```text\n> squirrel this project — add tests, fix lint errors, write README\n```\n\nSquirrel audits the existing codebase, then applies phases 4-8.\n\n## Best Practices\n\n- Respects existing code — matches naming conventions, test framework, import style, and architecture\n- Reads 2-3 similar files before writing a new one\n- Never suppresses type errors with `as any` or `@ts-ignore`\n- Never deletes failing tests to \"pass\"\n- Never leaves code in a broken state\n\n## Platform Compatibility\n\nSquirrel works on: Claude Code, Codex, Cursor, Antigravity, Gemini CLI, GitHub Copilot, Windsurf, OpenCode, Aider (9 total).\n\nInstall with:\n\n```bash\n# Universal installer\nnpx skills add flyingsquirrel0419\u002Fsquirrel-skill\n\n```\n\n## Limitations\n\n- Does not replace environment-specific validation or expert review\n- CI\u002FCD templates are starting points, not drop-in guarantees\n- Parallel sub-agent execution depends on platform support\n\n## Related Skills\n\n- `@brainstorming` - For planning before implementation\n- `@test-driven-development` - For TDD-oriented workflows\n- `@systematic-debugging` - For methodical problem-solving\n",{"name":5,"risk":23,"tags":24,"tools":31,"author":40,"source":41,"license":14,"category":25,"date_added":42,"description":7,"source_repo":43,"source_type":41,"license_source":44},"safe",[25,26,27,28,29,30],"development","testing","planning","code-review","documentation","ci-cd",[32,33,34,35,36,37,38,39],"claude","cursor","codex","antigravity","gemini","windsurf","opencode","copilot","flying_squirrel__","community","2026-04-29","flyingsquirrel0419\u002Fsquirrel-skill","https:\u002F\u002Fgithub.com\u002Fflyingsquirrel0419\u002Fsquirrel-skill\u002Fblob\u002Fmain\u002FLICENSE","main","cd1d94757d590093507ef8ac26299eab8bc20478","AGAS\u002Fskills\u002Fsquirrel","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add ASoudy\u002FAGS --skill squirrel",{"tool":57,"command":58},"bunx","bunx skills add ASoudy\u002FAGS --skill squirrel",{"tool":60,"command":61},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill squirrel","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002FAGAS\u002Fskills\u002Fsquirrel\u002FSKILL.md",true,[],[66,74,81,88,95,102],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M756BTEVC407T0QR8S420JWD","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", or \"typographic scale\". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","MIT","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M756B4RYF2CB17C33X6ZJQT5","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"usability testing\". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M756ANVFT0T6BAPV6Y93EPR6","traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftraction-eos\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M756A7NZZMNJN9KZ33QGFHV6","top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"premium website\", \"portfolio site\", \"scroll animations\", \"Awwwards quality\", \"brand experience\", \"cinematic web design\", \"parallax storytelling\", or \"agency-quality site\". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftop-design\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M7569J5G1NXM3RR194D52SGB","system-design","Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions \"system design\", \"scale this\", \"high availability\", \"rate limiter\", \"design a URL shortener\", \"system design interview\", \"capacity planning\", or \"distributed architecture\". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fsystem-design\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M75691MJKE6PBA1EC398EKQT","storybrand-messaging","Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions \"brand message\", \"website copy\", \"elevator pitch\", \"one-liner\", \"messaging isnt resonating\", \"brand script\", \"StoryBrand framework\", or \"customer as hero\". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fstorybrand-messaging\u002FSKILL.md",[],[]]