mojo-tools
Use when editing Mojo code, .mojo files, fire emoji files, SIMD kernels, Python-Mojo interop, GIL-free parallelism, C FFI, hatch-mojo build hooks, or packaging Mojo extensions.
Best use case
mojo-tools is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when editing Mojo code, .mojo files, fire emoji files, SIMD kernels, Python-Mojo interop, GIL-free parallelism, C FFI, hatch-mojo build hooks, or packaging Mojo extensions.
Teams using mojo-tools should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/mojo-tools/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How mojo-tools Compares
| Feature / Agent | mojo-tools | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when editing Mojo code, .mojo files, fire emoji files, SIMD kernels, Python-Mojo interop, GIL-free parallelism, C FFI, hatch-mojo build hooks, or packaging Mojo extensions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Mojo (Flow Tools) <workflow> ## 🚀 Official Modular Skills (Highly Recommended) For comprehensive support for modern Mojo syntax, project initialization, and GPU programming, we highly recommend installing the official Modular agent skills: - **mojo-syntax**: Overcomes agent misconceptions and ensures correct modern syntax. - **new-modular-project**: Wizard for initializing Mojo/MAX projects with Pixi and UV. - **mojo-python-interop**: Expert guidance for zero-copy Python interaction. - **mojo-gpu-fundamentals**: Patterns for high-performance accelerator programming. **Installation:** ```bash npx skills add modular/skills ``` ## Supplemental Patterns The patterns below focus on project integration and build hooks. ### Hatch-Mojo Build Hook The `hatch-mojo` plugin allows seamless compilation of Mojo source files during the standard Python build process. **Key Configuration (`pyproject.toml`):** ```toml [tool.hatch.build.targets.wheel.hooks.mojo] # Configuration for mojo compilation ``` </workflow> <guardrails> ## Guardrails - **Explicitly define memory ownership** -- Use `owned`, `borrowed`, and `inout` to manage data flow and avoid unnecessary copies. - **Use `SIMD` for performance-critical logic** -- Mojo excels at vectorization; always consider SIMD when processing large arrays. - **Verify data alignment** -- Ensure pointers are aligned for the target architecture, especially when using SIMD operations. </guardrails> <validation> ## Validation Checkpoint - [ ] Explicit ownership markers are correctly applied to arguments - [ ] SIMD vectorization is implemented where applicable - [ ] Memory safety is verified through ownership and borrowing checks </validation> <example> ## Hatch-Mojo Build Hook Example ```toml [tool.hatch.build.targets.wheel.hooks.mojo] dependencies = ["hatch-mojo"] path = "src/my_extension.mojo" ``` </example>
Related Skills
shadcn-tools
Use when editing shadcn/ui code, components.json, cn() utility, Radix primitives, shadcn add workflows, dialogs, forms, data tables, command palettes, or Tailwind component composition.
railway-tools
Use when deploying to Railway, editing railway.toml, railway.json, Procfile, configuring Railway services, databases, workers, environment variables, or troubleshooting Railway deployments.
flow-memory-keeper
Use at task, phase, flow, sync, archive, finish, revise, or failure checkpoints to keep Flow specs clean, capture learnings and failures, elevate durable patterns, and refine this skill with project-specific nuances
vue
Use when editing Vue projects, .vue files, vue.config.js, Vue 3 components, Composition API, <script setup>, SFC state, deployment workflows, or Vue CI configuration.
vite
Use when editing Vite projects, vite.config.ts, vite.config.js, Vite plugins, HMR, asset bundling, frontend build settings, deployment config, or Litestar/Vite integration.
uvicorn
Use when deploying ASGI apps with uvicorn, editing uvicorn CLI commands, Config or Server usage, workers, reload, event loop selection, SSL, lifespan, logging, or development server behavior.
tracer
Use when tracing execution paths, mapping dependencies, understanding unfamiliar code, following data flow, investigating end-to-end behavior, debugging call chains, or deciding which files to read next.
testing
Use when writing or refactoring tests, editing test_*.py, *.test.ts, *.spec.ts, conftest.py, vitest.config.ts, pytest fixtures, mocks, coverage, async tests, anyio, or test failure debugging.
terraform
Use when creating, adopting, refactoring, or operating Terraform, *.tf files, .terraform.lock.hcl, terragrunt.hcl, root modules, backends, state, workspaces, imports, CI plan/apply, tests, or policy checks.
tanstack
Use when editing TanStack code, @tanstack imports, useQuery, createRouter, React Query, TanStack Router, Table, Form, Store, file-based routing, data fetching, or SPA state management.
tailwind
Use when styling with Tailwind CSS, editing tailwind.config.ts, tailwind.config.js, @tailwind directives, utility classes, responsive layouts, @apply, cn(), @theme config, dark mode, or forms.
svelte
Use when editing Svelte components, .svelte files, svelte.config.js, Svelte 5 runes, $state, $derived, SvelteKit, component state, or migrating away from Svelte 4 patterns.