[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CPH26FD4983V1TEKWN24J7":3,"skill-same:01M7CPH26FD4983V1TEKWN24J7":62},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M7CPH26FD4983V1TEKWN24J7","jetson-derive-carrier",null,"Bootstrap a custom carrier board by forking carrier files and scaffolding a DT overlay from the reference devkit. Use after jetson-init-source; not for module-level or kernel-DTB changes.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fjetson-derive-carrier\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jetson-derive-carrier\ndescription: >-\n  Bootstrap a custom carrier board by forking carrier files and\n  scaffolding a DT overlay from the reference devkit. Use after\n  jetson-init-source; not for module-level or kernel-DTB changes.\nversion: 0.0.1\nlicense: \"Apache-2.0\"\nmetadata:\n  data-classification: public\n  author: \"Jetson Team\"\n  tags:\n    - target-platform\n    - custom-carrier\n    - bring-up\n    - setup\n  domain: meta\n---\n\n# jetson-derive-carrier\n\nCustomize first-run gate for any `customize-*` skill on a custom\ncarrier. Resolve the active target per\n[`target-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md).\n**Refuse** if no `custom_carrier:` block, or if\n`\u003Csource.root_path>\u002FLinux_for_Tegra\u002F.git` is missing\n(`jetson-init-source` first). Template file create\u002Fcopy rows land in a\nsingle overlay-tracker commit and copy **directly** to the\ncustom-carrier-renamed target path — reference-named pristine files\nare never staged (see [Fork plan](#fork-plan) for the local rule, which\noverrides the standard pristine + customization split from the\n[workflow](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#commit-batching-in-the-overlay-tracker));\nconf-chain discovery follows\n[per-board conf dispatch](..\u002F..\u002Fcontext\u002Fbsp-customization-software-layers.md#per-board-conf-dispatch--update_flash_args_common).\nKernel base DTB is **not** forked — carrier deltas layer as a DT\noverlay wired via `OVERLAY_DTB_FILE`.\n\n**Identifiers** (from active profile): `\u003Cchip>` from\n`reference_devkit.module.id` via\n[catalogue](..\u002F..\u002Freferences\u002Fbsp-platforms-catalogue.md) (unknown →\nwarn, fallback `tegra234`); `\u003Cmodule-id>`\u002F`\u003Cmodule-sku>` from\n`reference_devkit.module`; `\u003Ccarrier-id>`\u002F`\u003Ccarrier-sku>` from\n`reference_devkit.carrier`; `\u003Ccustom-id>`\u002F`\u003Ccustom-sku>`\u002F\n`\u003Ccustom-flash-conf>` from `custom_carrier`. `\u003Creal-conf>` =\n`readlink \u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F\u003Creference_devkit.flash_config>`\n(NVIDIA convention `\u003Cdevkit>.conf` → `\u003Ccarrier>-\u003Cmodule>-a\u003Crev>.conf`;\nwarn + treat top-level as real + skip symlink-wrapper row if not a\nsymlink).\n\n`\u003Ccustom-id>` is a custom carrier board token, not necessarily an\nNVIDIA-style `pNNNN` ID. Use it verbatim in dash-form filenames and DT\ncompatible strings. When a target file family uses p-stripped numeric\ntokens, derive `\u003Ccustom-id-file-token>` as `NNNN` only if `\u003Ccustom-id>`\nmatches `^p[0-9]{4}$`; otherwise use `\u003Ccustom-id>` unchanged. Do not\nreject custom carrier IDs merely because they do not start with `p`.\n\n## Instructions\n\nThe fork plan below is the instruction set: one discovery pass, then a\nrow-by-row fork of the per-board fileset, gated by the commit-message\npreview before each `git commit`.\n\n### Fork plan\n\nEvery `git commit` produced by this skill — in the overlay tracker\n(`Linux_for_Tegra\u002F`) or the `hardware\u002F` source repo — runs through\nthe\n[commit message preview gate](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#commit-message-preview-gate).\nSurface the staged file list + proposed message to the operator\nand require accept \u002F edit \u002F cancel before each `git commit`; on\n**cancel** leave the index staged for manual resolution.\n\n**Materialize renamed forks even when bytes do not change.** For every\naccepted fork-plan row, create and track the custom-carrier target path;\ndo not skip a missing target because the fork is only a rename\u002Fcopy or is\nbyte-identical to the reference. This includes BCT forks such as pinmux,\nGPIO\u002FGPIOINT, padvoltage\u002FPMC, misc, and MB2 misc. Skip only when the\nAcceptance column allows it, the source is an explicit warn-and-skip\nmiss, or the expected target path is already tracked; in the last case,\nreport it as already derived and do not create an empty commit.\n\n**Template file create\u002Fcopy rows squash into one overlay-tracker\ncommit, and reference-named pristine files are never staged.** All\nrows that materialize a new (template-derived) file in the overlay\ntracker — board flash-conf, flash-conf symlink, MB1 BCT (pinmux,\nGPIO\u002FGPIOINT, padvoltage\u002FPMC, misc), MB2 BCT (misc), BPMP DTB (when\nopted in), nvpmodel, nvfancontrol — copy **directly** from\n`\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F\u003Crel>\u002F\u003Creference-name>` to\n`\u003Csource.root_path>\u002FLinux_for_Tegra\u002F\u003Crel>\u002F\u003Ccustom-name>` with any\ncontent edits applied before staging. The reference-named\n(`\u003Ccarrier-id>-\u003Ccarrier-sku>`-keyed) filename is never staged or\ncommitted in the overlay tracker — only the custom-carrier-renamed\nfile is tracked. This overrides the standard pristine + customization\nsplit from\n[commit batching](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#commit-batching-in-the-overlay-tracker).\nAll such rows land in a **single** overlay-tracker commit that adds:\n(i) the custom-carrier-named files at their target paths with content\nalready applied, (ii) the flash-conf symlink, and (iii) the targeted\nflash-conf content rewrites inside the renamed flash-conf for\n`PINMUX_CONFIG` \u002F `GPIO_CONFIG` \u002F `GPIOINT_CONFIG` \u002F `PMC_CONFIG` \u002F\n`MISC_CONFIG` \u002F `MB2_BCT` (plus `BPFDTB_FILE` when BPMP DTB is opted\nin). Rows that edit existing upstream files instead of creating\ntemplates — the `nvpower.sh` patch — and the overlay wire-up\n(`OVERLAY_DTB_FILE+=` append to the just-created flash-conf fork,\ntreated as a temporally distinct phase per\n[commit batching](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#commit-batching-in-the-overlay-tracker))\nremain separate commits per their own rows. The DT overlay skeleton\ncommits in `bsp_sources\u002Fhardware\u002F`, not the overlay tracker, so it is\nunaffected. The commit message preview gate fires once on the\nsquashed commit; warn-and-skipped rows do not contribute, and if every\nrow in the bundle is already tracked the commit is omitted entirely.\n\n### Discovery (single batched pass)\n\nRun **one** discovery pass; do not interleave with staging. **Do not\ntruncate listings** — every candidate filename in each scanned\ndirectory must be visible to the matcher. `head`, `tail`, `| head -N`,\n`| tail -N`, and any other row-limiting filter are out of bounds for\nthis step; use `ls -1` \u002F `find` unclipped, or grep on the full output.\nTruncating risks false warn-and-skip calls when the matching file\nsits past the cutoff. Capture:\n\n- Flash-conf vars: `DTB_FILE` \u002F `TBCDTB_FILE` \u002F `BPFDTB_FILE` \u002F\n  `PINMUX_CONFIG` \u002F `PMC_CONFIG` \u002F `GPIO_CONFIG` \u002F `GPIOINT_CONFIG`.\n  `DTB_FILE` \u002F `TBCDTB_FILE` are captured for **reference only** so\n  the overlay wire-up can derive `\u003Cdtb-stem>` for the overlay\n  filename — they are never rewritten by this skill.\n- BCT `.dts` at `bootloader\u002Fgeneric\u002FBCT\u002F`; `.dtsi` siblings live\n  **one level up at `bootloader\u002F`** — NOT alongside.\n- nvpmodel: `nvpmodel_\u003Cmodule-id>_\u003Cmodule-sku>*.conf`. nvfancontrol:\n  `nvfancontrol_\u003Cmodule-id>_\u003Cmodule-sku>_\u003Ccarrier-id>_\u003Ccarrier-sku>.conf`.\n- `nvpower.sh` anchors for (a)–(d): `\u003Ccarrier-id>` cvb branch,\n  `\u003Cmodule-id>-\u003Cmodule-sku>` SKU `elif`, `tegra\u003Cchip>` nvpmodel\n  cascade, `tegra\u003Cchip>` nvfancontrol cascade.\n\n| File \u002F category | Discovery | Acceptance | Fork rule |\n|---|---|---|---|\n| Board flash conf | `\u003Creal-conf>` | Always | Filename sub `\u003Ccarrier-id>-\u003Ccarrier-sku>` → `\u003Ccustom-id>-\u003Ccustom-sku>`. Content sub is **targeted, not blanket**: rewrite RHS only for vars whose file this skill forks — `PINMUX_CONFIG`, `PMC_CONFIG`, `GPIO_CONFIG` \u002F `GPIOINT_CONFIG`, `MISC_CONFIG`, `MB2_BCT`. Other carrier-keyed vars (`DTB_FILE`, `TBCDTB_FILE`, `SCR_CONFIG`, `PMIC_CONFIG`, `DEVICEPROD_CONFIG`, `PROD_CONFIG`, `MINRATCHET_CONFIG`, `UPHY_CONFIG`, dynamic `OVERLAY_DTB_FILE+=`) MUST stay at reference values — their files aren't forked here and a blanket `sed` would point them at nonexistent files. `DTB_FILE` \u002F `TBCDTB_FILE` specifically: base DTB is not forked; the overlay row appends a new `OVERLAY_DTB_FILE+=` line instead. `BPFDTB_FILE`: opt-in extra commit. Never touch `\u003Cchip>`, `\u003Cmodule-id>`, `xxxx`. |\n| Flash-conf symlink | Unconditional | Always (skip if `\u003Creal-conf>` not a symlink) | New symlink `\u003Ccustom-flash-conf>` → flash-conf fork |\n| MB1 BCT pinmux | `PINMUX_CONFIG` + `#include` follow ¶ | Always | Rename rule † |\n| MB1 BCT GPIO | `GPIO_CONFIG`\u002F`GPIOINT_CONFIG` + `#include` follow ¶ | Always | Rename rule † |\n| MB1 BCT padvoltage | `PMC_CONFIG` + `#include` follow ¶ | Always | Rename rule † |\n| MB1 BCT misc | `MISC_CONFIG` + `#include` follow ¶ | Always | Rename rule † |\n| MB2 BCT misc | `MB2_BCT` + `#include` follow ¶ | Always | Rename rule † |\n| Kernel DTB + source DTS | (reference only — see header) | Never forked | Base DTB stays at reference. No pristine binary copy in the overlay tracker; no source DTS fork in `bsp_sources\u002Fhardware\u002F`. Carrier deltas live entirely in the DT overlay (next row). |\n| DT overlay skeleton (NEW) | Unconditional | Always | Create `\u003Csource.root_path>\u002Fhardware\u002Fnvidia\u002F\u003Cchip>\u002Fnv-public\u002Foverlay\u002F\u003Cchip>-\u003Ccustom-id>-\u003Ccustom-sku>+\u003Cmodule-id>-\u003Cmodule-sku>.dts` (skeleton ‡); commit in `hardware\u002F`, push to origin |\n| Per-dir Makefile registration | `\u003Csource.root_path>\u002Fbsp_sources\u002Fhardware\u002Fnvidia\u002F\u003Cchip>\u002Fnv-public\u002Foverlay\u002FMakefile` | Always | Append `dtbo-y += \u003Cchip>-\u003Ccustom-id>-\u003Ccustom-sku>+\u003Cmodule-id>-\u003Cmodule-sku>.dtbo` after the **last literal-named** `dtbo-y +=` entry (BEFORE the `$(addprefix $(makefile-path)\u002F,$(dtbo-y))` prefix block — inserting after `dtbo-y += $(old-dtbo)` silently drops the .dtbo). Same position-sensitive idiom and snippet as the composite slot's Makefile patch in [`..\u002Fjetson-build-source\u002Freferences\u002Fcomposite-registration.md#makefile-patch-idempotent-position-sensitive`](..\u002Fjetson-build-source\u002Freferences\u002Fcomposite-registration.md#makefile-patch-idempotent-position-sensitive). Commit in `hardware\u002F`. Without this row, `nvidia-dtbs` never produces the `.dtbo` referenced by the next row's `OVERLAY_DTB_FILE+=` line and `flash.sh` aborts mid-flash on the missing file. |\n| Overlay wire-up | Unconditional | Always | Append `OVERLAY_DTB_FILE+=\",\u003Cchip>-\u003Ccustom-id>-\u003Ccustom-sku>+\u003Cmodule-id>-\u003Cmodule-sku>.dtbo\"` to flash-conf fork (extra commit) |\n| nvpmodel config | `rootfs\u002Fetc\u002Fnvpmodel\u002Fnvpmodel_\u003Cmodule-id-num>_\u003Cmodule-sku>.conf` | Always | Filename: append `_\u003Ccustom-id-file-token>_\u003Ccustom-sku>` |\n| nvfancontrol config | `rootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002Fnvfancontrol_\u003Cmodule-id-num>_\u003Cmodule-sku>_\u003Ccarrier-id-num>_\u003Ccarrier-sku>.conf` | Always | Filename: substitute carrier portion (append `_\u003Ccustom-id-file-token>_\u003Ccustom-sku>` if source is module-keyed only) |\n| `nvpower.sh` patch | `rootfs\u002Fetc\u002Fsystemd\u002Fnvpower.sh` | Always | Pristine + single customization commit with 4 insertions: (a) cvb cascade `elif [[ \"${machine}\" =~ \"\u003Ccustom-id>\" ]]; then cvb=\"\u003Ccustom-id-file-token>\"` before reference; (b) inside module-SKU branch set `machine=\"\u003Cmodule-id>-\u003Cmodule-sku>-\u003Ccustom-id>-\u003Ccustom-sku>\"`; (c) nvpmodel cascade branch for composite machine key → `conf_file=` nvpmodel fork; (d) cvb-keyed nvfancontrol cascade branch → `conf_file=` nvfancontrol fork |\n| BPMP DTB | prebuilt at `bootloader\u002Fgeneric\u002F\u003CBPFDTB_FILE>` (alt naming: no `p` prefix, `xxxx` SKU) | **Opt-in** y\u002FN, default N — module-level, usually shared with reference | Fork binary: pristine + filename sub `-\u003Ccarrier-id-num>-` → `-\u003Ccustom-id-file-token>-` (content unchanged). Extra commit on flash-conf fork rewriting `BPFDTB_FILE` to the renamed binary. |\n\n¶ **`#include` follow.** Scan each captured `.dts` for `#include\n\"...\"` directives **anywhere** in the file (NVIDIA BSPs put them\ninside BCT node bodies); carrier-keyed includes join the fork list.\nStop at one level.\n\n† **Rename rule.** Carrier-keyed source (e.g.\n`…-p3834-xxxx-p4071-0000.dts`) → filename sub\n`\u003Ccarrier-id>-\u003Ccarrier-sku>` → `\u003Ccustom-id>-\u003Ccustom-sku>`; rewrite the\nflash-conf variable (e.g. `PINMUX_CONFIG`) to the renamed filename in\nthe same customization commit. **Module portion is preserved\nverbatim from pristine** — if pristine has `p3834-xxxx`, fork keeps\n`p3834-xxxx`; if pristine has `p3834-0008`, fork keeps `p3834-0008`.\nNever pin module-SKU on your own. Same rule for any other `xxxx`\nwildcard in the carrier-SKU position when pristine uses it (e.g.\n`p4071-xxxx` → `p1234-xxxx`). Module-keyed\nsource (e.g. `…-p3767-dp-a03.dtsi`) → append\n`_\u003Ccustom-id-file-token>_\u003Ccustom-sku>` (underscore-form) or\n`-\u003Ccustom-id>-\u003Ccustom-sku>` (dash-form) **plus** an extra commit on\nflash-conf fork rewriting the variable (e.g. `PINMUX_CONFIG`) to the\nsuffixed name. Content never substituted by default; prompt if\ncontent holds a literal carrier-id-sku self-reference.\n\n‡ **Overlay skeleton.** DT plugin overlay (`\u002Fplugin\u002F;`) with one\n`fragment@0` at `target-path = \"\u002F\"`; inside `__overlay__` set\n`model = \"\u003Ccustom_carrier.name> carrier board\"` and `compatible =\n\"nvidia,\u003Ccustom-id>-\u003Ccustom-sku>+\u003Cmodule-id>-\u003Cmodule-sku>\",\n\"nvidia,\u003Cchip>\"`. `nvpower.sh` machine narrowing reads `compatible`.\n\n### Edit verification\n\nRe-grep after every `sed` \u002F patch. `sed` silently no-ops on miss;\nexit code 0 proves nothing. Multi-line replacements: use Python\n`str.replace(old, new)`, not multi-line `sed` (brittle to whitespace\ndrift, silent no-ops). Refuse to commit on verification miss.\n\n**Summary.** Print forks per repo (count + commit SHAs), BPMP-DTB\ndecision, warn-and-skipped rows (mandatory source file missing on\nthis BSP — don't fail the run), overlay path written.\n\n## Examples\n\nTrigger phrases the operator might use:\n\n```text\nderive custom carrier\nbootstrap custom carrier\nfork carrier board from reference devkit\n```\n\nMinimal `custom_carrier:` block in the active profile that the skill\nexpects to find:\n\n```yaml\ncustom_carrier:\n  id: p1234            # any token; need not be NVIDIA pNNNN style\n  sku: 0000\n  flash_config: p1234.conf\n  name: Acme Custom Carrier\n```\n\n## Purpose\n\nCustomize the per-board fileset for a new carrier board so downstream\n`customize-*` skills, `nvpower.sh`, and the boot chain land on the\ncustom carrier instead of the reference devkit. Base DTB stays at the\nreference; carrier deltas live in a DT overlay so a re-derive against\na new reference BSP only needs to re-run this skill.\n\n## Prerequisites\n\n- Active profile resolved per\n  [`target-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md)\n  with a `custom_carrier:` block (id, sku, flash-conf, friendly name).\n- `source.root_path\u002FLinux_for_Tegra\u002F.git` initialized — run\n  `\u002Fjetson-init-source` first; this skill refuses if the overlay\n  tracker is missing.\n- `bsp_image.root_path` populated by `\u002Fjetson-init-image` so the\n  reference flash-conf symlink can be resolved.\n- `reference_devkit:` populated (module + carrier) so the rename rule\n  has carrier-id\u002Fsku tokens to substitute away from.\n\n## Limitations\n\n- Kernel base DTB and its source DTS are **not** forked — carrier\n  deltas must layer through the DT overlay wired via\n  `OVERLAY_DTB_FILE`.\n- BPMP DTB fork is opt-in (default OFF). Most carrier swaps share the\n  reference BPMP DTB; only opt in when board power\u002Fclock topology\n  diverges.\n- Flash-conf content substitution is **targeted**, not blanket. Vars\n  whose files this skill does not fork (`DTB_FILE`, `TBCDTB_FILE`,\n  `SCR_CONFIG`, `PMIC_CONFIG`, `DEVICEPROD_CONFIG`, `PROD_CONFIG`,\n  `MINRATCHET_CONFIG`, `UPHY_CONFIG`, dynamic `OVERLAY_DTB_FILE+=`)\n  stay at reference values — rewriting them would point at files that\n  do not exist.\n- Custom-carrier IDs need not follow NVIDIA `pNNNN` style; the\n  p-stripped numeric token is derived only when the ID matches\n  `^p[0-9]{4}$`.\n- Does not customize module-level files. Use the relevant\n  `jetson-customize-*` skill for pinmux, clocks, fan curves,\n  nvpmodel, PCIe, UPHY, USB, MGBE, or camera deltas.\n\n## Troubleshooting\n\n- **Refuses with \"no `custom_carrier:` block\"** — declare the block in\n  the active profile before re-running; the skill will not infer it.\n- **Refuses with \".git missing in `Linux_for_Tegra\u002F`\"** — overlay\n  tracker not initialized. Run `\u002Fjetson-init-source` first.\n- **\"`\u003Creal-conf>` not a symlink\"** — NVIDIA convention is a\n  `\u003Cdevkit>.conf` symlink to `\u003Ccarrier>-\u003Cmodule>-a\u003Crev>.conf`; if the\n  top-level is the real conf, the skill warns, treats it as real, and\n  skips the symlink-wrapper row. Not an error.\n- **`sed` reported success but the edit is missing** — `sed` silently\n  no-ops on miss. The skill re-greps after every patch and refuses to\n  commit on verification miss; for multi-line replacements switch to\n  Python `str.replace`.\n- **\"chip: unknown\" \u002F fallback to `tegra234`** — module ID is not in\n  the [catalogue](..\u002F..\u002Freferences\u002Fbsp-platforms-catalogue.md); update\n  the catalogue rather than override in the profile.\n- **Commit message preview prompt blocks the run** — expected gate per\n  [commit-batching](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#commit-batching-in-the-overlay-tracker);\n  accept, edit, or cancel. On cancel the index is left staged for\n  manual resolution.\n- **A mandatory source file is missing on this BSP** — the row is\n  recorded as warn-and-skipped in the summary; the rest of the run\n  still completes.\n","# jetson-derive-carrier\n\nCustomize first-run gate for any `customize-*` skill on a custom\ncarrier. Resolve the active target per\n[`target-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md).\n**Refuse** if no `custom_carrier:` block, or if\n`\u003Csource.root_path>\u002FLinux_for_Tegra\u002F.git` is missing\n(`jetson-init-source` first). Template file create\u002Fcopy rows land in a\nsingle overlay-tracker commit and copy **directly** to the\ncustom-carrier-renamed target path — reference-named pristine files\nare never staged (see [Fork plan](#fork-plan) for the local rule, which\noverrides the standard pristine + customization split from the\n[workflow](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#commit-batching-in-the-overlay-tracker));\nconf-chain discovery follows\n[per-board conf dispatch](..\u002F..\u002Fcontext\u002Fbsp-customization-software-layers.md#per-board-conf-dispatch--update_flash_args_common).\nKernel base DTB is **not** forked — carrier deltas layer as a DT\noverlay wired via `OVERLAY_DTB_FILE`.\n\n**Identifiers** (from active profile): `\u003Cchip>` from\n`reference_devkit.module.id` via\n[catalogue](..\u002F..\u002Freferences\u002Fbsp-platforms-catalogue.md) (unknown →\nwarn, fallback `tegra234`); `\u003Cmodule-id>`\u002F`\u003Cmodule-sku>` from\n`reference_devkit.module`; `\u003Ccarrier-id>`\u002F`\u003Ccarrier-sku>` from\n`reference_devkit.carrier`; `\u003Ccustom-id>`\u002F`\u003Ccustom-sku>`\u002F\n`\u003Ccustom-flash-conf>` from `custom_carrier`. `\u003Creal-conf>` =\n`readlink \u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F\u003Creference_devkit.flash_config>`\n(NVIDIA convention `\u003Cdevkit>.conf` → `\u003Ccarrier>-\u003Cmodule>-a\u003Crev>.conf`;\nwarn + treat top-level as real + skip symlink-wrapper row if not a\nsymlink).\n\n`\u003Ccustom-id>` is a custom carrier board token, not necessarily an\nNVIDIA-style `pNNNN` ID. Use it verbatim in dash-form filenames and DT\ncompatible strings. When a target file family uses p-stripped numeric\ntokens, derive `\u003Ccustom-id-file-token>` as `NNNN` only if `\u003Ccustom-id>`\nmatches `^p[0-9]{4}$`; otherwise use `\u003Ccustom-id>` unchanged. Do not\nreject custom carrier IDs merely because they do not start with `p`.\n\n## Instructions\n\nThe fork plan below is the instruction set: one discovery pass, then a\nrow-by-row fork of the per-board fileset, gated by the commit-message\npreview before each `git commit`.\n\n### Fork plan\n\nEvery `git commit` produced by this skill — in the overlay tracker\n(`Linux_for_Tegra\u002F`) or the `hardware\u002F` source repo — runs through\nthe\n[commit message preview gate](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#commit-message-preview-gate).\nSurface the staged file list + proposed message to the operator\nand require accept \u002F edit \u002F cancel before each `git commit`; on\n**cancel** leave the index staged for manual resolution.\n\n**Materialize renamed forks even when bytes do not change.** For every\naccepted fork-plan row, create and track the custom-carrier target path;\ndo not skip a missing target because the fork is only a rename\u002Fcopy or is\nbyte-identical to the reference. This includes BCT forks such as pinmux,\nGPIO\u002FGPIOINT, padvoltage\u002FPMC, misc, and MB2 misc. Skip only when the\nAcceptance column allows it, the source is an explicit warn-and-skip\nmiss, or the expected target path is already tracked; in the last case,\nreport it as already derived and do not create an empty commit.\n\n**Template file create\u002Fcopy rows squash into one overlay-tracker\ncommit, and reference-named pristine files are never staged.** All\nrows that materialize a new (template-derived) file in the overlay\ntracker — board flash-conf, flash-conf symlink, MB1 BCT (pinmux,\nGPIO\u002FGPIOINT, padvoltage\u002FPMC, misc), MB2 BCT (misc), BPMP DTB (when\nopted in), nvpmodel, nvfancontrol — copy **directly** from\n`\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F\u003Crel>\u002F\u003Creference-name>` to\n`\u003Csource.root_path>\u002FLinux_for_Tegra\u002F\u003Crel>\u002F\u003Ccustom-name>` with any\ncontent edits applied before staging. The reference-named\n(`\u003Ccarrier-id>-\u003Ccarrier-sku>`-keyed) filename is never staged or\ncommitted in the overlay tracker — only the custom-carrier-renamed\nfile is tracked. This overrides the standard pristine + customization\nsplit from\n[commit batching](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#commit-batching-in-the-overlay-tracker).\nAll such rows land in a **single** overlay-tracker commit that adds:\n(i) the custom-carrier-named files at their target paths with content\nalready applied, (ii) the flash-conf symlink, and (iii) the targeted\nflash-conf content rewrites inside the renamed flash-conf for\n`PINMUX_CONFIG` \u002F `GPIO_CONFIG` \u002F `GPIOINT_CONFIG` \u002F `PMC_CONFIG` \u002F\n`MISC_CONFIG` \u002F `MB2_BCT` (plus `BPFDTB_FILE` when BPMP DTB is opted\nin). Rows that edit existing upstream files instead of creating\ntemplates — the `nvpower.sh` patch — and the overlay wire-up\n(`OVERLAY_DTB_FILE+=` append to the just-created flash-conf fork,\ntreated as a temporally distinct phase per\n[commit batching](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#commit-batching-in-the-overlay-tracker))\nremain separate commits per their own rows. The DT overlay skeleton\ncommits in `bsp_sources\u002Fhardware\u002F`, not the overlay tracker, so it is\nunaffected. The commit message preview gate fires once on the\nsquashed commit; warn-and-skipped rows do not contribute, and if every\nrow in the bundle is already tracked the commit is omitted entirely.\n\n### Discovery (single batched pass)\n\nRun **one** discovery pass; do not interleave with staging. **Do not\ntruncate listings** — every candidate filename in each scanned\ndirectory must be visible to the matcher. `head`, `tail`, `| head -N`,\n`| tail -N`, and any other row-limiting filter are out of bounds for\nthis step; use `ls -1` \u002F `find` unclipped, or grep on the full output.\nTruncating risks false warn-and-skip calls when the matching file\nsits past the cutoff. Capture:\n\n- Flash-conf vars: `DTB_FILE` \u002F `TBCDTB_FILE` \u002F `BPFDTB_FILE` \u002F\n  `PINMUX_CONFIG` \u002F `PMC_CONFIG` \u002F `GPIO_CONFIG` \u002F `GPIOINT_CONFIG`.\n  `DTB_FILE` \u002F `TBCDTB_FILE` are captured for **reference only** so\n  the overlay wire-up can derive `\u003Cdtb-stem>` for the overlay\n  filename — they are never rewritten by this skill.\n- BCT `.dts` at `bootloader\u002Fgeneric\u002FBCT\u002F`; `.dtsi` siblings live\n  **one level up at `bootloader\u002F`** — NOT alongside.\n- nvpmodel: `nvpmodel_\u003Cmodule-id>_\u003Cmodule-sku>*.conf`. nvfancontrol:\n  `nvfancontrol_\u003Cmodule-id>_\u003Cmodule-sku>_\u003Ccarrier-id>_\u003Ccarrier-sku>.conf`.\n- `nvpower.sh` anchors for (a)–(d): `\u003Ccarrier-id>` cvb branch,\n  `\u003Cmodule-id>-\u003Cmodule-sku>` SKU `elif`, `tegra\u003Cchip>` nvpmodel\n  cascade, `tegra\u003Cchip>` nvfancontrol cascade.\n\n| File \u002F category | Discovery | Acceptance | Fork rule |\n|---|---|---|---|\n| Board flash conf | `\u003Creal-conf>` | Always | Filename sub `\u003Ccarrier-id>-\u003Ccarrier-sku>` → `\u003Ccustom-id>-\u003Ccustom-sku>`. Content sub is **targeted, not blanket**: rewrite RHS only for vars whose file this skill forks — `PINMUX_CONFIG`, `PMC_CONFIG`, `GPIO_CONFIG` \u002F `GPIOINT_CONFIG`, `MISC_CONFIG`, `MB2_BCT`. Other carrier-keyed vars (`DTB_FILE`, `TBCDTB_FILE`, `SCR_CONFIG`, `PMIC_CONFIG`, `DEVICEPROD_CONFIG`, `PROD_CONFIG`, `MINRATCHET_CONFIG`, `UPHY_CONFIG`, dynamic `OVERLAY_DTB_FILE+=`) MUST stay at reference values — their files aren't forked here and a blanket `sed` would point them at nonexistent files. `DTB_FILE` \u002F `TBCDTB_FILE` specifically: base DTB is not forked; the overlay row appends a new `OVERLAY_DTB_FILE+=` line instead. `BPFDTB_FILE`: opt-in extra commit. Never touch `\u003Cchip>`, `\u003Cmodule-id>`, `xxxx`. |\n| Flash-conf symlink | Unconditional | Always (skip if `\u003Creal-conf>` not a symlink) | New symlink `\u003Ccustom-flash-conf>` → flash-conf fork |\n| MB1 BCT pinmux | `PINMUX_CONFIG` + `#include` follow ¶ | Always | Rename rule † |\n| MB1 BCT GPIO | `GPIO_CONFIG`\u002F`GPIOINT_CONFIG` + `#include` follow ¶ | Always | Rename rule † |\n| MB1 BCT padvoltage | `PMC_CONFIG` + `#include` follow ¶ | Always | Rename rule † |\n| MB1 BCT misc | `MISC_CONFIG` + `#include` follow ¶ | Always | Rename rule † |\n| MB2 BCT misc | `MB2_BCT` + `#include` follow ¶ | Always | Rename rule † |\n| Kernel DTB + source DTS | (reference only — see header) | Never forked | Base DTB stays at reference. No pristine binary copy in the overlay tracker; no source DTS fork in `bsp_sources\u002Fhardware\u002F`. Carrier deltas live entirely in the DT overlay (next row). |\n| DT overlay skeleton (NEW) | Unconditional | Always | Create `\u003Csource.root_path>\u002Fhardware\u002Fnvidia\u002F\u003Cchip>\u002Fnv-public\u002Foverlay\u002F\u003Cchip>-\u003Ccustom-id>-\u003Ccustom-sku>+\u003Cmodule-id>-\u003Cmodule-sku>.dts` (skeleton ‡); commit in `hardware\u002F`, push to origin |\n| Per-dir Makefile registration | `\u003Csource.root_path>\u002Fbsp_sources\u002Fhardware\u002Fnvidia\u002F\u003Cchip>\u002Fnv-public\u002Foverlay\u002FMakefile` | Always | Append `dtbo-y += \u003Cchip>-\u003Ccustom-id>-\u003Ccustom-sku>+\u003Cmodule-id>-\u003Cmodule-sku>.dtbo` after the **last literal-named** `dtbo-y +=` entry (BEFORE the `$(addprefix $(makefile-path)\u002F,$(dtbo-y))` prefix block — inserting after `dtbo-y += $(old-dtbo)` silently drops the .dtbo). Same position-sensitive idiom and snippet as the composite slot's Makefile patch in [`..\u002Fjetson-build-source\u002Freferences\u002Fcomposite-registration.md#makefile-patch-idempotent-position-sensitive`](..\u002Fjetson-build-source\u002Freferences\u002Fcomposite-registration.md#makefile-patch-idempotent-position-sensitive). Commit in `hardware\u002F`. Without this row, `nvidia-dtbs` never produces the `.dtbo` referenced by the next row's `OVERLAY_DTB_FILE+=` line and `flash.sh` aborts mid-flash on the missing file. |\n| Overlay wire-up | Unconditional | Always | Append `OVERLAY_DTB_FILE+=\",\u003Cchip>-\u003Ccustom-id>-\u003Ccustom-sku>+\u003Cmodule-id>-\u003Cmodule-sku>.dtbo\"` to flash-conf fork (extra commit) |\n| nvpmodel config | `rootfs\u002Fetc\u002Fnvpmodel\u002Fnvpmodel_\u003Cmodule-id-num>_\u003Cmodule-sku>.conf` | Always | Filename: append `_\u003Ccustom-id-file-token>_\u003Ccustom-sku>` |\n| nvfancontrol config | `rootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002Fnvfancontrol_\u003Cmodule-id-num>_\u003Cmodule-sku>_\u003Ccarrier-id-num>_\u003Ccarrier-sku>.conf` | Always | Filename: substitute carrier portion (append `_\u003Ccustom-id-file-token>_\u003Ccustom-sku>` if source is module-keyed only) |\n| `nvpower.sh` patch | `rootfs\u002Fetc\u002Fsystemd\u002Fnvpower.sh` | Always | Pristine + single customization commit with 4 insertions: (a) cvb cascade `elif [[ \"${machine}\" =~ \"\u003Ccustom-id>\" ]]; then cvb=\"\u003Ccustom-id-file-token>\"` before reference; (b) inside module-SKU branch set `machine=\"\u003Cmodule-id>-\u003Cmodule-sku>-\u003Ccustom-id>-\u003Ccustom-sku>\"`; (c) nvpmodel cascade branch for composite machine key → `conf_file=` nvpmodel fork; (d) cvb-keyed nvfancontrol cascade branch → `conf_file=` nvfancontrol fork |\n| BPMP DTB | prebuilt at `bootloader\u002Fgeneric\u002F\u003CBPFDTB_FILE>` (alt naming: no `p` prefix, `xxxx` SKU) | **Opt-in** y\u002FN, default N — module-level, usually shared with reference | Fork binary: pristine + filename sub `-\u003Ccarrier-id-num>-` → `-\u003Ccustom-id-file-token>-` (content unchanged). Extra commit on flash-conf fork rewriting `BPFDTB_FILE` to the renamed binary. |\n\n¶ **`#include` follow.** Scan each captured `.dts` for `#include\n\"...\"` directives **anywhere** in the file (NVIDIA BSPs put them\ninside BCT node bodies); carrier-keyed includes join the fork list.\nStop at one level.\n\n† **Rename rule.** Carrier-keyed source (e.g.\n`…-p3834-xxxx-p4071-0000.dts`) → filename sub\n`\u003Ccarrier-id>-\u003Ccarrier-sku>` → `\u003Ccustom-id>-\u003Ccustom-sku>`; rewrite the\nflash-conf variable (e.g. `PINMUX_CONFIG`) to the renamed filename in\nthe same customization commit. **Module portion is preserved\nverbatim from pristine** — if pristine has `p3834-xxxx`, fork keeps\n`p3834-xxxx`; if pristine has `p3834-0008`, fork keeps `p3834-0008`.\nNever pin module-SKU on your own. Same rule for any other `xxxx`\nwildcard in the carrier-SKU position when pristine uses it (e.g.\n`p4071-xxxx` → `p1234-xxxx`). Module-keyed\nsource (e.g. `…-p3767-dp-a03.dtsi`) → append\n`_\u003Ccustom-id-file-token>_\u003Ccustom-sku>` (underscore-form) or\n`-\u003Ccustom-id>-\u003Ccustom-sku>` (dash-form) **plus** an extra commit on\nflash-conf fork rewriting the variable (e.g. `PINMUX_CONFIG`) to the\nsuffixed name. Content never substituted by default; prompt if\ncontent holds a literal carrier-id-sku self-reference.\n\n‡ **Overlay skeleton.** DT plugin overlay (`\u002Fplugin\u002F;`) with one\n`fragment@0` at `target-path = \"\u002F\"`; inside `__overlay__` set\n`model = \"\u003Ccustom_carrier.name> carrier board\"` and `compatible =\n\"nvidia,\u003Ccustom-id>-\u003Ccustom-sku>+\u003Cmodule-id>-\u003Cmodule-sku>\",\n\"nvidia,\u003Cchip>\"`. `nvpower.sh` machine narrowing reads `compatible`.\n\n### Edit verification\n\nRe-grep after every `sed` \u002F patch. `sed` silently no-ops on miss;\nexit code 0 proves nothing. Multi-line replacements: use Python\n`str.replace(old, new)`, not multi-line `sed` (brittle to whitespace\ndrift, silent no-ops). Refuse to commit on verification miss.\n\n**Summary.** Print forks per repo (count + commit SHAs), BPMP-DTB\ndecision, warn-and-skipped rows (mandatory source file missing on\nthis BSP — don't fail the run), overlay path written.\n\n## Examples\n\nTrigger phrases the operator might use:\n\n```text\nderive custom carrier\nbootstrap custom carrier\nfork carrier board from reference devkit\n```\n\nMinimal `custom_carrier:` block in the active profile that the skill\nexpects to find:\n\n```yaml\ncustom_carrier:\n  id: p1234            # any token; need not be NVIDIA pNNNN style\n  sku: 0000\n  flash_config: p1234.conf\n  name: Acme Custom Carrier\n```\n\n## Purpose\n\nCustomize the per-board fileset for a new carrier board so downstream\n`customize-*` skills, `nvpower.sh`, and the boot chain land on the\ncustom carrier instead of the reference devkit. Base DTB stays at the\nreference; carrier deltas live in a DT overlay so a re-derive against\na new reference BSP only needs to re-run this skill.\n\n## Prerequisites\n\n- Active profile resolved per\n  [`target-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md)\n  with a `custom_carrier:` block (id, sku, flash-conf, friendly name).\n- `source.root_path\u002FLinux_for_Tegra\u002F.git` initialized — run\n  `\u002Fjetson-init-source` first; this skill refuses if the overlay\n  tracker is missing.\n- `bsp_image.root_path` populated by `\u002Fjetson-init-image` so the\n  reference flash-conf symlink can be resolved.\n- `reference_devkit:` populated (module + carrier) so the rename rule\n  has carrier-id\u002Fsku tokens to substitute away from.\n\n## Limitations\n\n- Kernel base DTB and its source DTS are **not** forked — carrier\n  deltas must layer through the DT overlay wired via\n  `OVERLAY_DTB_FILE`.\n- BPMP DTB fork is opt-in (default OFF). Most carrier swaps share the\n  reference BPMP DTB; only opt in when board power\u002Fclock topology\n  diverges.\n- Flash-conf content substitution is **targeted**, not blanket. Vars\n  whose files this skill does not fork (`DTB_FILE`, `TBCDTB_FILE`,\n  `SCR_CONFIG`, `PMIC_CONFIG`, `DEVICEPROD_CONFIG`, `PROD_CONFIG`,\n  `MINRATCHET_CONFIG`, `UPHY_CONFIG`, dynamic `OVERLAY_DTB_FILE+=`)\n  stay at reference values — rewriting them would point at files that\n  do not exist.\n- Custom-carrier IDs need not follow NVIDIA `pNNNN` style; the\n  p-stripped numeric token is derived only when the ID matches\n  `^p[0-9]{4}$`.\n- Does not customize module-level files. Use the relevant\n  `jetson-customize-*` skill for pinmux, clocks, fan curves,\n  nvpmodel, PCIe, UPHY, USB, MGBE, or camera deltas.\n\n## Troubleshooting\n\n- **Refuses with \"no `custom_carrier:` block\"** — declare the block in\n  the active profile before re-running; the skill will not infer it.\n- **Refuses with \".git missing in `Linux_for_Tegra\u002F`\"** — overlay\n  tracker not initialized. Run `\u002Fjetson-init-source` first.\n- **\"`\u003Creal-conf>` not a symlink\"** — NVIDIA convention is a\n  `\u003Cdevkit>.conf` symlink to `\u003Ccarrier>-\u003Cmodule>-a\u003Crev>.conf`; if the\n  top-level is the real conf, the skill warns, treats it as real, and\n  skips the symlink-wrapper row. Not an error.\n- **`sed` reported success but the edit is missing** — `sed` silently\n  no-ops on miss. The skill re-greps after every patch and refuses to\n  commit on verification miss; for multi-line replacements switch to\n  Python `str.replace`.\n- **\"chip: unknown\" \u002F fallback to `tegra234`** — module ID is not in\n  the [catalogue](..\u002F..\u002Freferences\u002Fbsp-platforms-catalogue.md); update\n  the catalogue rather than override in the profile.\n- **Commit message preview prompt blocks the run** — expected gate per\n  [commit-batching](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#commit-batching-in-the-overlay-tracker);\n  accept, edit, or cancel. On cancel the index is left staged for\n  manual resolution.\n- **A mandatory source file is missing on this BSP** — the row is\n  recorded as warn-and-skipped in the summary; the rest of the run\n  still completes.\n",{"name":5,"license":15,"version":24,"metadata":25,"description":7},"0.0.1",{"tags":26,"author":31,"domain":32,"data-classification":33},[27,28,29,30],"target-platform","custom-carrier","bring-up","setup","Jetson Team","meta","public","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fnvidia-skills\u002Fjetson-derive-carrier",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill jetson-derive-carrier",{"tool":48,"command":49},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill jetson-derive-carrier",{"tool":51,"command":52},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill jetson-derive-carrier","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fjetson-derive-carrier\u002FSkill.md",true,[56],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"metadata.json","REFERENCE","参考文档",433,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fjetson-derive-carrier\u002Fmetadata.json",[63,71,76,83,88,95],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":72,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\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":67,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":84,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\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":67,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":96,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]