Reveals what matters. Hides what doesn't.
An FTC robotics project generator that gives your students professional-grade tools. Clean project structure, real unit tests, and workflows that mirror industry practices.
git clone https://nxgit.dev/nexus-workshops/weevil.git
Most FTC teams start by cloning the entire SDK and writing code inside it. It gets robots running, but there's a better path — one that mirrors professional software development and builds skills students will use for years.
What if new team members could open a project and immediately see just the code that's theirs? Clear boundaries make onboarding faster and learning easier.
When student code has its own home — separate from the SDK — it's easier to understand, modify, and share. Clear structure builds confidence.
Imagine teaching Git where students only track their own code. No confusion about what to commit, cleaner diffs, easier collaboration.
What if students could validate their logic at their desk before walking across the room to the robot? Faster feedback loops mean faster learning.
Separation of concerns, dependency management, testing — these patterns aren't just for industry. When students start with good structure, they build skills that compound.
Weevil generates standalone robot projects with your code in src/, tests that run on laptops, and the SDK as a clean dependency. It's the structure professional teams use — now available for FTC.
Student code in src/. Build scripts in Gradle. SDK as a dependency, not mixed in. Clear lines. Students know exactly what's theirs and what isn't.
45 tests in under 2 seconds. No robot, no USB cable, no walking across the room. Catch logic errors at your desk, then deploy with confidence.
Templates with complete subsystems, hardware abstraction, and comprehensive documentation. The kind of code students would write if they already had years of experience.
Proper .gitignore. Only your files in the repo. Diffs that make sense. Version control becomes a learning tool, not a source of confusion.
Auto-generated run configurations. Hit the green button to build, test, or deploy. SDK internals hidden from the file tree so students focus on what matters.
Automatic proxy detection from environment variables. Explicit --proxy flag when needed. Designed for the real world of school networks.
From empty directory to tested, deployed robot. The kind of workflow that lets students focus on problem-solving instead of build configuration.
Choose a template that matches where your team is. Get the structure right from day one, then focus on building your robot.
--template basicThe right project structure, the right build scripts, and a sample OpMode to get you started. Perfect for teams who know what they're doing and just want the boilerplate done right.
--template testingEverything in basic, plus three complete subsystems, a hardware abstraction layer, 45 passing tests, and professional documentation. Learn by reading real, production-quality code.
Our hands-on guide walks you through building your first testable subsystem — from mock classes to unit tests to real hardware adapters.
Read the TutorialYour code in src/. Tests alongside it. Build infrastructure generated for you. The SDK stays clean as a system dependency — not a container for student code.
Separation of concerns. Testability. Clean boundaries. These aren't corporate buzzwords — they're the difference between a team that spends Saturday debugging Gradle and a team that spends Saturday perfecting their autonomous routine.
Weevil already solves the core challenges. Here's what we're building next to make it even better.
Share tested components across teams. weevil add nexus/subsystems/mecanum-drive drops a documented mecanum drive into your project. Community packages, verified components, dependency resolution.
Grid-based robot localization with sensor fusion — encoders, IMU, and AprilTags working together. Fault-tolerant positioning that degrades gracefully when sensors fail.
Coming soonNot everyone loves the terminal. A graphical interface for creating projects, managing builds, and browsing packages. Built with Tauri for native performance.
On the roadmapSet breakpoints. Hit the debug button. Step through your OpMode code while it runs on the robot. Real debugging, not telemetry.addData() and guesswork.
Build error analysis in plain English. Connectivity diagnostics. Log analysis. Performance profiling. Tools that turn frustration into answers.
On the roadmapMSI for Windows, .deb for Debian/Ubuntu. Double-click to install, adds to PATH automatically. Professional installation experience.
On the roadmapWeevil is free, open source, and MIT licensed. Built for FTC teams who want to spend less time wrestling with build systems and more time learning to build great robots.