pcbjs-basics
/pcbjs-basics
Projektuje płytkę PCB w pcbjs za pomocą TypeScript i JSX: podzespoły, połączenia, rozmieszczenie i sprawdzenia DRC lub ERC.
Ocena i bezpieczeństwo
- Pliki w paczce
- 11
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Projektuje płytkę PCB w pcbjs za pomocą TypeScript i JSX: podzespoły, połączenia, rozmieszczenie i sprawdzenia DRC lub ERC.
Oryginalny opis (EN)
Design a PCB in pcbjs using TypeScript and JSX. Use when creating or editing a pcbjs board, connecting parts and nets, placing or routing entities, or resolving compile and DRC/ERC findings.
Jak działa
- Organize the work
- Essential working loop
- Load on demand
Podgląd SKILL.md
--- name: pcbjs-basics description: Design a PCB in pcbjs using TypeScript and JSX. Use when creating or editing a pcbjs board, connecting parts and nets, placing or routing entities, or resolving compile and DRC/ERC findings. --- # pcbjs basics A board is a TSX module exporting `<PCB>`. Nets and parts are values; JSX places them. Start with this entry point, then load only the reference or `docs` topic needed for the current decision. Do not preload the docs tree, all skills, or all references. ## Organize the work For work spanning independent areas, prefer an orchestrator with focused workers when the harness supports and permits delegation. The orchestrator owns scope, interfaces, task ownership, integration and acceptance evidence. Workers own detailed source inspection, relevant topic reading, implementation and focused checks. A small local change can stay in one agent. Give each worker a bounded outcome, owned files, relevant entry/board/target and constraints, plus the checks that establish completion. Pass paths and a short brief rather than the whole conversation or transcript. Workers load their own task-specific references and return decisions, changed files, verification results and unresolved risks with evidence paths. Keep raw logs and implementation exploration out of the orchestrator's context; inspect details only to resolve a conflict or verify a claim. Read [Orchestration](references/orchestration.md) when coordinating several tasks. ## Essential working loop - Notify the user of plans, meaningful progress, questions and completion in the main chat session. MCP task/progress updates populate agent activity, not VS Code notifications; workers report to the coordinator for user-facing updates. - Prefer pcbjs MCP tools when present: they see the live session and unsaved source. The connection owner calls `session` with the task and confirms the agent connection; keep that harness-owned process alive. On a shared connection, the coordinator owns task/progress and checks `events` before edits and after long shell-only work, relaying corrections to workers. Read [Live session](references/session.md) for setup, messaging or tool details; CLI commands do not establish an agent inbox. - Read current source and apply anchored edits. Do not replace an existing file with a whole-file Write. Give each file one writer at a time; coordinate changes to shared pinouts, nets, grids and configuration before workers depend on them. - Use `inspect` or `query` for positions and records, and `render` for a focused view. Avoid reading generated `board.json` or computing transformed pad positions by hand. - Run `check` after the change and inspect the relevant view. The orchestrator verifies the integrated board before reporting completion. Fabrication output requires a completed check; a halted preview is not validation. - Keep board markings useful for assembly, testing and operation. Do not add disclaimers, TODOs, readiness warnings or branding just to repeat the chat. Keep durable decisions in existing project notes; use `fabNotes` only for actionable fabrication instructions. See `docs fab-set` for where notes belong. ## Load on demand Use MCP `docs` or `npx pcbjs docs` without a topic to discover titles, then request one topic. Search with `topic` plus `grep` when the question is narrower. Load another reference only when the current task reaches that subject. | Current task | Load | | --- | --- | | Add a board to an existing project | [Multiple boards](references/multi-board.md), sharing its config and session by default | | Create a project or learn the full source structure | [Getting started](references/getting-started.md) | | Connect parts or define footprints | `docs schematic`, `docs footprints`, or `docs stdlib`, whichever applies | | Place parts, groups or grids | `docs placement`, `docs layout`, or `docs grids` | | Route manually or automatically | `docs routing`; add `autorouter`, `pairs` or `length` only for that feature | | Use a complete layout pattern | [Pattern index](references/board-patterns.md), then one linked example | | Resolve a finding | [Common fixes](references/fixes.md), or `docs findings` for the named rule | | Verify a change or preserve design intent in tests | [Verification](references/verification.md) | | Source or author 3D models | `docs models`; use the best-practices model reference for a model review | If pcbjs leaves a needed measurement out of a finding, report the missing detail and the query used to obtain it.
Pliki w paczce (11)
- SKILL.md 4 KB
- references/board-patterns.md 1 KB
- references/fixes.md 4 KB
- references/getting-started.md 3 KB
- references/length-matching.md 1 KB
- references/multi-board.md 1 KB
- references/orchestration.md 4 KB
- references/repeated-blocks.md 1 KB
- references/session.md 3 KB
- references/split-schematic.md 2 KB
- references/verification.md 4 KB
Wersje
W bazie nie ma innych skilli o nazwie pcbjs-basics.
Migawka bazy z 13.11.2026 · wersja paczki 8ebc05ee0773 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95design_pcb
Tworzy schemat, płytkę PCB i trasowanie w KiCad 9 przez MetaForge, sprawdzając każdy krok przez ERC, DRC i zgodność schematu. - 100copper-pilot-review
Recenzuje schemat lub płytkę PCB przez CopperPilot CLI: sprawdza ERC i DRC, bada sieci i oznaczenia oraz daje uwagi do projektu elektroniki. - 95design_pcb
Generuje schemat, płytkę PCB i trasowanie w KiCad 9 przez MetaForge, sprawdzane przez ERC, DRC i zgodność schematu z płytką. - 90makeirl-release-gate
Sprawdza płytkę KiCad 9 przed produkcją: ERC, DRC, zgodność schematu z PCB, kompletność BOM i eksport, z werdyktem BLOCKED, REVIEW lub READY. - 90pcbjs-best-practices
Przegląda i wzmacnia płytkę w pcbjs poza zwykłą kontrolą: ograniczenia projektowe, weryfikację elektryczną i mechaniczną, jakość trasowania i powtarzalne pliki produkcyjne. - 90pcbjs-upgrade
Aktualizuje projekt pcbjs do nowszej wersji i sprawdza, czy płytka nadal kompiluje się do tej samej miedzi, także po błędach typów lub niezgodnych pakietach.