dart-naming-conventions

Enforce Dart and Flutter naming conventions for interfaces, implementations, and folders.

5|Updated Oct 14, 2025

Search Tags:#refactoring #clean code #code style #naming conventions #flutter #dart

Ready to run

npx skills add https://github.com/reloveution/dart-flutter-rules --skill dart-naming-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dart-naming-conventions
Source: https://github.com/reloveution/dart-flutter-rules/tree/main/skills/dart-naming-conventions
Command: npx skills add https://github.com/reloveution/dart-flutter-rules --skill dart-naming-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the inconsistency and ambiguity in naming conventions within Dart and Flutter projects, leading to more readable, maintainable, and understandable codebases.

Core Features & Use Cases

Standardized Prefixes/Suffixes: Enforces conventions for interfaces (I prefix), implementations (Impl suffix), use cases (Ucs suffix), datasources (Dts suffix), extensions (X suffix), and mixins (Mxn suffix).
Folder and Variable Naming: Provides guidelines for abbreviations and folder organization (e.g., using repo instead of repository, organizing multiple datasources in api/, excell/, csv/ folders).
Acronym Handling: Ensures consistent capitalization of acronyms.
Use Case: When creating a new repository for data fetching, apply the IRepo interface and RepoImpl implementation naming conventions to ensure consistency with existing project patterns.

Quick Start

Apply the dart-naming-conventions skill to ensure all new classes follow the specified interface and implementation naming patterns.

Frequently Asked Questions about dart-naming-conventions

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

FAQPage Schema

How do I standardize Dart and Flutter naming conventions for interfaces and implementations?▼

Standardize Flutter naming by applying the I prefix to interfaces and the Impl suffix to implementations. This ensures consistency across classes, making the codebase more readable and maintainable for Flutter development.

What are the recommended suffixes for Dart use cases, datasources, and mixins?▼

Recommended Dart suffixes include Ucs for use cases, Dts for datasources, X for extensions, and Mxn for mixins. Applying these specific suffixes clarifies component roles and enforces clean code architecture.

How should I structure folders for multiple datasources in a Flutter project?▼

Organize multiple datasources in Flutter by creating distinct subfolders like api/, excell/, and csv/ within the datasource directory. Use the abbreviation repo instead of repository to maintain a clean folder structure.

What is the best way to handle acronym capitalization in Dart code?▼

Handle acronym capitalization in Dart by enforcing consistent casing rules across the entire project. This standardization eliminates ambiguity and improves code readability for all technical acronyms used.

Does this naming convention approach work for refactoring existing Dart codebases?▼

Yes, applying standardized naming prefixes and suffixes is highly effective for refactoring existing Dart codebases. It resolves inconsistency and ambiguity, leading to a more understandable and maintainable project structure.