Skip to main content
These commands are planned and not yet available. This page documents the intended interface. Available on Pro plans and above.

trace init

Create a new Trace project.
trace init [project-name] [options]
OptionDescription
--template <name>Use a project template (blank, arduino, stm32, esp32, rpi-pico)
--path <dir>Create in a specific directory
--layers <n>Number of copper layers (default: 2)
--size <WxH>Board dimensions in mm (e.g., 100x80)
# Create a 4-layer board from the STM32 template
trace init motor-controller --template stm32 --layers 4 --size 60x40

trace export

Export manufacturing files from a project.
trace export [options] <project-path>
OptionDescription
--format <type>Output format: gerber, bom, step, pick-and-place, pdf, odb++, ipc2581, all
--output <dir>Output directory (default: ./output)
--layers <list>Specific layers to export (comma-separated)
--manufacturer <name>Use manufacturer presets: jlcpcb, pcbway, oshpark, eurocircuits
--zipPackage outputs into a fab-ready ZIP
--validateRun DFM validation before export
# Export everything for JLCPCB in a ZIP
trace export --manufacturer jlcpcb --format all --zip ./board.kicad_pro

# Export just the BOM as CSV
trace export --format bom --output ./bom.csv ./board.kicad_pro

# Export STEP for mechanical integration
trace export --format step --output ./mechanical/board.step ./board.kicad_pro

trace drc

Run Design Rule Checks on a project.
trace drc [options] <project-path>
OptionDescription
--rules <file>Custom rules file (JSON or KiCad DRC format)
--strictExit with error code on warnings (not just errors)
--format <type>Output: text, json, markdown
--output <file>Write results to file instead of stdout
--category <list>Check specific categories: clearance, width, via, courtyard, edge, impedance
# Run full DRC with JSON output
trace drc --format json --output drc.json ./board.kicad_pro

# Check only impedance and clearance rules, fail on warnings
trace drc --strict --category impedance,clearance ./board.kicad_pro

trace erc

Run Electrical Rule Checks on a schematic.
trace erc [options] <project-path>
OptionDescription
--strictExit with error code on warnings
--format <type>Output: text, json, markdown
--output <file>Write results to file
trace erc --strict --format json ./board.kicad_pro

trace review

Run an AI design review on a project. Analyzes the schematic and PCB for potential issues, suggests improvements, and generates a structured report.
trace review [options] <project-path>
OptionDescription
--scope <type>Review scope: full, schematic, pcb, bom
--focus <areas>Focus areas (comma-separated): routing, thermal, impedance, dfm, components, power
--format <type>Output: text, json, markdown
--output <file>Write report to file
--severity <level>Minimum severity to report: info, warning, error, critical
# Full design review
trace review --format markdown --output review.md ./board.kicad_pro

# Focus on thermal and impedance issues only
trace review --focus thermal,impedance --severity warning ./board.kicad_pro

# Review just the schematic
trace review --scope schematic ./board.kicad_pro

What the Review Checks

  • Component selection — Availability, EOL status, pin-compatible alternatives
  • Routing quality — Trace widths, clearances, length matching, via usage
  • Thermal — Power dissipation, copper pour coverage, thermal via placement
  • Impedance — Controlled-impedance trace geometry vs. stackup
  • DFM — Manufacturability against fab house capabilities
  • Power integrity — Decoupling, power plane continuity, voltage drops
  • Signal integrity — Crosstalk risks, return path discontinuities

trace ask

Ask the AI a question about a design. Runs in read-only mode — no modifications are made.
trace ask "<question>" [options]
OptionDescription
--project <path>Project to analyze (required for design-specific questions)
--format <type>Output: text, json, markdown
--output <file>Write response to file
# Ask about a specific design
trace ask "What is the purpose of R14 and R15?" --project ./board.kicad_pro

# Get impedance guidance
trace ask "What trace width do I need for 90 ohm differential on the inner layers?" --project ./board.kicad_pro

# General circuit question (no project needed)
trace ask "What decoupling capacitors do I need for an STM32F4?"

trace components

Check component availability, pricing, and alternatives.
trace components <subcommand> [options]

trace components check

Validate all components in a BOM against distributor stock.
trace components check --bom <file> [options]
OptionDescription
--bom <file>BOM file (CSV or project path)
--distributors <list>Distributors to check: jlcpcb, lcsc, digikey, mouser, ti, amazon
--format <type>Output: text, json, csv
--suggest-alternativesInclude pin-compatible alternatives for out-of-stock parts
# Check all components against JLCPCB and DigiKey
trace components check --bom ./board.kicad_pro --distributors jlcpcb,digikey --suggest-alternatives
Search for components by description or part number.
trace components search "<query>" [options]
OptionDescription
--type <type>Filter by type: resistor, capacitor, ic, connector, etc.
--package <pkg>Filter by package: 0402, 0603, SOIC-8, QFP-48, etc.
--in-stockOnly show in-stock parts
--limit <n>Max results (default: 10)
trace components search "LDO 3.3V 500mA" --package SOT-223 --in-stock

trace bom

Generate, validate, and optimize a Bill of Materials.
trace bom [options] <project-path>
OptionDescription
--format <type>Output: csv, json, excel, html
--output <file>Write BOM to file
--pricingInclude real-time pricing from distributors
--optimizeSuggest cost-optimized alternatives
--validateCheck all parts are available and not EOL
# Generate BOM with pricing
trace bom --format csv --pricing --output bom.csv ./board.kicad_pro

# Validate and optimize BOM
trace bom --validate --optimize --format json ./board.kicad_pro

trace auth

Manage CLI authentication.
trace auth <subcommand>
SubcommandDescription
loginAuthenticate via browser
logoutRemove stored credentials
statusShow current auth status and plan info
tokenDisplay current API token
trace auth login
trace auth status

Exit Codes

All commands use consistent exit codes for scripting:
CodeMeaning
0Success
1General error
2Authentication required or failed
3Project not found or invalid
10DRC/ERC errors found
11DRC/ERC warnings found (with --strict)
20Components unavailable