Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

jlcpcb-component-finder-update-db

Sterne10

Forks2

Aktualisiert8. Juni 2026 um 04:01

Download or update the JLCPCB electronic components database for the jlcpcb-component-finder skill. Use when: (1) User says 'update jlcpcb db', 'download jlcpcb database', 'refresh parts database', (2) The jlcpcb-component-finder skill reports database not found, (3) User wants to get the latest component data from JLCPCB/LCSC, (4) User says 'update db', 'update parts db'. Downloads ~0.6 GB split-zip (~5 GB installed) from yaqwsx.github.io/jlcparts.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

Takazudo

Takazudo/claude-resources

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	jlcpcb-component-finder-update-db
description	Download or update the JLCPCB electronic components database for the jlcpcb-component-finder skill. Use when: (1) User says 'update jlcpcb db', 'download jlcpcb database', 'refresh parts database', (2) The jlcpcb-component-finder skill reports database not found, (3) User wants to get the latest component data from JLCPCB/LCSC, (4) User says 'update db', 'update parts db'. Downloads ~0.6 GB split-zip (~5 GB installed) from yaqwsx.github.io/jlcparts.
allowed-tools	["Bash"]

DO NOT auto-invoke this skill. This downloads ~0.6 GB and writes a ~5 GB database. Always ask for user confirmation before proceeding.

JLCPCB Database Updater

Download or update the JLCPCB parts database (~5 GB installed, ~7 million components). Upstream now ships the slim source-db-v2 format (table jlc_components); the old v1 format bundled a ~20 GB raw-payload table — this script drops it if it ever reappears.

Prerequisites

curl - for downloading files
7z (p7zip) - for extracting split-zip archives. Install: brew install p7zip
sqlite3 - for the defensive slim-down step. Install: brew install sqlite

Update Script

Run the automated update script:

bash $HOME/.claude/skills/jlcpcb-component-finder-update-db/scripts/update-db.sh

This script will:

Check prerequisites (curl, 7z, sqlite3)
Discover and download split-zip files from https://yaqwsx.github.io/jlcparts/data/
Extract cache.sqlite3 using 7z
Back up existing database (if any) to cache.sqlite3.bak
Install new database to $HOME/.jlcpcb-db/cache.sqlite3
Drop the legacy jlcpcb_component_details payload table if present (no-op on v2) + VACUUM
Remove the previous cache.sqlite3.bak so backups don't pile up
Clean up temporary files

Important Notes

Download size: ~0.6 GB compressed (12×50 MB split parts + a final ~13 MB zip)
Installed size: ~5 GB (source-db-v2); the old v1 format was ~26 GB due to a raw-payload table
Download time: usually a minute or two on a decent connection
Disk space needed: during the transition you briefly hold the old DB + new DB; the script

removes the .bak automatically after install
If the download fails partway, re-run the script - it cleans up partial downloads

Data Source

Database from JLC Parts by Jan Mrazek. Updated periodically from JLCPCB/LCSC component data.

Verify After Update

node $HOME/.claude/skills/jlcpcb-component-finder/query.js db-info

Manual Update (Alternative)

If the script doesn't work, download manually:

Visit https://yaqwsx.github.io/jlcparts/
Download all cache.z* and cache.zip files
Extract: 7z x cache.zip
Move: mv cache.sqlite3 $HOME/.jlcpcb-db/

Mehr aus diesem Repository

gleiches Repository

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-update-db
description	Download or update the JLCPCB electronic components database for the jlcpcb-component-finder skill. Use when: (1) User says 'update jlcpcb db', 'download jlcpcb database', 'refresh parts database', (2) The jlcpcb-component-finder skill reports database not found, (3) User wants to get the latest component data from JLCPCB/LCSC, (4) User says 'update db', 'update parts db'. Downloads ~0.6 GB split-zip (~5 GB installed) from yaqwsx.github.io/jlcparts.
allowed-tools	["Bash"]

DO NOT auto-invoke this skill. This downloads ~0.6 GB and writes a ~5 GB database. Always ask for user confirmation before proceeding.

JLCPCB Database Updater

Prerequisites

curl - for downloading files
7z (p7zip) - for extracting split-zip archives. Install: brew install p7zip
sqlite3 - for the defensive slim-down step. Install: brew install sqlite

Update Script

Run the automated update script:

bash $HOME/.claude/skills/jlcpcb-component-finder-update-db/scripts/update-db.sh

This script will:

Check prerequisites (curl, 7z, sqlite3)
Discover and download split-zip files from https://yaqwsx.github.io/jlcparts/data/
Extract cache.sqlite3 using 7z
Back up existing database (if any) to cache.sqlite3.bak
Install new database to $HOME/.jlcpcb-db/cache.sqlite3
Drop the legacy jlcpcb_component_details payload table if present (no-op on v2) + VACUUM
Remove the previous cache.sqlite3.bak so backups don't pile up
Clean up temporary files

Important Notes

Download size: ~0.6 GB compressed (12×50 MB split parts + a final ~13 MB zip)
Installed size: ~5 GB (source-db-v2); the old v1 format was ~26 GB due to a raw-payload table
Download time: usually a minute or two on a decent connection
Disk space needed: during the transition you briefly hold the old DB + new DB; the script

removes the .bak automatically after install
If the download fails partway, re-run the script - it cleans up partial downloads

Data Source

Database from JLC Parts by Jan Mrazek. Updated periodically from JLCPCB/LCSC component data.

Verify After Update

node $HOME/.claude/skills/jlcpcb-component-finder/query.js db-info

Manual Update (Alternative)

If the script doesn't work, download manually:

Visit https://yaqwsx.github.io/jlcparts/
Download all cache.z* and cache.zip files
Extract: 7z x cache.zip
Move: mv cache.sqlite3 $HOME/.jlcpcb-db/