Generates Mojo code using current syntax, conventions, and removed-construct replacements.
npx skills add https://github.com/shakfu/mdsp --skill mojo-syntax-shakfu
Please help me install this Agent Skill. Skill: mojo-syntax Source: https://github.com/shakfu/mdsp/tree/main/.claude/skills/mojo-syntax Command: npx skills add https://github.com/shakfu/mdsp --skill mojo-syntax-shakfu
fn, alias, inout, @parameter) with current Mojo syntax so generated code compiles against the latest toolchain. ## Core Features & Use Cases - Removed-syntax corrections: Maps deprecated constructs (fn, let, borrowed, inout, owned, DynamicVector, UnsafePointer APIs) to their modern replacements (def, var, imm, mut, List, Pointer). - Current language rules: Covers comptime constants and assertions, argument conventions (out, mut, deinit, ref), lifecycle methods, Writable/Writer, origins, closures, SIMD, strings, and error handling. - Use Case: When translating a Python DSP kernel to Mojo, use this Skill to write struct definitions with @fieldwise_init, explicit trait conformance, std.-prefixed imports, and raises annotations that compile on the first build. ## Quick Start Write a Mojo struct with copy and move constructors plus a test suite using current Mojo syntax.High-intent search queries and answers about installing and using this skill.
Use `def` for every function, method, and nested function; the `fn` keyword was removed and is now a hard parse error. Functions that can raise must be explicitly marked with `raises` before the return arrow, or compilation fails.
Replace `alias` with `comptime`, `let` with `var`, `inout` with `mut`, `owned` with `var`, and `@parameter if`/`for` with `comptime if`/`for`. Imports also move to the `std.` prefix, such as `from std.collections import ...`.
No, `fn` was fully removed and is a hard parse error with no valid remaining use. Every function, method, and nested function must be written with `def`, and raising functions need an explicit `raises` marker.
Types not conforming to `ImplicitlyCopyable`, such as `Dict`, `List`, and structs with only `Copyable, Movable`, require explicit `.copy()` or ownership transfer with `^`. Returning or passing such values without transfer is a compile error.
The `Writable` trait with a `write_to` method replaces `Stringable` and `__str__`. Both `write_to` and `write_repr_to` have default implementations via reflection when all fields are `Writable`, and values convert to text with `String(value)`.
panicPaulEnforce up-to-date Mojo syntax conventions in generated code.
HomericIntelligenceRun Mojo test suites with filtering by file or pattern.
Harmeet10000Explain CUDA-free Mojo GPU programming with LayoutTensor and shared memory patterns.
hafley66Compare React and Dioxus across component models, state semantics, and SSR capabilities.