[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMECGZAB2QB2K1B231WRG0":3,"skill-same:01M7EMECGZAB2QB2K1B231WRG0":59},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7EMECGZAB2QB2K1B231WRG0","domain-modeling",null,"Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.","Sales16\u002Fclaude-skills","Sales16","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145076606?v=4","01M7EME51GJ05X3WWQXFTG60PE","Eduardo Sales","01M7EME525598B2W3JQVR8X922",0,"MIT","https:\u002F\u002Fgithub.com\u002FSales16\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: domain-modeling\ndescription: Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.\n---\n\n# Domain Modeling\n\nConverse sempre em português nesta sessão. Isso vale só para a interação com o usuário: não mexa no idioma de CONTEXT.md, ADRs ou qualquer arquivo já existente no repo, esses são compartilhados e ficam como estão, mesmo se já estiverem em inglês. Ao criar um arquivo novo, pode escrever em inglês, seguindo o padrão que já existe no projeto.\n\nActively build and sharpen the project's domain model as you design. This is the *active* discipline: challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely *reading* `CONTEXT.md` for vocabulary is not this skill: that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)\n\n## File structure\n\nMost repos have a single context:\n\n```\n\u002F\n├── CONTEXT.md\n├── docs\u002F\n│   └── adr\u002F\n│       ├── 0001-event-sourced-orders.md\n│       └── 0002-postgres-for-write-model.md\n└── src\u002F\n```\n\nIf a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── CONTEXT-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── CONTEXT.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── CONTEXT.md\n│       └── docs\u002Fadr\u002F\n```\n\nCreate files lazily: only when you have something to write. If no `CONTEXT.md` exists, create one when the first term is resolved. If no `docs\u002Fadr\u002F` exists, create it when the first ADR is needed.\n\n## During the session\n\n### Challenge against the glossary\n\nWhen the user uses a term that conflicts with the existing language in `CONTEXT.md`, call it out immediately. \"Your glossary defines 'cancellation' as X, but you seem to mean Y. Which is it?\"\n\n### Sharpen fuzzy language\n\nWhen the user uses vague or overloaded terms, propose a precise canonical term. \"You're saying 'account': do you mean the Customer or the User? Those are different things.\"\n\n### Discuss concrete scenarios\n\nWhen domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.\n\n### Cross-reference with code\n\nWhen the user states how something works, check whether the code agrees. If you find a contradiction, surface it: \"Your code cancels entire Orders, but you just said partial cancellation is possible. Which is right?\"\n\n### Update CONTEXT.md inline\n\nWhen a term is resolved, update `CONTEXT.md` right there. Don't batch these up: capture them as they happen. Use the format in [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\n`CONTEXT.md` should be totally devoid of implementation details. Do not treat `CONTEXT.md` as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.\n\n### Offer ADRs sparingly\n\nOnly offer to create an ADR when all three are true:\n\n1. **Hard to reverse**: the cost of changing your mind later is meaningful\n2. **Surprising without context**: a future reader will wonder \"why did they do it this way?\"\n3. **The result of a real trade-off**: there were genuine alternatives and you picked one for specific reasons\n\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](.\u002FADR-FORMAT.md).\n\n## How to ask\n\nEvery question this skill puts to the user (a term conflict, a fuzzy term, a scenario, a code contradiction, which context a topic belongs to, whether to write an ADR) goes through the structured question tool (`AskUserQuestion` in Claude Code), never as chat text. Follow the rules in the `grilling` skill's \"How to ask\" section: one question per call, 2-4 options with trade-offs in the descriptions, recommended option first with ` (Recomendado)`, `multiSelect: true` when choices are not exclusive.\n\nExamples:\n\n- Term conflict: options are the glossary meaning, the meaning the user seems to use, and \"são dois termos diferentes\".\n- Fuzzy term: options are the candidate canonical terms.\n- ADR offer: \"Criar ADR\" (with the proposed title in the description) and \"Pular\".\n","# Domain Modeling\n\nConverse sempre em português nesta sessão. Isso vale só para a interação com o usuário: não mexa no idioma de CONTEXT.md, ADRs ou qualquer arquivo já existente no repo, esses são compartilhados e ficam como estão, mesmo se já estiverem em inglês. Ao criar um arquivo novo, pode escrever em inglês, seguindo o padrão que já existe no projeto.\n\nActively build and sharpen the project's domain model as you design. This is the *active* discipline: challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely *reading* `CONTEXT.md` for vocabulary is not this skill: that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)\n\n## File structure\n\nMost repos have a single context:\n\n```\n\u002F\n├── CONTEXT.md\n├── docs\u002F\n│   └── adr\u002F\n│       ├── 0001-event-sourced-orders.md\n│       └── 0002-postgres-for-write-model.md\n└── src\u002F\n```\n\nIf a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── CONTEXT-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── CONTEXT.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── CONTEXT.md\n│       └── docs\u002Fadr\u002F\n```\n\nCreate files lazily: only when you have something to write. If no `CONTEXT.md` exists, create one when the first term is resolved. If no `docs\u002Fadr\u002F` exists, create it when the first ADR is needed.\n\n## During the session\n\n### Challenge against the glossary\n\nWhen the user uses a term that conflicts with the existing language in `CONTEXT.md`, call it out immediately. \"Your glossary defines 'cancellation' as X, but you seem to mean Y. Which is it?\"\n\n### Sharpen fuzzy language\n\nWhen the user uses vague or overloaded terms, propose a precise canonical term. \"You're saying 'account': do you mean the Customer or the User? Those are different things.\"\n\n### Discuss concrete scenarios\n\nWhen domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.\n\n### Cross-reference with code\n\nWhen the user states how something works, check whether the code agrees. If you find a contradiction, surface it: \"Your code cancels entire Orders, but you just said partial cancellation is possible. Which is right?\"\n\n### Update CONTEXT.md inline\n\nWhen a term is resolved, update `CONTEXT.md` right there. Don't batch these up: capture them as they happen. Use the format in [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\n`CONTEXT.md` should be totally devoid of implementation details. Do not treat `CONTEXT.md` as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.\n\n### Offer ADRs sparingly\n\nOnly offer to create an ADR when all three are true:\n\n1. **Hard to reverse**: the cost of changing your mind later is meaningful\n2. **Surprising without context**: a future reader will wonder \"why did they do it this way?\"\n3. **The result of a real trade-off**: there were genuine alternatives and you picked one for specific reasons\n\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](.\u002FADR-FORMAT.md).\n\n## How to ask\n\nEvery question this skill puts to the user (a term conflict, a fuzzy term, a scenario, a code contradiction, which context a topic belongs to, whether to write an ADR) goes through the structured question tool (`AskUserQuestion` in Claude Code), never as chat text. Follow the rules in the `grilling` skill's \"How to ask\" section: one question per call, 2-4 options with trade-offs in the descriptions, recommended option first with ` (Recomendado)`, `multiSelect: true` when choices are not exclusive.\n\nExamples:\n\n- Term conflict: options are the glossary meaning, the meaning the user seems to use, and \"são dois termos diferentes\".\n- Fuzzy term: options are the candidate canonical terms.\n- ADR offer: \"Criar ADR\" (with the proposed title in the description) and \"Pular\".\n",{"name":5,"description":7},"main","a5bc9c03f62ea370f93edbe03b6bddf48c06b564","skills\u002Fdomain-modeling","https:\u002F\u002Fgithub.com\u002FSales16\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002FSales16","👋 Olá, sou Eduardo Sales, Desenvolvedor. Apaixonado por solucionar problemas com código. Atualmente, foco em Python, C# .NET e HTML\u002FCSS\u002FJS.","2026-10-14 10:10:03",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Sales16\u002Fclaude-skills --skill domain-modeling",{"tool":37,"command":38},"bunx","bunx skills add Sales16\u002Fclaude-skills --skill domain-modeling",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Sales16\u002Fclaude-skills --skill domain-modeling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSales16\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"ADR-FORMAT.md","REFERENCE","参考文档",2733,"https:\u002F\u002Fgithub.com\u002FSales16\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdomain-modeling\u002FADR-FORMAT.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml",101,"https:\u002F\u002Fgithub.com\u002FSales16\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdomain-modeling\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"CONTEXT-FORMAT.md",2402,"https:\u002F\u002Fgithub.com\u002FSales16\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdomain-modeling\u002FCONTEXT-FORMAT.md",[60,67,74,81,88],{"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},"01M7EMENPEQ2DVV0ZQ2YEZXQ5E","revisar-branch","Revisão profunda da branch atual (ou do PR aberto dela) contra a branch-pai real — develop\u002Fmain ou outra branch de issue da qual ela foi criada, revisando só os commits próprios —, usando a issue do Jira do nome da branch como contexto de escopo. Dispara múltiplos agentes em paralelo — bugs, exceções, edge-cases, duplicidade, segurança, performance, manutenibilidade —, verifica red\u002Fgreen de cada teste novo ou alterado, valida criticamente cada achado e propõe um fix por achado. Use quando pedirem \"revise essa branch\", \"revise meu PR\", \"review antes de abrir PR\", ou antes de \u002Ffinish-issue.","https:\u002F\u002Fgithub.com\u002FSales16\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fskills\u002Frevisar-branch\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},"01M7EMEJWQ2TTMAANP4ZEKYDST","grilling","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002FSales16\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgrilling\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},"01M7EMEHCDPMZB4PHA18CXA05B","grill-with-docs","A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.","https:\u002F\u002Fgithub.com\u002FSales16\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgrill-with-docs\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},"01M7EMEFAY2G075FYY6RDGH9W5","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002FSales16\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgrill-me\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},"01M7EME6HSNXM1WT44VBK5KQP7","atualizar-prs","Atualiza em cadeia uma pilha de PRs empilhados (develop -> PR1 -> PR2 -> PR3), de qualquer branch da pilha. Começa pela branch mais próxima da develop e desce uma por vez, sem paralelismo. Em cada branch remove a migration EF própria, mergeia a branch anterior, resolve conflitos, recria a migration preservando o custom code, compara antiga x nova, compila e testa. Só commita local, nunca dá push sem ordem explícita. Use quando pedirem \"atualiza os PRs em cadeia\", \"atualiza a stack\", \"atualiza minhas branches com a develop\" ou \u002Fatualizar-prs.","https:\u002F\u002Fgithub.com\u002FSales16\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fskills\u002Fatualizar-prs\u002FSKILL.md",[],[]]