Mojo Syntax
modular/skills/mojo-syntaxby modularb9b3a8e86700No license200 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today
Help to write Mojo code using current syntax and conventions. Always use this skill when writing any Mojo code, including when other Mojo-specific skills (e.g., mojo-gpu-fundamentals) also apply. Use when writing or reviewing Mojo code, translating projects to Mojo, or otherwise generating Mojo. Use this skill to overcome misconceptions with how Mojo is written.
- b9b3a8e86700Currentcommit b9b3a8ePublished Oct 8, 2026
Source and attribution
Source:modular/skillsinmojo-syntaxat commitb9b3a8e
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from modular/skills
New Modular Project
modular
Guides creation of a new Mojo or MAX project, choosing an environment manager and channel.
Mojo Gpu Fundamentals
modular
Teaches how to write Mojo GPU kernels, correcting CUDA-based assumptions about syntax, memory and launches.
Benchmark Model
modular
Benchmarks a running MAX model server with the max benchmark command, measuring throughput and latency.
More in Software Development
Playground
anthropics
Builds self-contained interactive HTML playgrounds with controls, live preview, and copyable prompt output.
M5 Onboard
anthropics
Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.
Cardputer Buddy
anthropics
Guides iterating on a Cardputer-Adv MicroPython app bundle: adding apps, pushing files over USB-serial, tailing logs, and running REPL commands.
Web Design Guidelines
vercel-labs
Reviews UI code against Web Interface Guidelines fetched from a remote source and reports findings as file:line entries.
Vercel React Native Skills
vercel-labs
React Native and Expo best-practice rules covering list performance, animation, navigation, UI patterns, state, and monorepo setup.
Vercel React Best Practices
vercel-labs
Vercel's React and Next.js performance guidelines, organized as 70 rules for writing, reviewing, and refactoring code.