Pybricks Api Coach

Code Rules

• Keep every function single-purpose.
• Name actions by field meaning, not by motor detail. Prefer deliver_sample() over run_attachment_a().
• Put all tunable values in one block near the top.
• Keep mission code readable enough to patch at the table in less than a minute.
• When the user gives incomplete hardware info, state the assumptions explicitly instead of inventing hidden ports.
• If the user asks for line following, routing, or attachment sequencing, call out the matching specialized skill in the answer and still provide valid starter code here.

Output Pattern

Use this structure unless the user requests a different one:

Assumptions

• hub
• ports
• wheel diameter
• axle track
• sensors
• attachments

Program

Provide a full runnable program.

Tuning checklist

• constants to verify first
• likely failure points
• one quick bench test

Resources

• Use references/pybricks-competition-patterns.md for standard imports, structure, and review checks.
• Use assets/competition_base.py as the default starting skeleton when writing a new program.