[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DDJSGQ558TSJ83A243A63V":3,"skill-same:01M7DDJSGQ558TSJ83A243A63V":51},{"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":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7DDJSGQ558TSJ83A243A63V","circuit-spec-integration",null,"Audit behavior that spans more than one exact component, such as shared supplies, signal boundaries, startup and reset states, protection, sensing, thermal coupling, firmware assumptions and as-built state. Use whenever a question, substitution or design change involves several component records or a stage beyond a single datasheet.","Takazudo\u002Fzudo-circuit-doc","Takazudo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128233?v=4","01M71B20VDT4VZ991ET3Y5ZYEN","Takeshi Takatsudo","01M7DDJAFBYYYT9D9V42NBQ0G0",0,"MIT","https:\u002F\u002Fgithub.com\u002FTakazudo\u002Fzudo-circuit-doc\u002Fblob\u002Fmain\u002Fexamples\u002Fempty\u002F.claude\u002Fskills\u002Fcircuit-spec-integration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: circuit-spec-integration\ndescription: Audit behavior that spans more than one exact component, such as shared supplies, signal boundaries, startup and reset states, protection, sensing, thermal coupling, firmware assumptions and as-built state. Use whenever a question, substitution or design change involves several component records or a stage beyond a single datasheet.\n---\n\n# Circuit specification integration\n\nIndividually valid components do not prove the whole circuit. This skill handles the cross-component rules in `references\u002Frules.json`. The canonical workflow is [circuit\u002FWORKFLOW.md](..\u002F..\u002F..\u002Fcircuit\u002FWORKFLOW.md).\n\n1. Run `pnpm exec zudo-circuit-doc validate` (or `pnpm circuit:check`) and note pre-existing failures.\n2. Read `references\u002Frules.json` and load every exact owner bundle named by each matching rule, through the component-spec-audit skill. Resolve manufacturer, MPN and order codes independently; reject conflicts, same-name wrong-vendor parts and ambiguous bare names. Load subordinate records directly.\n3. Use the listed fact IDs with their exact conditions and locators. An `UNSOURCED` fact cannot close a domain, and design connectivity cannot prove programmed, assembled or measured state.\n4. For a substitution or design change, report the affected rule, the raw facts, recalculated margins with their dependencies, the evidence stages still missing, and one honest verdict. Do not change design files silently.\n5. Recompute conditioned calculations from their inputs. The validator checks the arithmetic, not the units or the reading of the source table; check those yourself.\n\n## Adding a rule\n\nThe rule list may be empty; `{ \"schema_version\": 1, \"rules\": [] }` is valid. Add a rule **only when a real interaction exists** between exact components. A rule names its `rule_id`, `domain`, `record_ids`, `fact_ids` (owned by those records), `conditions`, `verdict`, `refusal` text and any `conditioned_calculations`.\n\nAn evidence chain lists stages in order, from the official source and the conditioned requirement through the netlist, symbol and footprint, PCB orientation, BOM and placement, as-built and programmed state, to bench results. Every stage stays `OPEN` with empty `fact_ids` until real evidence exists. A completed early stage never implies a later one, and a generated netlist is never `CONFIRMED`.\n\nAfter editing rules, update the integration count lock `expect.integrationRules` in `circuit\u002Fpublication\u002Fselection.json`, then run `pnpm circuit:generate` and `pnpm check`.\n","# Circuit specification integration\n\nIndividually valid components do not prove the whole circuit. This skill handles the cross-component rules in `references\u002Frules.json`. The canonical workflow is [circuit\u002FWORKFLOW.md](..\u002F..\u002F..\u002Fcircuit\u002FWORKFLOW.md).\n\n1. Run `pnpm exec zudo-circuit-doc validate` (or `pnpm circuit:check`) and note pre-existing failures.\n2. Read `references\u002Frules.json` and load every exact owner bundle named by each matching rule, through the component-spec-audit skill. Resolve manufacturer, MPN and order codes independently; reject conflicts, same-name wrong-vendor parts and ambiguous bare names. Load subordinate records directly.\n3. Use the listed fact IDs with their exact conditions and locators. An `UNSOURCED` fact cannot close a domain, and design connectivity cannot prove programmed, assembled or measured state.\n4. For a substitution or design change, report the affected rule, the raw facts, recalculated margins with their dependencies, the evidence stages still missing, and one honest verdict. Do not change design files silently.\n5. Recompute conditioned calculations from their inputs. The validator checks the arithmetic, not the units or the reading of the source table; check those yourself.\n\n## Adding a rule\n\nThe rule list may be empty; `{ \"schema_version\": 1, \"rules\": [] }` is valid. Add a rule **only when a real interaction exists** between exact components. A rule names its `rule_id`, `domain`, `record_ids`, `fact_ids` (owned by those records), `conditions`, `verdict`, `refusal` text and any `conditioned_calculations`.\n\nAn evidence chain lists stages in order, from the official source and the conditioned requirement through the netlist, symbol and footprint, PCB orientation, BOM and placement, as-built and programmed state, to bench results. Every stage stays `OPEN` with empty `fact_ids` until real evidence exists. A completed early stage never implies a later one, and a generated netlist is never `CONFIRMED`.\n\nAfter editing rules, update the integration count lock `expect.integrationRules` in `circuit\u002Fpublication\u002Fselection.json`, then run `pnpm circuit:generate` and `pnpm check`.\n",{"name":5,"description":7},"main","9e46d70ac7accfe98abce683d6f550274e6731d0","examples\u002Fempty\u002F.claude\u002Fskills\u002Fcircuit-spec-integration","https:\u002F\u002Fgithub.com\u002FTakazudo\u002Fzudo-circuit-doc","https:\u002F\u002Fgithub.com\u002FTakazudo","https:\u002F\u002Ftakazudo.me","2026-11-13 00:43:35",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Takazudo\u002Fzudo-circuit-doc --skill circuit-spec-integration",{"tool":37,"command":38},"bunx","bunx skills add Takazudo\u002Fzudo-circuit-doc --skill circuit-spec-integration",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Takazudo\u002Fzudo-circuit-doc --skill circuit-spec-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTakazudo\u002Fzudo-circuit-doc\u002Fblob\u002Fmain\u002Fexamples\u002Fempty\u002F.claude\u002Fskills\u002Fcircuit-spec-integration\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Frules.json","REFERENCE","参考文档",41,"https:\u002F\u002Fgithub.com\u002FTakazudo\u002Fzudo-circuit-doc\u002Fblob\u002Fmain\u002Fexamples\u002Fempty\u002F.claude\u002Fskills\u002Fcircuit-spec-integration\u002Freferences\u002Frules.json",[52,58,64,69,76,83],{"skillNo":53,"name":54,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7DDPFDRT2Z0T14HSSCD3A5Q","component-spec-audit","https:\u002F\u002Fgithub.com\u002FTakazudo\u002Fzudo-circuit-doc\u002Fblob\u002Fmain\u002Fpackages\u002Fcreate-zudo-circuit-doc\u002Ftest\u002Ffixtures\u002Ftemplate\u002F.claude\u002Fskills\u002Fcomponent-spec-audit\u002FSKILL.md",[],[],{"skillNo":59,"name":54,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7DDPBWD406JGYAGQGVQ00X7","Audit exact electronic-component identities and evidence, and run the end-to-end workflow for adding or replacing a component. Use whenever circuit, schematic, PCB, BOM, firmware, bring-up, substitution or documentation work could depend on a component rating, pin, package, source, CAD asset, publication or interaction.","https:\u002F\u002Fgithub.com\u002FTakazudo\u002Fzudo-circuit-doc\u002Fblob\u002Fmain\u002Fpackages\u002Fcreate-zudo-circuit-doc\u002Ftemplates\u002Fdefault\u002F.claude\u002Fskills\u002Fcomponent-spec-audit\u002FSKILL.md",[],[],{"skillNo":65,"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":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DDP80DW34N9DSWFMFZNP91","https:\u002F\u002Fgithub.com\u002FTakazudo\u002Fzudo-circuit-doc\u002Fblob\u002Fmain\u002Fpackages\u002Fcreate-zudo-circuit-doc\u002Ftemplates\u002Fdefault\u002F.claude\u002Fskills\u002Fcircuit-spec-integration\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DDP4VY9ZF7DRB1GN50996X","component-example","Resolve exact EXAMPLE-MPN component limits and application constraints. Use whenever EXAMPLE-MPN, its LCSC ID, manufacturer, function, pins, package, substitution, bring-up, or firmware behavior is relevant.","https:\u002F\u002Fgithub.com\u002FTakazudo\u002Fzudo-circuit-doc\u002Fblob\u002Fmain\u002Fpackages\u002Fcircuit-doc\u002Ftemplates\u002Fcomponent-skill-template\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DDNZM50BP1XMP22VSMDH76","component-xfcn-board-headers","Audit the exact XFCN PZ254V-11-06P C492405 male and PM254V-11-06-H85 C2832269 female six-position 2.54 mm board-to-board headers. Use for Boards P\u002FL pin order, orientation, footprint, ratings, mating, stock, alignment, or substitution.","https:\u002F\u002Fgithub.com\u002FTakazudo\u002Fzudo-circuit-doc\u002Fblob\u002Fmain\u002Ffixtures\u002Fled\u002Fupstream\u002F.claude\u002Fskills\u002Fcomponent-xfcn-board-headers\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DDNTN99XAZJKQ8830B7Y0A","component-umw-ao3401a-c347476","Audit the exact UMW (Youtai Semiconductor) AO3401A C347476 P-channel load-switch MOSFET. Use for Board P Q1 identity, gate polarity, pinout, ratings, SOA, thermal behavior, bring-up, or substitution decisions.","https:\u002F\u002Fgithub.com\u002FTakazudo\u002Fzudo-circuit-doc\u002Fblob\u002Fmain\u002Ffixtures\u002Fled\u002Fupstream\u002F.claude\u002Fskills\u002Fcomponent-umw-ao3401a-c347476\u002FSKILL.md",[],[]]