How does this skill help with Cairo development?

It provides clear patterns for organizing code, specifically showing how to use the `mod` keyword to link external files and maintain a clean project structure.

Where should I put a submodule file in Cairo?

The skill explains that if you declare a submodule in `name.cairo`, the corresponding file should be placed in a directory named `name/` at the same level.

Can it help refactor a single large Cairo file?

Absolutely; it guides the process of extracting code into separate files while maintaining the correct module hierarchy required by the compiler.

Does it explain the difference between 'mod' and 'use'?

Yes, it clarifies that `mod` is used to declare and load a module into the project tree, while `use` is only for bringing existing items into the current scope.

Cairo Module Organizer

Name: Cairo Module Organizer
Author: teddyjfpender

byteddyjfpender

•

Developer Tools

Guides the organization and mapping of Cairo modules across files and directories for structured project development.

About

This skill provides specialized guidance on how to correctly structure Cairo projects by splitting modules into multiple files and directories. It clarifies the critical relationship between `mod` declarations and the file system, helping users avoid common pitfalls like confusing `use` with module loading. By providing clear patterns for placing module bodies in `name.cairo` or `name/mod.cairo`, it ensures that developers can scale their Cairo applications with a clean, maintainable, and standards-compliant file hierarchy.

Key Features

Maps `mod` declarations to specific file paths and directories
Provides hierarchical submodule structure guidance for complex projects
Clarifies the distinction between loading modules (`mod`) and importing items (`use`)
Ensures compliance with standard Cairo package organization conventions
Assists in refactoring monolithic Cairo files into modular components
3 GitHub stars

Use Cases

Troubleshooting module resolution and 'file not found' errors in Cairo
Splitting a large smart contract into smaller, manageable module files
Setting up a nested directory structure for complex Starknet projects

About

Key Features

Maps `mod` declarations to specific file paths and directories
Provides hierarchical submodule structure guidance for complex projects
Clarifies the distinction between loading modules (`mod`) and importing items (`use`)
Ensures compliance with standard Cairo package organization conventions
Assists in refactoring monolithic Cairo files into modular components
3 GitHub stars

Use Cases

Troubleshooting module resolution and 'file not found' errors in Cairo
Splitting a large smart contract into smaller, manageable module files
Setting up a nested directory structure for complex Starknet projects