[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7194554TNS0498F2M0NZQP4":3,"skill-same:01M7194554TNS0498F2M0NZQP4":76},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M7194554TNS0498F2M0NZQP4","requirements-spec",null,"Gather requirements and produce comprehensive implementation specifications through interactive clarification and codebase analysis. Use when:\n(1) User requests a new feature implementation plan\n(2) User wants to enrich or validate an existing sprint\u002Fimplementation document\n(3) User asks \"what do I need to build X\" or \"help me plan Y\"\n(4) User provides vague requirements needing clarification\n(5) User wants to identify reusable code before implementing\nProduces structured specification documents with blocking issues, domain models, API schemas, migration strategies, deliverables, and test plans.","vasceannie\u002Fslopgate","vasceannie","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20271133?v=4","01M718RGA8VV2EF22XJEMXVQ0Q","Travis Vasceannie","01M718RGB0GWSXBBZBN67Q6NHQ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Frequirements-spec\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"requirements","requirements spec","spec","sprint","documents","new","when","reusable code","implementation plan","vague","implementing","enrich","issues","code","strategies","feature implementation","specification","plan","api","analysis","2026-11-10 10:12:30",false,"---\nname: requirements-spec\ndescription: |\n  Gather requirements and produce comprehensive implementation specifications through interactive clarification and codebase analysis. Use when:\n  (1) User requests a new feature implementation plan\n  (2) User wants to enrich or validate an existing sprint\u002Fimplementation document\n  (3) User asks \"what do I need to build X\" or \"help me plan Y\"\n  (4) User provides vague requirements needing clarification\n  (5) User wants to identify reusable code before implementing\n  Produces structured specification documents with blocking issues, domain models, API schemas, migration strategies, deliverables, and test plans.\n---\n\n# Requirements & Specifications\n\nProduce implementation-ready specification documents through iterative clarification and codebase validation.\n\n## Workflow\n\n```\n┌─────────────────┐    ┌──────────────────┐    ┌─────────────────┐\n│  1. CLARIFY     │───▶│  2. ANALYZE      │───▶│  3. SYNTHESIZE  │\n│  Requirements   │    │  Codebase        │    │  Specification  │\n└─────────────────┘    └──────────────────┘    └─────────────────┘\n     │                       │                       │\n     ▼                       ▼                       ▼\n  AskUserQuestion      Semantic + Grep         Markdown Document\n  (2-4 questions)      (find reusable code)   (Sprint README format)\n```\n\n## Phase 1: Clarify Requirements\n\nUse `AskUserQuestion` with 2-4 focused questions per round. Stop when sufficient clarity exists.\n\n### Question Categories\n\n| Category | When Missing | Example |\n|----------|--------------|---------|\n| **Scope** | Feature boundaries unclear | \"Backend only, full-stack, or client-only?\" |\n| **Actors** | No roles\u002Fpermissions mentioned | \"Who can perform this? Role restrictions?\" |\n| **Data** | Entities without relationships | \"How does [A] relate to [B]?\" |\n| **Integration** | Standalone vs connected unclear | \"Does this integrate with existing features?\" |\n| **Constraints** | NFRs not specified | \"Performance, security, or compatibility requirements?\" |\n| **Priority** | MVP vs full feature unclear | \"What's minimum viable vs nice-to-have?\" |\n\n### Clarification Patterns\n\n**Ambiguous scope**: Ask about boundaries and priority breakdown.\n\n**Missing actors**: Ask about access control and ownership scope (user\u002Fworkspace\u002Fglobal).\n\n**Unclear data model**: Ask about relationships and lifecycle (archive\u002Fdelete behavior).\n\n**Integration uncertainty**: Ask about existing feature touchpoints and API contracts.\n\n## Phase 2: Analyze Codebase\n\nFind reusable patterns, existing implementations, and integration points using parallel searches.\n\n### Search Strategy\n\n```python\n# Semantic search (similar patterns)\nfind_symbol(name_path_pattern=\"*Service\", depth=1)\nfind_symbol(name_path_pattern=\"*Repository\", depth=1)\n\n# Keyword search (specific implementations)\nsearch_for_pattern(substring_pattern=\"@dataclass\", paths_include_glob=\"**\u002Fdomain\u002F**\")\n\n# Reference search (usage patterns)\nfind_referencing_symbols(name_path=\"UnitOfWork\", relative_path=\"domain\u002Fports\u002F\")\n```\n\n### What to Find\n\n| Category | Search Target | Purpose |\n|----------|---------------|---------|\n| **Domain** | Entities, value objects | Reuse field patterns, validation |\n| **Services** | Application services | Follow established DI, error handling |\n| **Repositories** | Port definitions | Match existing CRUD patterns |\n| **API** | Proto messages, RPCs | Consistent API design |\n| **Tests** | Fixtures, parameterized tests | Reuse test infrastructure |\n| **Migrations** | Alembic scripts | Follow migration conventions |\n\n### Validation Checklist\n\n- [ ] No duplicate implementations exist\n- [ ] Identified base classes\u002Fprotocols to extend\n- [ ] Found related features for integration\n- [ ] Located test fixtures to reuse\n- [ ] Checked for conflicting naming\n\n## Phase 3: Synthesize Specification\n\nGenerate specification following `references\u002Foutput-template.md`. Key sections:\n\n1. **Header** — Sprint name, size, owner, prerequisites, phase\n2. **Open Issues** — Blocking issues, design gaps, prerequisite verification\n3. **Validation Status** — What exists vs needs implementation\n4. **Objective** — 2-3 sentence goal\n5. **Key Decisions** — Table with rationale\n6. **What Already Exists** — Reusable assets from analysis\n7. **Scope** — Task breakdown with effort (S\u002FM\u002FL\u002FXL)\n8. **Domain Model** — Entity definitions with code\n9. **API Schema** — Proto\u002FgRPC or REST additions\n10. **Migration Strategy** — Phased rollout with risks\n11. **Deliverables** — Checkbox lists by layer\n12. **Test Strategy** — Fixtures, parameterized tests, cases\n13. **Quality Gates** — Exit criteria\n\n### Effort Guide\n\n| Size | Scope |\n|------|-------|\n| **S** | Single file, straightforward (add field, simple function) |\n| **M** | Multiple files, clear pattern (new entity, repo method) |\n| **L** | Cross-cutting, some complexity (new service, gRPC mixin) |\n| **XL** | Architectural, high complexity (new subsystem, major refactor) |\n\n## Tool Usage\n\n| Tool | Phase | Purpose |\n|------|-------|---------|\n| `AskUserQuestion` | 1 | Gather requirements |\n| `find_symbol` | 2 | Semantic code search |\n| `search_for_pattern` | 2 | Regex code search |\n| `find_referencing_symbols` | 2 | Find usage patterns |\n| `get_symbols_overview` | 2 | Understand file structure |\n| `Write` | 3 | Generate specification |\n\n### Guardrails\n\n- `think_about_collected_information` — After Phase 2\n- `think_about_task_adherence` — Before writing spec\n- `think_about_whether_you_are_done` — After document complete\n\n## References\n\n- `references\u002Foutput-template.md` — Full specification document template\n- `references\u002Fquestion-bank.md` — Comprehensive clarification questions\n","# Requirements & Specifications\n\nProduce implementation-ready specification documents through iterative clarification and codebase validation.\n\n## Workflow\n\n```\n┌─────────────────┐    ┌──────────────────┐    ┌─────────────────┐\n│  1. CLARIFY     │───▶│  2. ANALYZE      │───▶│  3. SYNTHESIZE  │\n│  Requirements   │    │  Codebase        │    │  Specification  │\n└─────────────────┘    └──────────────────┘    └─────────────────┘\n     │                       │                       │\n     ▼                       ▼                       ▼\n  AskUserQuestion      Semantic + Grep         Markdown Document\n  (2-4 questions)      (find reusable code)   (Sprint README format)\n```\n\n## Phase 1: Clarify Requirements\n\nUse `AskUserQuestion` with 2-4 focused questions per round. Stop when sufficient clarity exists.\n\n### Question Categories\n\n| Category | When Missing | Example |\n|----------|--------------|---------|\n| **Scope** | Feature boundaries unclear | \"Backend only, full-stack, or client-only?\" |\n| **Actors** | No roles\u002Fpermissions mentioned | \"Who can perform this? Role restrictions?\" |\n| **Data** | Entities without relationships | \"How does [A] relate to [B]?\" |\n| **Integration** | Standalone vs connected unclear | \"Does this integrate with existing features?\" |\n| **Constraints** | NFRs not specified | \"Performance, security, or compatibility requirements?\" |\n| **Priority** | MVP vs full feature unclear | \"What's minimum viable vs nice-to-have?\" |\n\n### Clarification Patterns\n\n**Ambiguous scope**: Ask about boundaries and priority breakdown.\n\n**Missing actors**: Ask about access control and ownership scope (user\u002Fworkspace\u002Fglobal).\n\n**Unclear data model**: Ask about relationships and lifecycle (archive\u002Fdelete behavior).\n\n**Integration uncertainty**: Ask about existing feature touchpoints and API contracts.\n\n## Phase 2: Analyze Codebase\n\nFind reusable patterns, existing implementations, and integration points using parallel searches.\n\n### Search Strategy\n\n```python\n# Semantic search (similar patterns)\nfind_symbol(name_path_pattern=\"*Service\", depth=1)\nfind_symbol(name_path_pattern=\"*Repository\", depth=1)\n\n# Keyword search (specific implementations)\nsearch_for_pattern(substring_pattern=\"@dataclass\", paths_include_glob=\"**\u002Fdomain\u002F**\")\n\n# Reference search (usage patterns)\nfind_referencing_symbols(name_path=\"UnitOfWork\", relative_path=\"domain\u002Fports\u002F\")\n```\n\n### What to Find\n\n| Category | Search Target | Purpose |\n|----------|---------------|---------|\n| **Domain** | Entities, value objects | Reuse field patterns, validation |\n| **Services** | Application services | Follow established DI, error handling |\n| **Repositories** | Port definitions | Match existing CRUD patterns |\n| **API** | Proto messages, RPCs | Consistent API design |\n| **Tests** | Fixtures, parameterized tests | Reuse test infrastructure |\n| **Migrations** | Alembic scripts | Follow migration conventions |\n\n### Validation Checklist\n\n- [ ] No duplicate implementations exist\n- [ ] Identified base classes\u002Fprotocols to extend\n- [ ] Found related features for integration\n- [ ] Located test fixtures to reuse\n- [ ] Checked for conflicting naming\n\n## Phase 3: Synthesize Specification\n\nGenerate specification following `references\u002Foutput-template.md`. Key sections:\n\n1. **Header** — Sprint name, size, owner, prerequisites, phase\n2. **Open Issues** — Blocking issues, design gaps, prerequisite verification\n3. **Validation Status** — What exists vs needs implementation\n4. **Objective** — 2-3 sentence goal\n5. **Key Decisions** — Table with rationale\n6. **What Already Exists** — Reusable assets from analysis\n7. **Scope** — Task breakdown with effort (S\u002FM\u002FL\u002FXL)\n8. **Domain Model** — Entity definitions with code\n9. **API Schema** — Proto\u002FgRPC or REST additions\n10. **Migration Strategy** — Phased rollout with risks\n11. **Deliverables** — Checkbox lists by layer\n12. **Test Strategy** — Fixtures, parameterized tests, cases\n13. **Quality Gates** — Exit criteria\n\n### Effort Guide\n\n| Size | Scope |\n|------|-------|\n| **S** | Single file, straightforward (add field, simple function) |\n| **M** | Multiple files, clear pattern (new entity, repo method) |\n| **L** | Cross-cutting, some complexity (new service, gRPC mixin) |\n| **XL** | Architectural, high complexity (new subsystem, major refactor) |\n\n## Tool Usage\n\n| Tool | Phase | Purpose |\n|------|-------|---------|\n| `AskUserQuestion` | 1 | Gather requirements |\n| `find_symbol` | 2 | Semantic code search |\n| `search_for_pattern` | 2 | Regex code search |\n| `find_referencing_symbols` | 2 | Find usage patterns |\n| `get_symbols_overview` | 2 | Understand file structure |\n| `Write` | 3 | Generate specification |\n\n### Guardrails\n\n- `think_about_collected_information` — After Phase 2\n- `think_about_task_adherence` — Before writing spec\n- `think_about_whether_you_are_done` — After document complete\n\n## References\n\n- `references\u002Foutput-template.md` — Full specification document template\n- `references\u002Fquestion-bank.md` — Comprehensive clarification questions\n",{"name":5,"description":7},"master","5fab8004af1390aa17b3447f2780766c8bf2482c","bundle\u002Fshared\u002Fskills\u002Frequirements-spec",0,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate","https:\u002F\u002Fgithub.com\u002Fvasceannie","thingswithstuff.io","2026-11-12 20:22:46",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add vasceannie\u002Fslopgate --skill requirements-spec",{"tool":58,"command":59},"bunx","bunx skills add vasceannie\u002Fslopgate --skill requirements-spec",{"tool":61,"command":62},"pnpm","pnpm dlx skills add vasceannie\u002Fslopgate --skill requirements-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Frequirements-spec\u002FSKILL.md",true,[66,72],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Foutput-template.md","REFERENCE","参考文档",7868,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Frequirements-spec\u002Freferences\u002Foutput-template.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fquestion-bank.md",7001,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Frequirements-spec\u002Freferences\u002Fquestion-bank.md",[77,107,133,170,195,215],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":88,"publishedAt":39},"01M71951JDWCYMS8GDC2C7395D","type-strictness","Enforce strict type compliance by eliminating `Any` types and `# type: ignore` comments. Use when:\n(1) Editing code that contains `Any` as a type annotation\n(2) Code has `# type: ignore` or `# pyright: ignore` comments\n(3) User requests type fixes or type strictness enforcement\n(4) Importing from untyped third-party libraries\n(5) User asks to \"fix types\", \"remove Any\", or \"add proper typing\"\n(6) Pyrefly or mypy reports type errors that need resolution\n(7) Code review reveals weak typing patterns\nFollows hierarchical resolution: codebase inference → type stubs → library inspection → type guards → casting (last resort).","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Ftype-strictness\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[89,90,91,92,93,94,95,96,97,25,32,98,99,100,101,102,103,104,105,106],"type","type strictness","typing","types","remove","code review","fix","errors","inspection","review","reports","libraries","casting","pyrefly","mypy","pyright","library","patterns",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":117,"publishedAt":39},"01M7194XGBQXSE7Y5BZ4K5CSTK","slopgate-test-extender","Extend Python test suites with parametrization, fixture reuse, and quality enforcement. Use when asked to add tests, extend existing tests, improve test coverage, consolidate duplicate tests, fix test quality issues, or when Slopgate reports untested-production-code, missing test references, or coverage gaps. Triggers on requests like \"add tests for X\", \"extend these tests\", \"parametrize tests\", \"consolidate tests\", \"fix test quality\", \"improve test coverage\", \"write tests for this function\", \"test this module\", \"behavior tests\", \"integration tests\", \"missing tests\", \"coverage holes\", \"untested code\", or when a hook denies with test-related findings.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-test-extender\u002FSKILL.md",[113,114],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":115,"categoryName":116,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000008","测试与质量",[118,119,120,121,122,95,31,123,124,125,126,127,25,32,128,129,99,130,131,132],"slopgate test extender","test","coverage","fixture","testing","write tests","improve","only","cleanup","loop","candidate","consolidate","references","opencode","orchestrator",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":154,"publishedAt":39},"01M7194RMVQS5YJJ4ZEFXX20VS","slopgate-intelligent-coding-patterns","Pattern-selection playbook for agents editing code with complex branching, stateful parsers\u002Fworkflows, duplicated skeletons, policy checks, or ordered transforms. Load before refactoring if\u002Felif dispatch chains, boolean-flag state machines, repeated validation predicates, parallel provider\u002Flanguage implementations, or regex\u002Fcontent transformation pipelines. Also load when asked to \"apply a design pattern\", \"which pattern should I use here\", \"refactor this switch statement\", \"replace if-elif chain\", \"state machine pattern\", \"strategy pattern\", \"template method\", \"pipeline pattern\", \"specification pattern\", \"dispatch table\", \"guard clause refactor\", \"reduce cyclomatic complexity\", or when Slopgate fires PY-CODE-014, PY-CODE-017, PY-CODE-018, QUALITY-LINT-001, or PY-QUALITY-010. Use with behavior-locking tests and avoid pattern theater for simple one-off code.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-intelligent-coding-patterns\u002FSKILL.md",[139,140,143,146,151],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":141,"categoryName":142,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":144,"categoryName":145,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":152,"categoryName":153,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000032","设计师",[155,156,106,157,158,159,160,161,162,163,164,165,166,125,126,167,168,25,169,32],"coding patterns","slopgate intelligent coding patterns","coding","stateful","complexity","branch","which","chain","parsers","pipeline","selection","design","utility","workflows","reduce",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":178,"publishedAt":39},"01M7194KTXBM85GB0W7JKFQD55","slopgate-hygiene-orchestrator","Orchestrate systematic elimination of linter warnings and errors across Python, TypeScript, and Rust codebases. Use when asked to \"clean up lints\", \"fix all warnings\", \"run hygiene\", \"eliminate type errors\", \"orchestrate code quality fixes\", \"fix lint errors\", \"resolve quality gate failures\", \"pass CI checks\", \"reduce tech debt\", \"refactor to pass hooks\", or when a Slopgate hook denies with QUALITY-LINT-001, PY-CODE-017, PY-CODE-018, or any collector finding. This skill coordinates multiple code-hygiene-enforcer agents working in parallel on non-conflicting file groupings, tracks progress persistently via JSON exports, and loops until all issues are resolved. CRITICAL: Never run linters directly—always use `slopgate lint check` as the primary gate, discover project-specific tools from config files, and export findings to JSON for tracking.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-hygiene-orchestrator\u002FSKILL.md",[176,177],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":144,"categoryName":145,"taxonomyType":86,"taxonomyTypeDesc":87},[179,180,132,181,95,182,183,184,185,186,126,169,187,188,189,190,191,192,193,194],"slopgate hygiene orchestrator","hygiene","project","ci","local","clean","never run","files","run","lint check","systematic","config","typescript","debt","quality-gates","hook",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":203,"publishedAt":39},"01M7194G50FZYXXT8VNK360RPA","slopgate-code-smell-utility-locator","Autoactivate when code-smell hooks or reviews mention feature envy, thin wrappers, duplicate helpers, duplicate code,\nscattered helpers, builders\u002Ffactories\u002Fconfig\u002Fconstants\u002Fdataclass reuse, PY-CODE-012, PY-CODE-013, QUALITY-LINT-001,\nor repeated slopgate code-quality denials. Also load when asked to \"find existing helpers\", \"consolidate utilities\",\n\"search for duplicate code\", \"where is this already implemented\", \"reuse existing logic\", \"don't duplicate this\",\n\"find similar functions\", \"utility inventory\", \"code smell radar\", or before adding new helpers\u002Fwrappers so agents can\nfind existing shared utilities and consolidate instead of duplicating.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-code-smell-utility-locator\u002FSKILL.md",[201,202],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},[167,204,32,205,120,206,207,208,209,125,24,25,210,129,131,211,212,190,213,214],"slopgate code smell utility locator","shared","reviews","inventory","search","hooks","coordination","radar","code-quality","Utilities","dataclass",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":223,"publishedAt":39},"01M7194AWG1Q37F9756H4SFDH9","slopgate-code-hygiene-refactor","Recovery playbook for Slopgate and project quality failures. Load after hook\u002Flint denials such as PY-CODE-017 flat sibling modules, PY-CODE-018 oversized modules, QUALITY-LINT-001 post-edit quality backstops, PY-QUALITY-010 magic numbers \u002F repeated literals, PY-CODE-012\u002FPY-CODE-013 smell findings, type-suppression bans, duplicate helpers, or repeated hygiene retry loops. Also load when asked to \"refactor this module\", \"split this file\", \"extract a class\", \"reduce complexity\", \"fix god class\", \"flatten module hierarchy\", \"move code to a package\", \"extract helpers\", \"consolidate duplicates\", \"replace magic numbers with constants\", or when a hook blocks an edit with structural complaints. Focuses on preserving public APIs while refactoring toward packages, cohesive modules, typed seams, and focused tests.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-code-hygiene-refactor\u002FSKILL.md",[221,222],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},[224,225,32,226,180,227,159,228,229,181,230,207,231,95,125,167,25,169,210,129],"code hygiene","slopgate code hygiene refactor","refactor","modules","duplicates","retry","move","structural"]