skills.rest
GlowLED
GlowLEDCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

busic-coding-conventions

Enforce BuSic coding conventions for Dart/Flutter projects.

23|8|Updated Mar 2, 2026
Search Tags:#coding#conventions#code-quality#flutter#lint#dart
One-click install
npx skills add https://github.com/GlowLED/BuSic --skill busic-coding-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: busic-coding-conventions
Source: https://github.com/GlowLED/BuSic/tree/main/.agents/skills/busic-coding-conventions
Command: npx skills add https://github.com/GlowLED/BuSic --skill busic-coding-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BuSic coding conventions establish a single, shared standard for naming, file structure, import practices, logging, and error handling across the Dart/Flutter codebase, reducing ambiguity and onboarding time.

Core Features & Use Cases

  • Standard naming: file names use snake_case; public types use PascalCase; provider names can be codegen-generated.
  • Import and dependency guidelines: prefer relative imports and avoid package imports unless necessary.
  • Logging and error handling: enforce AppLogger usage and consistent error handling patterns.
  • Code structure and readability: one major public type per file; comments explain why; ensure texts are internationalization-ready.
  • Documentation and references: link to docs and style guides to ensure continued adherence.

Quick Start

Start applying these conventions in your next Dart/Flutter module to align with BuSic's coding standards.

Frequently Asked Questions about busic-coding-conventions

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

FAQPage Schema
What are the standard Flutter naming conventions for files and public types?▼

Standard Flutter naming conventions require snake_case for filenames and PascalCase for public types to maintain consistency. Adhering to these rules improves code readability and structure across Dart projects.

How do I enforce consistent error handling and logging in Dart?▼

Enforce consistent error handling and logging in Dart by utilizing AppLogger for all log outputs. This establishes a unified error handling pattern, reducing ambiguity and ensuring reliable tracking across your codebase.

Should I use relative imports or package imports in Flutter projects?▼

Relative imports are preferred over package imports in Flutter projects unless absolutely necessary. This import guideline minimizes dependency confusion and keeps your Dart module structure clean and maintainable.

How do I structure Dart files for better code readability?▼

Structure Dart files for better code readability by limiting one major public type per file. Additionally, ensure texts are internationalization-ready and comments explain the why behind the code.

Does this coding convention standard apply to existing Flutter modules?▼

Yes, these coding conventions apply to both new features and existing Flutter modules. Applying these standards across your Dart codebase reduces onboarding time and aligns ongoing development with shared rules.

Related Skills

Explore More Software Engineering Skills→
morodomimorodomi
8

flutter-quality

Run dart analyze, dart format, and flutter test on Flutter projects.

Community
Advanced
3balljugglerYu3balljugglerYu

spec-verifying

Verify EARS specification coverage against Dart test files.

Community
Advanced
wildbitcawildbitca
1

flutter-error-handling-result

Implement Result<T> types for standardized async error handling in Flutter apps.

Official
Advanced
virajpvirajp
1

analysis-options

Configure strict Flutter analyzer and lint settings in analysis_options.yaml.

Community
Intermediate