by adom
Create a wiki component page the RIGHT way. Pages are keyed manufacturer-mpn and scoped to ONE DATASHEET, so a datasheet covering six voltages and three packages is ONE page covering all of them, never six pages. Two manufacturers publishing the same MPN are two pages, because their limits genuinely differ. Renders through a hand-built readme.html on the Adom theme tokens with a fixed ten-section shape (identity, at a glance, specifications, symbol+footprint viewers, pin map, variants, assets, i
← Commit history
SKILL.md+8−1@@ -182,7 +182,14 @@ Add sections when the part earns them (thermal-design tables, application notes, - **Colours come from the `adom-theme` skill**, studio-dark column. Load it, do not guess. `--green` / `--red` / `--yellow` are SEMANTIC (success / destructive / warning) and must not be used as categorical colours. For a pin-map legend needing many hues, derive a ramp across the three non-semantic brand hues (teal `#00b8b1`, blue `#64abff`, purple `#8c6bf7`) plus neutrals. - **Fonts**: Satoshi for prose, "JetBrains Mono" for code and part numbers.-- **No em-dashes, no en-dashes, no emoji.** House prose rule, and `adom-wiki pkg publish` lints for it. Run `prose-lint README.md`.+- **No em-dashes, no en-dashes, no emoji.** House prose rule, and `adom-wiki pkg publish` lints for it.++ ```sh+ prose-lint README.md readme.html+ grep -c -e '—' -e '–' readme.html # prose-lint CANNOT see these+ ```++ `prose-lint` matches the literal `—` and `–` characters and **not their HTML entities**, so a `readme.html` written with `—` passes clean while the rendered page is full of em-dashes. Grep for the entities yourself until adom/prose-lint#1 lands. Substitutions that read well: a dash introducing an elaboration becomes a colon, or a period plus a capital when what follows is an independent clause; a bare dash in a table cell becomes `n/a`; a numeric range `1.5 – 2.5` becomes `1.5 to 2.5`. - **Every number is attributable.** If it is not in the datasheet, either cite where it came from in Provenance or leave it out. - Keep the `postMessage` height-reporting script at the bottom of the template. The wiki sizes the readme iframe from it.
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "adom-component-page",- "version": "2.0.0",+ "version": "2.0.1", "type": "skill", "description": "Create a wiki component page the RIGHT way. Pages are keyed manufacturer-mpn and scoped to ONE DATASHEET, so a datasheet covering six voltages and three packages is ONE page covering all of them, never six pages. Two manufacturers publishing the same MPN are two pages, because their limits genuinely differ. Renders through a hand-built readme.html on the Adom theme tokens with a fixed ten-section shape (identity, at a glance, specifications, symbol+footprint viewers, pin map, variants, assets, implementation, datasheet, provenance). Anything not available yet gets a 'not available, open a pull request' placeholder rather than being silently dropped. Covers the boundary decision, dedup against existing and legacy bare-MPN pages, pulling CAD from KiCad's official library, the adom-footprint empty-fab-layer workaround, publishing both the registry and page-repo layers, deprecating a page so it actually looks deprecated, and linking into a library.", "tags": [
page.json+1−1@@ -1,6 +1,6 @@ { "slug": "adom-component-page",- "version": "2.0.0",+ "version": "2.0.1", "type": "skill", "description": "Create a wiki component page the RIGHT way. Pages are keyed manufacturer-mpn and scoped to ONE DATASHEET, so a datasheet covering six voltages and three packages is ONE page covering all of them, never six pages. Two manufacturers publishing the same MPN are two pages, because their limits genuinely differ. Renders through a hand-built readme.html on the Adom theme tokens with a fixed ten-section shape (identity, at a glance, specifications, symbol+footprint viewers, pin map, variants, assets, implementation, datasheet, provenance). Anything not available yet gets a 'not available, open a pull request' placeholder rather than being silently dropped. Covers the boundary decision, dedup against existing and legacy bare-MPN pages, pulling CAD from KiCad's official library, the adom-footprint empty-fab-layer workaround, publishing both the registry and page-repo layers, deprecating a page so it actually looks deprecated, and linking into a library.", "tags": [