Design Standards

The Team Way — how we build, code, and organize.

🔧 Build Standards

• Use nylocks on all competition-critical joints — no regular nuts
• All C-channel cuts must be deburred and filed smooth
• Wires must be zip-tied and routed away from moving parts
• Standoffs must be used for motor mounting — never direct-bolt
• Always use bearing flats on shafts that pass through metal
• Label all motors with their port numbers using tape flags

💻 Code Style Guide

• Use camelCase for variables and functions: driveForward(), liftSpeed
• Use UPPER_SNAKE_CASE for constants: MAX_SPEED, DRIVE_KP
• Comment all autonomous routines with a description of what they do
• Keep functions under 50 lines — break long logic into helpers
• Use PID controllers for all precision movements (not raw setPower)
• Commit to GitHub after every successful test, with descriptive messages

📂 File & Naming Conventions

• CAD Files: XXXXX[D/P]_[mechanism]_v[version].step — e.g., Team A_intake_v3.step
• Code Files: src/[subsystem].cpp — e.g., src/drivetrain.cpp, src/auton.cpp
• Notebook Entries: YYYY-MM-DD_[topic].pdf — e.g., 2026-01-15_drivetrain-rebuild.pdf
• Media: [event]_[date]_[number].jpg — e.g., states_2026-02-08_001.jpg

📐 CAD Best Practices

• Always start designs from the official VEX CAD library models
• Build in sub-assemblies: drivetrain, intake, lift, clamp as separate files
• Use constraints/mates to simulate range of motion before building
• Export STL files for any 3D-printed components at 0.2mm resolution
• Version your designs — never overwrite, always "Save As" with incremented version
• Save screenshots of each iteration for the engineering notebook

📋 Pre-Match Checklist

• ✅ Battery above 80%
• ✅ All screws tightened (check drivetrain, lift, clamp)
• ✅ Autonomous routine selected and confirmed
• ✅ Controller paired and tested
• ✅ Rubber bands checked for wear
• ✅ Robot fits within 18" × 18" × 18" sizing tool

🤝 Team Communication

• Use the team Discord for real-time coordination
• Post build updates in the #build-log channel with photos
• Tag @programmers for any code-related requests
• Weekly standup meetings every Monday to review progress