[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0VF3AHH9QMC13MSMCFG33":3,"skill-same:01M7F0VF3AHH9QMC13MSMCFG33":46},{"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":30,"updatedAt":31,"install":32,"resources":45},"01M7F0VF3AHH9QMC13MSMCFG33","altium-component-intake",null,"Get a number about a part from the component database, or add a part met for the first time (datasheet download, extraction, check); use whenever a design needs a pin, rating, package or application value of a part.","simulahmed003\u002Faltium-claude-kit","simulahmed003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140954342?v=4","01M7F0V9Y6Q8CW5BB804G4DHQN","Simul Ahmed","01M7F0V9YSGPE568PR4S96S24V",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsimulahmed003\u002Faltium-claude-kit\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Faltium-component-intake\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: altium-component-intake\ndescription: Get a number about a part from the component database, or add a part met for the first time (datasheet download, extraction, check); use whenever a design needs a pin, rating, package or application value of a part.\n---\n\n## Goal\nEvery device number used in a design comes from the part's record in `library\u002Fparts\u002F`, with its datasheet page and\nquote (RQ-01). A part or fact that is missing is added first, then read from the record.\n\n## Inputs\n- the MPN or LCSC C-number, and what the design needs (a section, a fact key)\n- `library\u002Fparts\u002FREADME.md` (record format and the first-time workflow), `library\u002Fparts\u002Ftaxonomy.json` (families, required facts, units)\n\n## Rules to load\n- `rules\u002F02_REQUIREMENTS_CALCS_PARTS.md` (RQ-01 database first, RQ-03 C-numbers, RQ-04 stock at BOM time)\n- `rules\u002F03_LIBRARY.md` (LIB-05 footprint status) when the part goes on to the library\n\n## Approach\n1. `parts.py find \u003Cmpn or C-number>`. Found and PASS: read only the section needed (`parts.py get \u003Cmpn> --section abs_max`).\n2. Not found: `parts.py new --lcsc C123` (or offline `--mpn --mfr --category`), `parts.py fetch \u003Cmpn> --project \u003Cp>`\n   (maker's website first for the English original, LCSC second; downloads need no question), `parts.py locate \u003Cmpn>`, then extract per README step 5: every required fact, pins with the exposed pad,\n   abs max, recommended, package and land pattern, application, layout and firmware notes, each with page and quote.\n3. Found but the needed fact is missing: fetch the datasheet if it is not on disk, extract that fact into the record.\n4. `parts.py check \u003Cmpn>` until PASS, then `parts.py index`. Read the number from the record, not from your notes.\n5. Values the text layer lacks: read the page image, mark `visual`, add to `review.open`.\n6. The project's PDFs stay local in `docs\u002Fdatasheets\u002F`: `parts.py datasheet \u003Cparts> --project \u003Cp>` (or `--manifest`)\n   copies them from the library cache or `--search` folders, else downloads from the record's link. Never commit a PDF.\n7. Extracted records may be used while designing. Before G1 the user checks pins, abs max, package and every visual\n   value and records it with `parts.py verify`; `parts.py check --gate` must PASS.\n\n## Stop and ask the user (do not guess) when\n- `parts.py check` fails and the cause is in the datasheet itself (missing page, unreadable table)\n- the datasheet contradicts itself, another datasheet, the supplier data or the catalog\n- a downloaded datasheet has another sha256 than recorded (the maker revised it)\n- the decision rests on an open `review.open` item or a `visual` value\n- G1 is next and `parts.py check --gate` fails (pins, abs max, package or visual values not checked by the user)\nState the part, the fact, the pages and the options, and wait.\n\n## Exit checks\n| Check | How | Pass when |\n|---|---|---|\n| record valid | `parts.py check \u003Cmpn>` | PASS |\n| index current | `parts.py index` | the part is found by `parts.py find` |\n| G1 ready | `parts.py check --gate` | PASS |\n\n## Write back\n- the record, `library\u002Fdatasheets\u002Findex.json`, `library\u002Fparts\u002Findex.json` (never a PDF, in any repo)\n- `PROJECT.md`: parts added and any open questions to the user\n","## Goal\nEvery device number used in a design comes from the part's record in `library\u002Fparts\u002F`, with its datasheet page and\nquote (RQ-01). A part or fact that is missing is added first, then read from the record.\n\n## Inputs\n- the MPN or LCSC C-number, and what the design needs (a section, a fact key)\n- `library\u002Fparts\u002FREADME.md` (record format and the first-time workflow), `library\u002Fparts\u002Ftaxonomy.json` (families, required facts, units)\n\n## Rules to load\n- `rules\u002F02_REQUIREMENTS_CALCS_PARTS.md` (RQ-01 database first, RQ-03 C-numbers, RQ-04 stock at BOM time)\n- `rules\u002F03_LIBRARY.md` (LIB-05 footprint status) when the part goes on to the library\n\n## Approach\n1. `parts.py find \u003Cmpn or C-number>`. Found and PASS: read only the section needed (`parts.py get \u003Cmpn> --section abs_max`).\n2. Not found: `parts.py new --lcsc C123` (or offline `--mpn --mfr --category`), `parts.py fetch \u003Cmpn> --project \u003Cp>`\n   (maker's website first for the English original, LCSC second; downloads need no question), `parts.py locate \u003Cmpn>`, then extract per README step 5: every required fact, pins with the exposed pad,\n   abs max, recommended, package and land pattern, application, layout and firmware notes, each with page and quote.\n3. Found but the needed fact is missing: fetch the datasheet if it is not on disk, extract that fact into the record.\n4. `parts.py check \u003Cmpn>` until PASS, then `parts.py index`. Read the number from the record, not from your notes.\n5. Values the text layer lacks: read the page image, mark `visual`, add to `review.open`.\n6. The project's PDFs stay local in `docs\u002Fdatasheets\u002F`: `parts.py datasheet \u003Cparts> --project \u003Cp>` (or `--manifest`)\n   copies them from the library cache or `--search` folders, else downloads from the record's link. Never commit a PDF.\n7. Extracted records may be used while designing. Before G1 the user checks pins, abs max, package and every visual\n   value and records it with `parts.py verify`; `parts.py check --gate` must PASS.\n\n## Stop and ask the user (do not guess) when\n- `parts.py check` fails and the cause is in the datasheet itself (missing page, unreadable table)\n- the datasheet contradicts itself, another datasheet, the supplier data or the catalog\n- a downloaded datasheet has another sha256 than recorded (the maker revised it)\n- the decision rests on an open `review.open` item or a `visual` value\n- G1 is next and `parts.py check --gate` fails (pins, abs max, package or visual values not checked by the user)\nState the part, the fact, the pages and the options, and wait.\n\n## Exit checks\n| Check | How | Pass when |\n|---|---|---|\n| record valid | `parts.py check \u003Cmpn>` | PASS |\n| index current | `parts.py index` | the part is found by `parts.py find` |\n| G1 ready | `parts.py check --gate` | PASS |\n\n## Write back\n- the record, `library\u002Fdatasheets\u002Findex.json`, `library\u002Fparts\u002Findex.json` (never a PDF, in any repo)\n- `PROJECT.md`: parts added and any open questions to the user\n",{"name":5,"description":7},"main","ddd2793a851f7fb7607770bab4a6957824cc98ea",".claude\u002Fskills\u002Faltium-component-intake","https:\u002F\u002Fgithub.com\u002Fsimulahmed003\u002Faltium-claude-kit","https:\u002F\u002Fgithub.com\u002Fsimulahmed003","https:\u002F\u002Fsimul-ahmed.vercel.app","Embedded Systems Engineer | PCB Design & Fabrication | Robotics | Energy Science & Engineering, KUET","2026-11-08 05:25:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add simulahmed003\u002Faltium-claude-kit --skill altium-component-intake",{"tool":38,"command":39},"bunx","bunx skills add simulahmed003\u002Faltium-claude-kit --skill altium-component-intake",{"tool":41,"command":42},"pnpm","pnpm dlx skills add simulahmed003\u002Faltium-claude-kit --skill altium-component-intake","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsimulahmed003\u002Faltium-claude-kit\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Faltium-component-intake\u002FSKILL.md",true,[],[47,54,61,67,74],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7F0W2E1X47H52P08G6XB3FS","altium-rule-harvest","Turn the user's design feedback from a project into rule, guideline and user-standard proposals, plus upkeep that keeps the rules small; use at the end of every design stage, or when asked what the kit should learn from a design.","https:\u002F\u002Fgithub.com\u002Fsimulahmed003\u002Faltium-claude-kit\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Faltium-rule-harvest\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7F0VY2ZXQS8BXZ6A0WVZM76","altium-orchestrator","Pick the next step in an Altium board project under projects\u002F\u003Cname>\u002F; use at the start of a design session or when unsure which phase, rules or playbook apply.","https:\u002F\u002Fgithub.com\u002Fsimulahmed003\u002Faltium-claude-kit\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Faltium-orchestrator\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"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":64,"categories":65,"keywords":66,"publishedAt":19},"01M7F0VVNFEZMEXWBH2F54EBMZ","altium-local-library","https:\u002F\u002Fgithub.com\u002Fsimulahmed003\u002Faltium-claude-kit\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Faltium-local-library\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},"01M7F0VQ550X7W2XXX7AZG4HCW","altium-jlc-quote","Get JLCPCB PCB + assembly quotes for one or more boards at several quantities through the browser, including the full cost when parts are short on stock, and deliver an Excel workbook and a screenshot document; use when the user asks for a JLC (PCBA) quotation or price.","https:\u002F\u002Fgithub.com\u002Fsimulahmed003\u002Faltium-claude-kit\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Faltium-jlc-quote\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},"01M7F0VKEQNT8XC4TCYQAXPDWE","altium-fab-package","Build and check the production package for the manufacturer (Gerber zip, BOM, CPL, README, optional assembly drawing) from an Altium or KiCad design, with BOM alternates and a CPL checked by numbers; use when the user asks for fab, production or assembly files.","https:\u002F\u002Fgithub.com\u002Fsimulahmed003\u002Faltium-claude-kit\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Faltium-fab-package\u002FSKILL.md",[],[]]