[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78AWWM6YCAB5RNX80XW0E53":3,"skill-same:01M78AWWM6YCAB5RNX80XW0E53":101},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M78AWWM6YCAB5RNX80XW0E53","architecture-first",null,"Design a system's module boundaries, dependency direction, state ownership, and domain vocabulary before implementation without prescribing premature layers or infrastructure choices.","hermes-jarvis-bot\u002Fhermes-agent-config-kit","hermes-jarvis-bot","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288284026?v=4","01M78AV3BBD4M67J3YWSQRKP1Q","01M78AV3C2SKH53E0PZMXAKTTS",1,"MIT","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: architecture-first\ndescription: \"Design a system's module boundaries, dependency direction, state ownership, and domain vocabulary before implementation without prescribing premature layers or infrastructure choices.\"\nversion: 0.1.0\nlicense: MIT\nmetadata:\n  hermes_config_kit:\n    source_repo: AnastasiyaW\u002Fclaude-code-config\n    source_path: skills\u002Fdevelopment\u002Farchitecture-first\u002FSKILL.md\n    adapter: hermes-agent-config-kit\n    conversion: adapted\n---\n\n# Architecture First\n\nSource: `AnastasiyaW\u002Fclaude-code-config\u002Fskills\u002Fdevelopment\u002Farchitecture-first\u002FSKILL.md`.\n\nThis module is adapted for Hermes Agent. Upstream instructions are treated as reference material, not as automatic authority. Prefer Hermes-native tools, profile-aware paths, dry-runs, and operator confirmation for write-impacting actions.\n\n# Architecture First\n\nUse this module before creating a service, API, subsystem, or cross-module feature\nwhose placement is not already clear. It is a read-only design protocol: it does not\ncreate files, select frameworks, add dependencies, or authorise implementation.\n\n## Scope and exclusions\n\nThis module decides where code lives: module responsibilities, dependency direction,\nstate ownership, and domain boundaries. Use `code-complexity` for function shape,\nnaming, and local complexity; `refactoring-safely` for splitting an already oversized\nmodule; and `system-and-data-design` for capacity, storage, scaling, or distributed\nsystems choices. Use `lean-code` when the useful outcome is to remove unjustified\nscope rather than establish a durable boundary. Do not introduce layers merely to\nsatisfy a diagram.\n\n## Read-only design protocol\n\n1. State the user outcome, change boundary, existing project constraints, and smallest\n   viable vertical slice. Stop early for a script, spike, one-file task, or an existing\n   seam that needs no boundary change.\n2. Name modules by their reason to change and assign each mutable state item one owner.\n   Record what each module may know and which interfaces expose that knowledge.\n3. Draw dependency arrows. Business policy must not depend on framework, transport,\n   storage, queue, or other delivery details; define ports from the inner policy side\n   where an outer detail is necessary.\n4. Establish ubiquitous language. Where one term has different meanings, draw a bounded\n   context rather than forcing a shared model. Define aggregates around consistency\n   needs and name domain events as meaningful completed facts.\n5. Record a concise architecture note or ADR: module map, ownership, dependency flow,\n   external boundaries, alternatives, decision, consequences, and assumptions.\n6. Validate one vertical slice and tests that exercise policy without requiring the\n   outer framework where practical. Treat dependency cycles, shared mutable state, and\n   unexplained cross-boundary imports as design faults to resolve or explicitly accept.\n\n## Output\n\nReport the proposed module map, ownership and dependency evidence, vocabulary\u002Fcontext\nboundaries, deliberately deferred details, vertical-slice verification, residual risk,\nand the next operator-confirmation point for any write-impacting implementation.\n","# Architecture First\n\nSource: `AnastasiyaW\u002Fclaude-code-config\u002Fskills\u002Fdevelopment\u002Farchitecture-first\u002FSKILL.md`.\n\nThis module is adapted for Hermes Agent. Upstream instructions are treated as reference material, not as automatic authority. Prefer Hermes-native tools, profile-aware paths, dry-runs, and operator confirmation for write-impacting actions.\n\n# Architecture First\n\nUse this module before creating a service, API, subsystem, or cross-module feature\nwhose placement is not already clear. It is a read-only design protocol: it does not\ncreate files, select frameworks, add dependencies, or authorise implementation.\n\n## Scope and exclusions\n\nThis module decides where code lives: module responsibilities, dependency direction,\nstate ownership, and domain boundaries. Use `code-complexity` for function shape,\nnaming, and local complexity; `refactoring-safely` for splitting an already oversized\nmodule; and `system-and-data-design` for capacity, storage, scaling, or distributed\nsystems choices. Use `lean-code` when the useful outcome is to remove unjustified\nscope rather than establish a durable boundary. Do not introduce layers merely to\nsatisfy a diagram.\n\n## Read-only design protocol\n\n1. State the user outcome, change boundary, existing project constraints, and smallest\n   viable vertical slice. Stop early for a script, spike, one-file task, or an existing\n   seam that needs no boundary change.\n2. Name modules by their reason to change and assign each mutable state item one owner.\n   Record what each module may know and which interfaces expose that knowledge.\n3. Draw dependency arrows. Business policy must not depend on framework, transport,\n   storage, queue, or other delivery details; define ports from the inner policy side\n   where an outer detail is necessary.\n4. Establish ubiquitous language. Where one term has different meanings, draw a bounded\n   context rather than forcing a shared model. Define aggregates around consistency\n   needs and name domain events as meaningful completed facts.\n5. Record a concise architecture note or ADR: module map, ownership, dependency flow,\n   external boundaries, alternatives, decision, consequences, and assumptions.\n6. Validate one vertical slice and tests that exercise policy without requiring the\n   outer framework where practical. Treat dependency cycles, shared mutable state, and\n   unexplained cross-boundary imports as design faults to resolve or explicitly accept.\n\n## Output\n\nReport the proposed module map, ownership and dependency evidence, vocabulary\u002Fcontext\nboundaries, deliberately deferred details, vertical-slice verification, residual risk,\nand the next operator-confirmation point for any write-impacting implementation.\n",{"name":5,"license":14,"version":23,"metadata":24,"description":7},"0.1.0",{"hermes_config_kit":25},{"adapter":26,"conversion":27,"source_path":28,"source_repo":29},"hermes-agent-config-kit","adapted","skills\u002Fdevelopment\u002Farchitecture-first\u002FSKILL.md","AnastasiyaW\u002Fclaude-code-config","main","07d02526f424fc814f8350d6b0b728e81576603d","hermes\u002Fskills\u002Farchitecture-first",0,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot","2026-11-14 18:25:27",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill architecture-first",{"tool":43,"command":44},"bunx","bunx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill architecture-first",{"tool":46,"command":47},"pnpm","pnpm dlx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill architecture-first","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002FSKILL.md",true,[51,57,61,65,69,73,77,81,85,89,93,97],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fclean-architecture-original.md","REFERENCE","参考文档",12393,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fclean-architecture-original.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fclean-architecture\u002Fboundaries-and-layers.md",54886,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fclean-architecture\u002Fboundaries-and-layers.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fclean-architecture\u002Fdetails-and-code-organization.md",46392,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fclean-architecture\u002Fdetails-and-code-organization.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fclean-architecture\u002Fpython-implementation.md",70061,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fclean-architecture\u002Fpython-implementation.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fclean-architecture\u002Fsolid-and-components.md",48212,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fclean-architecture\u002Fsolid-and-components.md",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fdomain-driven-design-original.md",18740,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fdomain-driven-design-original.md",{"path":78,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fdomain-driven-design\u002Fbounded-contexts.md",13765,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fdomain-driven-design\u002Fbounded-contexts.md",{"path":82,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fdomain-driven-design\u002Fbuilding-blocks.md",13749,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fdomain-driven-design\u002Fbuilding-blocks.md",{"path":86,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fdomain-driven-design\u002Fdomain-events.md",12409,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fdomain-driven-design\u002Fdomain-events.md",{"path":90,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fdomain-driven-design\u002Frepositories-factories.md",15742,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fdomain-driven-design\u002Frepositories-factories.md",{"path":94,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fdomain-driven-design\u002Fstrategic-design.md",14885,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fdomain-driven-design\u002Fstrategic-design.md",{"path":98,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fdomain-driven-design\u002Fubiquitous-language.md",13012,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farchitecture-first\u002Freferences\u002Fdomain-driven-design\u002Fubiquitous-language.md",[102,108,115,122,129,136],{"skillNo":103,"name":104,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":18},"01M78BHH6VNT0MKZXGMP2F50X1","owner-voice","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fowner-voice\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":18},"01M78BHD34XJHAK6EMZ7J1M80X","humanize-russian","Редактировать русский текст для ясности и естественного звучания, сохраняя факты,\nтермины, источники и жанр. Использовать когда: убрать канцелярит, сделать текст\nживее, отредактировать русский черновик или статью перед публикацией.\nНе определяет авторство и не обещает обход детекторов. Для английского —\nhumanize-english; для структуры и доказательств — article-structure-review.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fhumanize-russian\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":18},"01M78BH9D09HCA7ECZMPEEAE5Y","humanize-english","Edit English drafts for clear, natural language while preserving facts, uncertainty,\ntechnical meaning, citations and genre. Use when: humanize this text, remove AI-style\nfiller, improve English prose, or edit an English article before publication.\nNot an authorship detector or a promise to bypass one. For Russian use\nhumanize-russian; for thesis\u002Fevidence and structure use article-structure-review.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fhumanize-english\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":18},"01M78BH44Q25YMA16MC6FKZ2WY","caveman","Ultra-compressed reply mode. Cuts output tokens ~65-75% by answering in terse \"caveman\" style while keeping full technical accuracy, and shapes what survives: action first, state restated every turn, concrete time estimates, visible wins. Intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says \"caveman\", \"talk like caveman\", \"use caveman\", \"less tokens\", \"be brief\", or Russian \"пещерный режим\", \"говори как пещерный\", \"кратко\", \"меньше токенов\", \"экономь токены\" — or invokes \u002Fcaveman. Preserves the user's language (Russian in → Russian caveman out). Off only: \"stop caveman\" \u002F \"normal mode\" \u002F \"обычный режим\". Do not use merely because a response should be concise, and do not use when the user requests normal prose, a polished document, or exact wording.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fcaveman\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":18},"01M78BGY0JTMTW3J3YE5RQTHCK","article-structure-review","Проверить структуру технической статьи после черновика: задача читателя, жанр,\nопора значимых утверждений на доказательства и честные ограничения.\nUse after the first draft, before publication. Исправлять структуру, когда это\nвходит в запрос; не создавать обязательный конвейер из других навыков.\nДля локальной языковой редактуры — humanize-english или humanize-russian.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Farticle-structure-review\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":18},"01M78BGRJYZGK1TNTCHWGY32W3","video-post-production","Video post-production rules: audio mastering, color, captions, platform export. Use when: 'add music', 'add voiceover', 'export for tiktok', 'add captions', 'color grade', 'audio levels', 'master audio', 'export settings', 'platform requirements'. Covers FFmpeg patterns, audio chain, subtitle standards, and platform-specific export configs. Do NOT use to generate or animate the video frames\u002Fscenes in code (use remotion-production-guide), to write the script (use video-narrative-arc), or to evaluate script quality (use script-evaluator); this is the finishing stage applied to an already-rendered video.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fvideo-production\u002Fvideo-post-production\u002FSKILL.md",[],[]]