motoko-general-style-guidelines

Organize Motoko code with standardized spacing, indentation, braces, naming, and type annotations.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/research-ag/motoko-skills --skill motoko-general-style-guidelines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: motoko-general-style-guidelines
Source: https://github.com/research-ag/motoko-skills/tree/main/skills/motoko-general-style-guidelines
Command: npx skills add https://github.com/research-ag/motoko-skills --skill motoko-general-style-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve readability and uniformity of Motoko source code by providing a comprehensive, opinionated style guide that standardizes formatting, naming, and structural conventions across *.mo files.

Core Features & Use Cases

  • Spacing, punctuation, and line-break conventions to increase readability.
  • Indentation and grouping guidelines to structure complex code.
  • Naming conventions for types, modules, and variables to reduce ambiguity.
  • Comments and documentation best practices within Motoko projects.

Quick Start

Review these guidelines before starting new Motoko files to ensure consistent formatting.

Frequently Asked Questions about motoko-general-style-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to format Motoko code for readability?▼

A comprehensive Motoko style guide standardizes formatting, naming conventions, and structural rules to improve readability and reduce ambiguity across all project files.

How do I establish naming conventions for Motoko types and modules?▼

Standardizing Motoko naming conventions involves applying consistent rules for types, modules, and variables to reduce ambiguity and improve source code uniformity.

What spacing and indentation rules should I use for Motoko projects?▼

Consistent spacing and indentation conventions structure Motoko code logically, increasing readability and maintaining uniformity across different project sizes.

Does this style guide work for Motoko projects of any size?▼

The style guide applies universally to Motoko projects of all sizes, providing consistent formatting and naming conventions regardless of project scale.

When do I need a style guide for my Motoko source code?▼

A style guide is needed when starting new Motoko files to establish consistent formatting, spacing, and naming conventions, preventing structural ambiguity in the codebase.