ワンクリックでManusで任意のスキルを実行

jlcpcb-component-finder

スター10

フォーク2

更新日2026年6月8日 04:01

Search the JLCPCB electronic components database (~7M parts) for hardware projects. Use when: (1) Finding components (resistors, capacitors, inductors, ICs, connectors, diodes, transistors, MOSFETs, op-amps, microcontrollers, sensors, LEDs, voltage regulators, audio jacks, etc.), (2) Looking up part numbers, LCSC (C-prefix), or manufacturer part numbers, (3) Finding alternatives/equivalents, (4) Checking stock at JLCPCB/LCSC, (5) Getting specs (package, footprint), (6) Searching SMD or through-hole parts. Keywords: JLCPCB, LCSC, PCB parts, SMT, PCBA, BOM, component sourcing.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

Takazudo

Takazudo/claude-resources

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

JLCPCB Parts Finder

Search ~7 million electronic components in the local JLCPCB database.

Database

Path: $HOME/.jlcpcb-db/cache.sqlite3 (~5 GB, yaqwsx/jlcparts source-db-v2 schema: table jlc_components)
Override the path with the JLCPCB_DB_PATH env var if needed
If missing, tell the user to run /jlcpcb-component-finder-update-db

Query Script

All queries use: node $HOME/.claude/skills/jlcpcb-component-finder/query.js <command>

Commands

Command	Usage	Description
`db-info`	`node query.js db-info`	Show DB stats (total parts, categories, stock count, DB date)
`list-categories`	`node query.js list-categories [keyword]`	List categories, optionally filtered by keyword
`search-parts`	`node query.js search-parts <category> [keyword] [limit]`	Search within a category (category is a NAME substring, matched against category/subcategory)
`search-all`	`node query.js search-all <keyword> [limit]`	Search across ALL categories by keyword
`lookup`	`node query.js lookup <lcsc_number>`	Look up a specific part by LCSC number (e.g. C12084)

Examples

# Check database status
node $HOME/.claude/skills/jlcpcb-component-finder/query.js db-info

# Find audio-related categories
node $HOME/.claude/skills/jlcpcb-component-finder/query.js list-categories "audio"

# Search for 3.5mm audio jacks within the "Audio" category
node $HOME/.claude/skills/jlcpcb-component-finder/query.js search-parts "Audio" "3.5" 10

# Search for CH340 across all categories
node $HOME/.claude/skills/jlcpcb-component-finder/query.js search-all "CH340" 10

# Look up a specific part
node $HOME/.claude/skills/jlcpcb-component-finder/query.js lookup C12084

Workflow

Understand request - What component does the user need?
Find category - Use list-categories [keyword] or search-all for quick discovery
Search parts - Use search-parts with a category name, or search-all for cross-category
Present results with LCSC number, manufacturer, description, package, stock, price, and URL

Output Fields

Each result includes:

LCSC number (C-prefix, e.g. C12084)
Manufacturer and description
Package type (e.g. SOP-8, 0805)
Stock availability (sorted highest first)
Basic/Preferred tags - Basic parts have lower assembly fees at JLCPCB
Price tiers (quantity breaks)
Datasheet URL (when available)
Detail page URL: https://jlcpcb.com/partdetail/C{number}

Tips

Basic parts have the lowest JLCPCB assembly fee - prefer these when possible
Preferred parts are commonly used and well-stocked
Start with broader keywords if specific searches return no results
Use search-all when you don't know the category
Use list-categories with a keyword to discover category names
Limit initial searches to 10-20 results to avoid overwhelming output
Results are sorted by stock (descending) - highest stock = most available
Always include the detail page URL in recommendations

このリポジトリの他の Skills

同じリポジトリ

issue-sweep

Takazudo/claude-resources

Sweep open GitHub issues — optionally narrowed by label — and drive each to completion via `/big-plan -m -a`. Collects candidates, triages out work that needs careful human judgment, confirms once, then handles the rest autonomously one issue at a time. Use when: (1) User says '/issue-sweep', 'sweep issues', 'sweep open issues', 'handle the open issues', 'clear the issue backlog', or 'do the issues', (2) The user wants to batch-process a label's worth of issues (e.g. `agent-found`, `mac`), (3) After a work round that left a pile of follow-up issues. Options: "`-f`/`--filter LABEL` keeps only issues carrying that label; `-ex`/`--exclude LABEL`" drops issues carrying it; with no options it sweeps ALL open issues. Locally-checkable "verify X" tasks are verified directly and closed (not run through `/big-plan`). Skips issues that need careful human judgment (huge multi-major version bumps, super-big epics, design calls); verification tasks that can't be auto-verified locally (auth/deploy/external/subjective) are

2026-06-2510

codex-imagegen

Takazudo/claude-resources

Generate or redesign raster images (PNG mockups, illustrations, photos, UI design polish) from inside Claude Code by driving Codex CLI's built-in $imagegen, billed to ChatGPT-included usage instead of per-image OpenAI API charges. Use whenever the user wants to create/generate an image, make a mockup or illustration, produce a photo, polish or redesign a UI from a screenshot, or get a PNG out of a session — even if they don't mention Codex or "imagegen". This is the preferred image-generation path because Anthropic models cannot generate raster images and this route avoids API billing.

2026-06-2210

design-polish-loop

Takazudo/claude-resources

Iterative visual design-polish loop for an existing or WIP web UI. Each round: capture the live page as screenshots, judge it from the rendered pixels, and apply CSS polish toward a better-looking target using /css-wisdom's tight-token strategy — then re-capture and compare. The target direction is set by codex-imagegen 'north-star' mockups generated from the current screenshot, so the loop pursues a genuinely better look instead of nudging the existing one in place. Use when: (1) user says 'design-polish-loop', 'polish loop', 'polish this page/design/UI', (2) user wants to level up / upgrade the look of a current design or WIP project, (3) user wants AI-proposed redesign directions applied to a real rendering page, (4) user calls a design plain, dated, flat, or unpolished and wants it improved. Main use case: improving the current design of a WIP project. It polishes what already renders — not brand-new-from-scratch pages.

2026-06-2210

dev-bump-zudo-deps

Takazudo/claude-resources

Bump every `@takazudo/*` registry dependency in the current project to its newest version, resolving each by the channel it currently tracks. Use when: (1) User says '/dev-bump-zudo-deps', 'bump zudo deps', 'bump the @takazudo packages', 'update zfb', 'update zudo-doc', or 'update the takazudo toolchain to latest', (2) A new `@takazudo/*` prerelease or release has shipped and this project should adopt it, (3) Routine first-party dependency-update rounds. Resolution rule: a dep currently on the `next` prerelease line (`0.1.0-next.N`) → newest `next` release; a dep on the literal `latest` tag → `dist-tags.latest`; a plain stable semver → newest stable. Skips `workspace:`/`file:`/`link:` specs and leaves operator style (exact / `^` / `~`) and prerelease channel intact. A bundled script does the discovery + semver resolution; this skill drives install + verify + report.

2026-06-2210

big-plan

Takazudo/claude-resources

Plan implementation by breaking work into one epic GitHub issue + child sub-issues. Use when: (1) User says '/big-plan', (2) User wants to plan an implementation before coding, (3) User wants to split a feature into small issues for parallel agent team work, (4) User references existing issues (e.g. 'implement issue #123', 'plan all open issues', 'plan recent 3 open issues'). Auto-reads project-scope l-lessons-* skills (from /retro-notes) before planning. Codex (-co) is the DEFAULT Step 5 plan reviewer — it runs even when no reviewer flag is passed; -op/-gco add more second opinions (runnable in parallel). Use -a/--auto to run the chain autonomously: skip the Step 6 confirmation wait (pausing only when something needs careful consideration), auto-create the issues, then auto-invoke the implementation skill in the same session — /x-wt-teams for a multi-sub-issue plan, /x-as-pr for a single-sub-issue plan — forwarding -a so multi-wave plans auto-chain wave after wave. Use -m/--merge to also merge the final PR i

2026-06-1810

dev-purge-gh-cache

Takazudo/claude-resources

Purge GitHub Actions caches across every non-archived repo for one or more GitHub owners (users or orgs). Use when (1) the user says "purge gh cache", "clear actions cache", "delete CI cache", or invokes /dev-purge-gh-cache, (2) the user wants to free up GitHub Actions cache storage for an account/org, (3) the user names one or more GitHub owners (e.g. "Takazudo", "zudolab") and asks to wipe their Actions caches. Handles fan-out across all repos, parallel survey, bulk delete, and real-time verification.

2026-06-1810

name	jlcpcb-component-finder
description	Search the JLCPCB electronic components database (~7M parts) for hardware projects. Use when: (1) Finding components (resistors, capacitors, inductors, ICs, connectors, diodes, transistors, MOSFETs, op-amps, microcontrollers, sensors, LEDs, voltage regulators, audio jacks, etc.), (2) Looking up part numbers, LCSC (C-prefix), or manufacturer part numbers, (3) Finding alternatives/equivalents, (4) Checking stock at JLCPCB/LCSC, (5) Getting specs (package, footprint), (6) Searching SMD or through-hole parts. Keywords: JLCPCB, LCSC, PCB parts, SMT, PCBA, BOM, component sourcing.
allowed-tools	["Bash"]

JLCPCB Parts Finder

Search ~7 million electronic components in the local JLCPCB database.

Database

Path: $HOME/.jlcpcb-db/cache.sqlite3 (~5 GB, yaqwsx/jlcparts source-db-v2 schema: table jlc_components)
Override the path with the JLCPCB_DB_PATH env var if needed
If missing, tell the user to run /jlcpcb-component-finder-update-db

Query Script

All queries use: node $HOME/.claude/skills/jlcpcb-component-finder/query.js <command>

Commands

Command	Usage	Description
`db-info`	`node query.js db-info`	Show DB stats (total parts, categories, stock count, DB date)
`list-categories`	`node query.js list-categories [keyword]`	List categories, optionally filtered by keyword
`search-parts`	`node query.js search-parts <category> [keyword] [limit]`	Search within a category (category is a NAME substring, matched against category/subcategory)
`search-all`	`node query.js search-all <keyword> [limit]`	Search across ALL categories by keyword
`lookup`	`node query.js lookup <lcsc_number>`	Look up a specific part by LCSC number (e.g. C12084)

Examples

# Check database status
node $HOME/.claude/skills/jlcpcb-component-finder/query.js db-info

# Find audio-related categories
node $HOME/.claude/skills/jlcpcb-component-finder/query.js list-categories "audio"

# Search for 3.5mm audio jacks within the "Audio" category
node $HOME/.claude/skills/jlcpcb-component-finder/query.js search-parts "Audio" "3.5" 10

# Search for CH340 across all categories
node $HOME/.claude/skills/jlcpcb-component-finder/query.js search-all "CH340" 10

# Look up a specific part
node $HOME/.claude/skills/jlcpcb-component-finder/query.js lookup C12084

Workflow

Understand request - What component does the user need?
Find category - Use list-categories [keyword] or search-all for quick discovery
Search parts - Use search-parts with a category name, or search-all for cross-category
Present results with LCSC number, manufacturer, description, package, stock, price, and URL

Output Fields

Each result includes:

LCSC number (C-prefix, e.g. C12084)
Manufacturer and description
Package type (e.g. SOP-8, 0805)
Stock availability (sorted highest first)
Basic/Preferred tags - Basic parts have lower assembly fees at JLCPCB
Price tiers (quantity breaks)
Datasheet URL (when available)
Detail page URL: https://jlcpcb.com/partdetail/C{number}

Tips

Basic parts have the lowest JLCPCB assembly fee - prefer these when possible
Preferred parts are commonly used and well-stocked
Start with broader keywords if specific searches return no results
Use search-all when you don't know the category
Use list-categories with a keyword to discover category names
Limit initial searches to 10-20 results to avoid overwhelming output
Results are sorted by stock (descending) - highest stock = most available
Always include the detail page URL in recommendations