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.

Jump to install

Repository: Takazudo/zudo-led-lamp
Last source activity: August 2, 2026 at 20:55
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Takazudo/zudo-led-lamp --skill component-example

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

8 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

component-spec-audit

Audit exact electronic-component identities and run the end-to-end workflow for adding or replacing a BOM part. Use whenever circuit, schematic, PCB, BOM, firmware, bring-up, substitution, or related documentation could depend on a component rating, pin, package, source, preview, publication, or interaction.

2026-08-02

zudo-doc-navigation-design

Navigation design rules for the zudo-led-lamp doc site (zudo-doc). Consult before creating new pages, restructuring directories, or changing header navigation. Covers: 3-level hierarchy (header → sidebar → nested), file-structure-is-navigation principle, header nav conciseness, category index pages, sidebar_position discipline, the generated claude* categories, and common mistakes. Triggered by 'nav design', 'navigation structure', 'zudo-doc-navigation-design', 'structure nav', 'add category', 'add header nav', 'add a doc page'.

2026-08-02

circuit-spec-integration

Audit cross-component circuit behavior, evidence chains, substitutions, startup, rails, protection, sensing, firmware assumptions, thermal limits, and as-built state. Use whenever a question spans multiple exact component skills or changes USB-PD/NVM, either converter stage, MCU/LED/NTC behavior, harnesses, PCB/BOM/CPL identity, or bench claims.

2026-08-02

View all from this repository

name	component-example
description	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.

Exact component record

Run the central validator, read every local JSON record, and cite fact/source IDs with conditions and locators. Preserve SOURCE UNAVAILABLE and UNSOURCED; never replace exact-orderable evidence with memory or same-name vendor data. Keep this owner aligned with its manifest.json, sources.json, facts.json, coverage.json, routing.json, interactions.json, and pin-map.json; its inventory line, direct-routing fixture, real-pin lock, and any applicable cross-component forward test.

Human component reference

Human projection of this bundle: rec-example. Replace this with one link for every owned record, then link the component catalog and cross-component rules. These pages are generated from this bundle's JSON files and add nothing to them.

component-example

Source facts

Install options

Review the source files

More from this repository

More from this repository

Exact component record

Human component reference

Exact component record

Human component reference