[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CCC17PRZ3J9WTH67NEXB0G":3,"skill-same:01M6CCC17PRZ3J9WTH67NEXB0G":61},{"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":23,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6CCC17PRZ3J9WTH67NEXB0G","software-architecture",null,"Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.","Gabriellmaia01\u002Fneuro-dose-assist","Gabriellmaia01","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F135177180?v=4","01M6CBRZEZC8G5C400AG3SPFNH","Gabriel","01M6CBRZK8MB7DWW0B4C82TV2G",0,"MIT","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fsoftware-architecture\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33],"architecture","software architecture","design","development","code","design architecture","analyze","quality","write","guide","2026-11-10 10:12:30",false,"---\nname: software-architecture\ndescription: Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.\n---\n\n# Software Architecture Development Skill\n\nThis skill provides guidance for quality focused software development and architecture. It is based on Clean Architecture and Domain Driven Design principles.\n\n## Code Style Rules\n\n### General Principles\n\n- **Early return pattern**: Always use early returns when possible, over nested conditions for better readability\n- Avoid code duplication through creation of reusable functions and modules\n- Decompose long (more than 80 lines of code) components and functions into multiple smaller components and functions. If they cannot be used anywhere else, keep it in the same file. But if file longer than 200 lines of code, it should be split into multiple files.\n- Use arrow functions instead of function declarations when possible\n\n### Best Practices\n\n#### Library-First Approach\n\n- **ALWAYS search for existing solutions before writing custom code**\n  - Check npm for existing libraries that solve the problem\n  - Evaluate existing services\u002FSaaS solutions\n  - Consider third-party APIs for common functionality\n- Use libraries instead of writing your own utils or helpers. For example, use `cockatiel` instead of writing your own retry logic.\n- **When custom code IS justified:**\n  - Specific business logic unique to the domain\n  - Performance-critical paths with special requirements\n  - When external dependencies would be overkill\n  - Security-sensitive code requiring full control\n  - When existing solutions don't meet requirements after thorough evaluation\n\n#### Architecture and Design\n\n- **Clean Architecture & DDD Principles:**\n  - Follow domain-driven design and ubiquitous language\n  - Separate domain entities from infrastructure concerns\n  - Keep business logic independent of frameworks\n  - Define use cases clearly and keep them isolated\n- **Naming Conventions:**\n  - **AVOID** generic names: `utils`, `helpers`, `common`, `shared`\n  - **USE** domain-specific names: `OrderCalculator`, `UserAuthenticator`, `InvoiceGenerator`\n  - Follow bounded context naming patterns\n  - Each module should have a single, clear purpose\n- **Separation of Concerns:**\n  - Do NOT mix business logic with UI components\n  - Keep database queries out of controllers\n  - Maintain clear boundaries between contexts\n  - Ensure proper separation of responsibilities\n\n#### Anti-Patterns to Avoid\n\n- **NIH (Not Invented Here) Syndrome:**\n  - Don't build custom auth when Auth0\u002FSupabase exists\n  - Don't write custom state management instead of using Redux\u002FZustand\n  - Don't create custom form validation instead of using established libraries\n- **Poor Architectural Choices:**\n  - Mixing business logic with UI components\n  - Database queries directly in controllers\n  - Lack of clear separation of concerns\n- **Generic Naming Anti-Patterns:**\n  - `utils.js` with 50 unrelated functions\n  - `helpers\u002Fmisc.js` as a dumping ground\n  - `common\u002Fshared.js` with unclear purpose\n- Remember: Every line of custom code is a liability that needs maintenance, testing, and documentation\n\n#### Code Quality\n\n- Proper error handling with typed catch blocks\n- Break down complex logic into smaller, reusable functions\n- Avoid deep nesting (max 3 levels)\n- Keep functions focused and under 50 lines when possible\n- Keep files focused and under 200 lines of code when possible\n","# Software Architecture Development Skill\n\nThis skill provides guidance for quality focused software development and architecture. It is based on Clean Architecture and Domain Driven Design principles.\n\n## Code Style Rules\n\n### General Principles\n\n- **Early return pattern**: Always use early returns when possible, over nested conditions for better readability\n- Avoid code duplication through creation of reusable functions and modules\n- Decompose long (more than 80 lines of code) components and functions into multiple smaller components and functions. If they cannot be used anywhere else, keep it in the same file. But if file longer than 200 lines of code, it should be split into multiple files.\n- Use arrow functions instead of function declarations when possible\n\n### Best Practices\n\n#### Library-First Approach\n\n- **ALWAYS search for existing solutions before writing custom code**\n  - Check npm for existing libraries that solve the problem\n  - Evaluate existing services\u002FSaaS solutions\n  - Consider third-party APIs for common functionality\n- Use libraries instead of writing your own utils or helpers. For example, use `cockatiel` instead of writing your own retry logic.\n- **When custom code IS justified:**\n  - Specific business logic unique to the domain\n  - Performance-critical paths with special requirements\n  - When external dependencies would be overkill\n  - Security-sensitive code requiring full control\n  - When existing solutions don't meet requirements after thorough evaluation\n\n#### Architecture and Design\n\n- **Clean Architecture & DDD Principles:**\n  - Follow domain-driven design and ubiquitous language\n  - Separate domain entities from infrastructure concerns\n  - Keep business logic independent of frameworks\n  - Define use cases clearly and keep them isolated\n- **Naming Conventions:**\n  - **AVOID** generic names: `utils`, `helpers`, `common`, `shared`\n  - **USE** domain-specific names: `OrderCalculator`, `UserAuthenticator`, `InvoiceGenerator`\n  - Follow bounded context naming patterns\n  - Each module should have a single, clear purpose\n- **Separation of Concerns:**\n  - Do NOT mix business logic with UI components\n  - Keep database queries out of controllers\n  - Maintain clear boundaries between contexts\n  - Ensure proper separation of responsibilities\n\n#### Anti-Patterns to Avoid\n\n- **NIH (Not Invented Here) Syndrome:**\n  - Don't build custom auth when Auth0\u002FSupabase exists\n  - Don't write custom state management instead of using Redux\u002FZustand\n  - Don't create custom form validation instead of using established libraries\n- **Poor Architectural Choices:**\n  - Mixing business logic with UI components\n  - Database queries directly in controllers\n  - Lack of clear separation of concerns\n- **Generic Naming Anti-Patterns:**\n  - `utils.js` with 50 unrelated functions\n  - `helpers\u002Fmisc.js` as a dumping ground\n  - `common\u002Fshared.js` with unclear purpose\n- Remember: Every line of custom code is a liability that needs maintenance, testing, and documentation\n\n#### Code Quality\n\n- Proper error handling with typed catch blocks\n- Break down complex logic into smaller, reusable functions\n- Avoid deep nesting (max 3 levels)\n- Keep functions focused and under 50 lines when possible\n- Keep files focused and under 200 lines of code when possible\n",{"name":5,"description":7},"main","eac60cc6e0b6baa2a05a765a851fb10638f4e733",".agent\u002Fskills\u002Fskills\u002Fsoftware-architecture","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist","https:\u002F\u002Fgithub.com\u002FGabriellmaia01","https:\u002F\u002Fportfolio-bice-theta-81.vercel.app\u002F","💻 Desenvolvimento De Software_\r\n\r\n⚙️ Engenharia De Software\r\n","2026-11-10 08:31:19",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add Gabriellmaia01\u002Fneuro-dose-assist --skill software-architecture",{"tool":53,"command":54},"bunx","bunx skills add Gabriellmaia01\u002Fneuro-dose-assist --skill software-architecture",{"tool":56,"command":57},"pnpm","pnpm dlx skills add Gabriellmaia01\u002Fneuro-dose-assist --skill software-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fsoftware-architecture\u002FSKILL.md",true,[],[62,85,115,135,146,167],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":71,"publishedAt":34},"01M6CCFWA9JJ23708FSKK1QNBW","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[68],{"categoryNo":69,"categoryName":70,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[72,73,74,75,28,76,77,78,79,80,81,82,83,84],"zapier make patterns","writing","workflow","automation","apache","how","automate","integrations","business","use","simplicity","power","complexity",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":97,"publishedAt":34},"01M6CCFSBPM49S618W7G4NHH13","Cross-Site Scripting and HTML Injection Testing","This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection vulnerabilities\", \"steal cookies via XSS\", or \"bypass content security policies\". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fxss-html-injection\u002FSKILL.md",[91,94],{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114],"injection","scripting","html","site","Cross Site Scripting and HTML Injection Testing","testing","html injection testing","cookies","applications","xss","exploit","content","web","test","vulnerabilities","user","security",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":130,"publishedAt":34},"01M6CCFJ9XTPXHTE4JR06WY475","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[121,122,125],{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[73,131,132,133,134,81],"writing skills","deployment","work","editing",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":143,"publishedAt":34},"01M6CCFG98EMZZ43D1CPZZZ54E","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[141,142],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},[73,144,145,28,81],"writing plans","spec",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":34},"01M6CCFDPACVC9ZM8TN63MGBP5","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fworkflow-automation\u002FSKILL.md",[152],{"categoryNo":69,"categoryName":70,"taxonomyType":21,"taxonomyTypeDesc":22},[154,75,74,155,156,157,158,159,76,160,161,162,163,164,165,166],"Workflow Automation","network","ai agents","accessibility","workflows","infrastructure","flow","Production","execution","inngest","parallel","orchestrator","resume",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":34},"01M6CCFB0KAB0PPNV38XQPX6YX","WordPress Penetration Testing","This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vulnerabilities\", or \"use WPScan\". It provides comprehensive WordPress security assessment methodologies.","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fwordpress-penetration-testing\u002FSKILL.md",[173],{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},[103,169,175,176,114,112,177,178,113,81,108,179,180],"penetration testing","wordpress","assessment","plugins","pentest","security assessment"]