[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VJE4W3YK0YVAAV7RV11VT":3,"skill-same:01M77VJE4W3YK0YVAAV7RV11VT":52},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77VJE4W3YK0YVAAV7RV11VT","python-design-patterns",null,"Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing between inheritance and composition for a new class hierarchy, or when a codebase is becoming hard to test because of entangled I\u002FO and business logic.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-design-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing between inheritance and composition for a new class hierarchy, or when a codebase is becoming hard to test because of entangled I\u002FO and business logic.\"\n---\n# Python Design Patterns\n\nWrite maintainable Python code using fundamental design principles. These patterns help you build systems that are easy to understand, test, and modify.\n\n## When to Use This Skill\n\n- Designing new components or services\n- Refactoring complex or tangled code\n- Deciding whether to create an abstraction\n- Choosing between inheritance and composition\n- Evaluating code complexity and coupling\n- Planning modular architectures\n\n## Core Concepts\n\n### 1. KISS (Keep It Simple)\n\nChoose the simplest solution that works. Complexity must be justified by concrete requirements.\n\n### 2. Single Responsibility (SRP)\n\nEach unit should have one reason to change. Separate concerns into focused components.\n\n### 3. Composition Over Inheritance\n\nBuild behavior by combining objects, not extending classes.\n\n### 4. Rule of Three\n\nWait until you have three instances before abstracting. Duplication is often better than premature abstraction.\n\n## Quick Start\n\n```python\n# Simple beats clever\n# Instead of a factory\u002Fregistry pattern:\nFORMATTERS = {\"json\": JsonFormatter, \"csv\": CsvFormatter}\n\ndef get_formatter(name: str) -> Formatter:\n    return FORMATTERS[name]()\n```\n\n## Detailed patterns and worked examples\n\nDetailed pattern documentation lives in `references\u002Fdetails.md`. Read that file when the navigation tier above is insufficient.\n\n## Best Practices Summary\n\n1. **Keep it simple** - Choose the simplest solution that works\n2. **Single responsibility** - Each unit has one reason to change\n3. **Separate concerns** - Distinct layers with clear purposes\n4. **Compose, don't inherit** - Combine objects for flexibility\n5. **Rule of three** - Wait before abstracting\n6. **Keep functions small** - 20-50 lines (varies by complexity), one purpose\n7. **Inject dependencies** - Constructor injection for testability\n8. **Delete before abstracting** - Remove dead code, then consider patterns\n9. **Test each layer** - Isolated tests for each concern\n10. **Explicit over clever** - Readable code beats elegant code\n\n## Troubleshooting\n\n**A class is growing and seems to have multiple responsibilities, but splitting it feels wrong.**\nApply the \"reason to change\" test: list every change that could require editing this class. If the list has items from different domains (e.g., HTTP parsing AND business rules AND formatting), split it. If all changes stem from the same domain concern, the class may be appropriately sized.\n\n**Injecting all dependencies through the constructor is producing constructors with 7+ parameters.**\nThis is a sign of too many responsibilities in one class, not a problem with dependency injection. Split the class into smaller units first, then each constructor naturally becomes smaller.\n\n**Composition is producing deeply nested wrapper objects that are hard to trace.**\nKeep the composition shallow (2-3 levels). If wrapping is the only mechanism, consider whether a Protocol-based approach or simple function composition would be cleaner than a chain of decorator objects.\n\n**The rule of three says not to abstract yet, but the duplication is causing bugs when one copy is updated but not the other.**\nDuplication that diverges in dangerous ways should be abstracted sooner. The rule of three is a heuristic, not a law. If the copies are already diverging incorrectly, extract immediately and add a test that exercises the shared behavior.\n\n**A service layer is importing from the API layer, breaking the dependency direction.**\nThis is a layering violation. The service layer must not import from handlers. Introduce a shared types\u002Fmodels layer that both can import from, keeping the dependency arrow pointing downward (API → Service → Repository).\n\n## Related Skills\n\n- [python-testing-patterns](..\u002Fpython-testing-patterns\u002FSKILL.md) — Test each layer in isolation using the dependency injection structure established here\n- [python-project-setup](..\u002Fpython-project-setup\u002FSKILL.md) — Set up project structure and tooling that enforces layer boundaries from the start\n","# Python Design Patterns\n\nWrite maintainable Python code using fundamental design principles. These patterns help you build systems that are easy to understand, test, and modify.\n\n## When to Use This Skill\n\n- Designing new components or services\n- Refactoring complex or tangled code\n- Deciding whether to create an abstraction\n- Choosing between inheritance and composition\n- Evaluating code complexity and coupling\n- Planning modular architectures\n\n## Core Concepts\n\n### 1. KISS (Keep It Simple)\n\nChoose the simplest solution that works. Complexity must be justified by concrete requirements.\n\n### 2. Single Responsibility (SRP)\n\nEach unit should have one reason to change. Separate concerns into focused components.\n\n### 3. Composition Over Inheritance\n\nBuild behavior by combining objects, not extending classes.\n\n### 4. Rule of Three\n\nWait until you have three instances before abstracting. Duplication is often better than premature abstraction.\n\n## Quick Start\n\n```python\n# Simple beats clever\n# Instead of a factory\u002Fregistry pattern:\nFORMATTERS = {\"json\": JsonFormatter, \"csv\": CsvFormatter}\n\ndef get_formatter(name: str) -> Formatter:\n    return FORMATTERS[name]()\n```\n\n## Detailed patterns and worked examples\n\nDetailed pattern documentation lives in `references\u002Fdetails.md`. Read that file when the navigation tier above is insufficient.\n\n## Best Practices Summary\n\n1. **Keep it simple** - Choose the simplest solution that works\n2. **Single responsibility** - Each unit has one reason to change\n3. **Separate concerns** - Distinct layers with clear purposes\n4. **Compose, don't inherit** - Combine objects for flexibility\n5. **Rule of three** - Wait before abstracting\n6. **Keep functions small** - 20-50 lines (varies by complexity), one purpose\n7. **Inject dependencies** - Constructor injection for testability\n8. **Delete before abstracting** - Remove dead code, then consider patterns\n9. **Test each layer** - Isolated tests for each concern\n10. **Explicit over clever** - Readable code beats elegant code\n\n## Troubleshooting\n\n**A class is growing and seems to have multiple responsibilities, but splitting it feels wrong.**\nApply the \"reason to change\" test: list every change that could require editing this class. If the list has items from different domains (e.g., HTTP parsing AND business rules AND formatting), split it. If all changes stem from the same domain concern, the class may be appropriately sized.\n\n**Injecting all dependencies through the constructor is producing constructors with 7+ parameters.**\nThis is a sign of too many responsibilities in one class, not a problem with dependency injection. Split the class into smaller units first, then each constructor naturally becomes smaller.\n\n**Composition is producing deeply nested wrapper objects that are hard to trace.**\nKeep the composition shallow (2-3 levels). If wrapping is the only mechanism, consider whether a Protocol-based approach or simple function composition would be cleaner than a chain of decorator objects.\n\n**The rule of three says not to abstract yet, but the duplication is causing bugs when one copy is updated but not the other.**\nDuplication that diverges in dangerous ways should be abstracted sooner. The rule of three is a heuristic, not a law. If the copies are already diverging incorrectly, extract immediately and add a test that exercises the shared behavior.\n\n**A service layer is importing from the API layer, breaking the dependency direction.**\nThis is a layering violation. The service layer must not import from handlers. Introduce a shared types\u002Fmodels layer that both can import from, keeping the dependency arrow pointing downward (API → Service → Repository).\n\n## Related Skills\n\n- [python-testing-patterns](..\u002Fpython-testing-patterns\u002FSKILL.md) — Test each layer in isolation using the dependency injection structure established here\n- [python-project-setup](..\u002Fpython-project-setup\u002FSKILL.md) — Set up project structure and tooling that enforces layer boundaries from the start\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fpython-design-patterns",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill python-design-patterns",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill python-design-patterns",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill python-design-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-design-patterns\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fdetails.md","REFERENCE","参考文档",10996,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-design-patterns\u002Freferences\u002Fdetails.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]