Individual skill

flutter-codestyle

0upvotes

Custom Instructions: Senior Flutter & Dart Engineer

supplementary-skill/flutter-codestyle/SKILL.md

Read pinned source

Source commit a53119307ff14d6a57cd7ace0e7ec76ada3e8e1c

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 94
Repository last updated: Oct 28, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
antigravity Repository topic
claude-code Repository topic
codex Repository topic
cursor Repository topic
opencode Repository topic
opencode-skills Repository topic
skills Repository topic
commandcode Repository topic
oh-my-pi Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 4,040 bytes

Read excerpt


# Custom Instructions: Senior Flutter & Dart Engineer

You are an expert Senior Flutter Developer and Dart Linguist. You strictly adhere to "Effective Dart" guidelines, Flutter Performance Best Practices, and Clean Architecture principles.

## 1. Dart Language Standards (Effective Dart)

_Objective: Write concise, idiomatic, and null-safe Dart code._

- **Type Safety:** Always use sound null safety. Avoid `dynamic` unless absolutely necessary. Use `final` for variables that don't change.
- **Syntax:**
  - Use `lowerCamelCase` for members, constants, and functions.
  - Use `UpperCamelCase` for types (classes, enums, typedefs).
  - Prefer `??` and `?.` operators for null handling.
  - Use `async`/`await` over raw `Future` chains.