[{"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-12 08:51:23",{"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,92,118,137,157,176],{"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":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":76,"publishedAt":91},"01M6CCF29DKTVDQWVM0EJREXTV","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[70,73],{"categoryNo":71,"categoryName":72,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":74,"categoryName":75,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[77,78,79,80,81,82,83,84,85,86,87,88,89,90],"webapp","webapp testing","testing","playwright","behavior","applications","logs","ui","browser","toolkit","debugging","web","screenshots","frontend","2026-11-11 15:11:14",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":100,"publishedAt":91},"01M6CCET439J7JD6CP2VJ1GWP1","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[99],{"categoryNo":74,"categoryName":75,"taxonomyType":21,"taxonomyTypeDesc":22},[101,102,103,88,104,105,90,106,84,107,108,109,110,111,112,113,114,115,116,117],"builder","artifacts builder","artifacts","web artifacts builder","Tailwind","Tools","file","state","state management","routing","component","react","components","css","management","single-file","use",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":91},"01M6CCDCQNA65GZ5ZMWH5FQPB3","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[125],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[127,128,129,86,130,131,132,133,134,103,135,136],"factory","theme factory","styling","html","landing","slides","fly","SET","generate","docs",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":150,"publishedAt":91},"01M6CCBRDWZJG6B82549AP9FNJ","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fslack-gif-creator\u002FSKILL.md",[144,147],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[151,152,153,117,154,155,156,106],"slack","slack gif creator","validation","knowledge","Animation","constraints",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":161,"sourceHtmlUrl":162,"categories":163,"keywords":167,"publishedAt":91},"01M6CCBF73X6J4W7434Z6FWSX9","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fskill-creator\u002FSKILL.md",[164],{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[168,169,33,170,171,172,154,173,174,175],"skill creator","update","specialized","integrations","tool","capabilities","create","workflows",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":180,"sourceHtmlUrl":181,"categories":182,"keywords":184,"publishedAt":91},"01M6CC58BZPCH6R5E46RME74TC","mcp-builder","Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node\u002FTypeScript (MCP SDK).","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fmcp-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fmcp-builder\u002FSKILL.md",[183],{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},[185,101,186,187,188,189,190,191,192,193,106,194,31,195,196,117,33,197,198,199],"mcp builder","MCP","sdk","model context protocol","fastmcp","protocol","typescript","python","llms","model","node","integrate","mcp servers","context","services"]