Explicit advanced workflow for generating, inspecting, dry-running, and validating plain FDM `.gcode` with real slicer CLIs. Use only when the user asks Replicator to generate G-code, needs headless/reproducible slicing, or cannot use a slicer UI.

Explicit advanced workflow to inspect status, upload, or cautiously start/control local Bambu Lab printers through LAN FTPS/MQTT after validated G-code exists. Use only when the user asks for printer communication or physical print control.

Use before Project Replicator product, hardware, PCB, CAD, manufacturing, or review work.

Use before Project Replicator PCB source, layout, routing, DRC, fabrication, or PCB visual-review work.

Use when writing or revising product/README.md, product/requirements.json, or product/contract.json in project-replicator.

Use when uploaded or project PDF files need exact text extraction, page-specific review, visual inspection of embedded images/diagrams/scans, datasheet figures, tables, or layout-sensitive evidence.

Independently audit one immutable, Host-frozen PCB release candidate using the design's own editable source, its manufacturing reports, and board-frame measurements from `pcb.measure`. Use only for the Host-owned PCB release review that returns a prioritized Markdown report; do not use for PCB editing, routing, or fabrication export.

Use for persistent, visual, short-loop CAD modeling with cad.open, cad.add_part, cad.edit_part, cad.place, cad.import, cad.delete, cad.look, cad.inspect, Host-owned CAD Review, and cad.export.

Independently audit one complete committed CAD build using cad.look image evidence and cad.inspect geometry facts. Use only for the Host-owned CAD handoff review that returns prioritized P0/P1 issues as ordinary text; do not use for CAD editing, finite-element analysis, physical load certification, or export.

Use for CAD Part Research when standard, purchasable, or library-backed mechanical components must be resolved before modeling.

Use when standard mechanical parts, fasteners, bearings, V-slot rails, T-nuts, wheels, or linear-motion parts are needed in Build123d CAD, and always before modeling a screw into a 3D-printed part — printed screw joints must come from this skill's kit, never hand-modeled.

Use when custom Build123d Python CAD code, geometry operations, selectors, locations, joints, assemblies, imports, exports, or DFM details are needed. Read `references/dfm-rules.md` BEFORE writing the first line of geometry code for any screw boss, standoff, snap fit, wall interface, or overhang-sensitive feature — not after the shape exists. A screw fastening into a 3D-printed part additionally requires the `build123d-libs` kit; never hand-model that joint.

Prepare committed Replicator CAD objects for ordinary FDM printing by arranging quantities across real build-plate dimensions and exporting one standard unsliced `.3mf` per plate for Bambu Studio or another slicer.

Use when electronic components must be selected, priced, checked for stock, compared with alternatives, or prepared as BOM-ready candidates with datasheet-backed implementation evidence.

Use when a selected electronic parts list must be validated, enriched, exported, or made procurement-ready.

Use when a development board, SBC, MCU module, or board-level enclosure constraint must be resolved for hardware or CAD design.

Allows to interact with web pages by performing actions such as clicking buttons, filling out forms, and navigating links. It works by remote controlling Google Chrome or Chromium browsers using the Chrome DevTools Protocol (CDP). When Claude needs to browse the web, it can use this skill to do so.

Project-specific patterns for the Saleor Paper storefront built with Next.js 16, TypeScript, and Tailwind CSS. Use when working with product pages, checkout flow, caching, variant selection, filtering, SEO, or UI components. For universal Saleor API patterns, see the saleor-storefront dependency.

Complete reference for ecluse — ephemeral local environments for coding agents, any stack. Use this skill whenever ecluse is mentioned, a .ecluse.toml file is present in the repo, the user asks about worktree isolation, parallel dev environments, or port/database conflicts between branches. When a .ecluse.toml file is present in the repo, loading this skill before starting work is strongly recommended so you understand the isolation model and avoid port conflicts.

Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.