TraceRules

What It Does

TraceRules stores written design preferences in .trace/rules.md. The shared design notebook, .trace/context.md, records project requirements, decisions and unresolved questions.

These files provide context, not enforced engineering rules or guaranteed memory. Inspect important decisions and the actual saved design rather than assume the assistant retained or followed every note.

File Location

my-project/
├── my-board.kicad_pro
├── my-board.trace_sch
├── my-board.trace_sch.xo
└── .trace/
    ├── rules.md     # Personal project preferences
    └── context.md   # Shared design requirements and notes

.tracerules is a legacy filename. Do not assume current clients load it or merge it with .trace/rules.md. Review old rules and move the intended preferences into the current file, avoiding contradictory copies.

Rules File Format

Use short Markdown sections with explicit priorities and design-grounded constraints:

# Personal Design Preferences

## Components
- Prefer 0603 imperial passives where the design permits.
- Keep exact user-selected part numbers unless I approve a substitution.

## Review
- Explain unresolved pinout or package assumptions before changing parts.
- Check manufacturer limits in the active DRC rules, not just this note.

Package, trace-width, decoupling and impedance choices still need the actual device, current, stackup and manufacturer requirements. Example preferences are not universally correct engineering values.

Workspace Context

.trace/context.md can contain confirmed design goals, selected parts and rationale, interface/mechanical requirements, reviewed results and open issues. The assistant can update it through supported file tools. Read and correct inaccurate or stale notes yourself; an AI-written note is not proof of a measurement, approval or completed operation.

How the AI Uses Your Rules

Capable native chat includes bounded project rules as context. Trace Plugin also reads the selected project's .trace/rules.md, but sends only a bounded excerpt. Keep rules concise and put essential requirements within that excerpt; do not assume the entire file reaches the model. Save changes before the next new request; an existing-task resume is not a guarantee that every setting or note is reread.

Stating a preferred manufacturer does not install or activate its DRC preset. Use the actual DRC controls and inspect their findings. Natural-language rules do not waive ERC/DRC, establish circuit correctness, override permissions or authorize physical hardware actions.

What to Put in .trace/rules.md

For the current .trace/rules.md, include personal component preferences, review conventions and presentation style. Put confirmed project-wide requirements into .trace/context.md when they should be shared.

State which constraints are mandatory and which are preferences. Ask for clarification when they conflict; placing a rule first does not give it a guaranteed priority.

What Not to Put

• Credentials or private information unsuitable for hosted context.
• Blanket instructions to ignore DRC categories or skip required checks.
• Unsupported claims that a design passed a measurement or manufacturing review.
• Contradictory copies of requirements in several files.

TraceRules Editor

Use TraceRules from the chat controls where offered, or edit .trace/rules.md in a text editor. Check the active project before saving. Review shared notebook edits in Workspaces Changes just like other authored project content.

Example: Full Project Setup

Keep personal preferences and shared design facts distinct. A shared notebook can start with:

# Sensor Board — Confirmed Requirements

## Requirements
- Programming access must remain usable through the enclosure opening.
- Keep the approved connector position, rotation, and board side unless the team approves a change.

## Open Questions
- Confirm the selected enclosure drawing and connector mating clearance.
- No physical access or thermal measurement has been performed.

Evaluating Quality

Compare the actual result with your requirements and correct stale notebook entries. Rules are not a beta-access guarantee, a deterministic constraint solver or a substitute for review. See the TraceRules reference for file and sharing scope.