[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74EEQ3TN5F26DPBHSXDDP51":3,"skill-same:01M74EEQ3TN5F26DPBHSXDDP51":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M74EEQ3TN5F26DPBHSXDDP51","dart-coding",null,"Apply when writing or editing Dart (.dart) files. Behavioral corrections for null safety, async patterns, type system, error handling, and common antipatterns. Project conventions always override these defaults.","tamarillo-ai\u002Ftheta","tamarillo-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264659913?v=4","01M732W8TW61PS979NJ2W4Z6XZ","tamarillo.ai","01M732W8VRBBGT4F0Q3B2HNGTQ",15,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcodex-cli\u002Fregression\u002Fjust-works\u002F.codex\u002Fskills\u002Fdart-coding\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: dart-coding\ndescription: Apply when writing or editing Dart (.dart) files. Behavioral corrections for null safety, async patterns, type system, error handling, and common antipatterns. Project conventions always override these defaults.\n---\n\n# Dart Coding\n\nMatch the project's existing conventions. When uncertain, read 2-3 existing files to infer the local style. Check `pubspec.yaml` for SDK constraints, `analysis_options.yaml` for lint rules, and any `.dart_tool\u002F` config for code generation. These defaults apply only when the project has no established convention.\n\n## Never rules\n\nThese are unconditional. They prevent bugs and crashes regardless of project style.\n\n- **Never null-check a non-`final` field directly** — Dart's flow analysis only promotes `final`, local, or private variables. After the check, the field could still change between the test and the use. Copy to a local first.\n\n```dart\n\u002F\u002F Wrong: _temp is mutable; not promoted to non-null\nif (_temp != null) {\n  print(_temp.length); \u002F\u002F compile error or stale value\n}\n\n\u002F\u002F Correct: local is promoted\nfinal t = _temp;\nif (t != null) {\n  print(t.length);\n}\n```\n\n- **Never use `!` to \"guarantee\" non-null without prior verification** — `!` is a runtime cast that throws `TypeError` when the value is null. It silently turns a static type error into a production crash. Use `??`, `if`-checks, or pattern matching first.\n- **Never mix `late` with `?`** — `late String?` confuses two distinct states (uninitialized vs explicitly null) and defeats the purpose of `late`. Pick one: `late String` (deferred init, never null) or `String?` (may be null at any time).\n- **Never index a `Map` without a null-check or `!` for known-present keys** — `map['k']` returns `V?`. Calling `.length` on the result without handling null is a compile error in null-safe code; using `!` blindly turns missing keys into runtime crashes.\n\n```dart\n\u002F\u002F Wrong: subscript returns null on missing key\nfinal n = map['k'].length;\n\n\u002F\u002F Correct: handle missing key explicitly\nfinal v = map['k'];\nfinal n = v?.length ?? 0;\n\n\u002F\u002F Correct: assert presence with rationale\nfinal n = map['k']!.length; \u002F\u002F key inserted at line 12, guaranteed present\n```\n\n- **Never discard a `Future`** — without `await` (or explicit `unawaited(...)`), errors silently vanish and ordering is undefined. Enable `unawaited_futures` lint. Use `unawaited(future)` only when you intentionally want fire-and-forget behavior.\n- **Never `await` sequentially in a loop for independent operations** — serializes work that could run in parallel. Use `Future.wait` for fan-out.\n\n```dart\n\u002F\u002F Wrong: serial round-trips\nfor (final id in ids) {\n  results.add(await fetch(id));\n}\n\n\u002F\u002F Correct: concurrent\nfinal results = await Future.wait(ids.map(fetch));\n```\n\n- **Never declare `async` without `await`, `throw`, or a `Future` return inside** — meaningless overhead and confuses callers about whether the function is asynchronous.\n- **Never leave a `StreamSubscription` uncancelled** — leaks memory and continues firing callbacks after the owner is disposed. `await sub.cancel()` in `dispose`\u002Fcleanup paths.\n- **Never re-listen to a single-subscription stream** — throws `StateError`. HTTP, file, and most service streams are single-subscription. Use `.asBroadcastStream()` only when you genuinely need multiple listeners.\n- **Never catch `Error` subtypes** — `StateError`, `ArgumentError`, `RangeError`, etc. signal programming bugs. Catching them hides defects. Catch `Exception` for recoverable failures; let `Error`s crash so they get fixed.\n\n```dart\n\u002F\u002F Wrong: hides programmer bugs\ntry {\n  doWork();\n} on Error catch (_) {\n  \u002F\u002F swallowed StateError, ArgumentError, etc.\n}\n\n\u002F\u002F Correct: catch only recoverable failures\ntry {\n  doWork();\n} on FormatException catch (e, st) {\n  log.warning('bad input', e, st);\n}\n```\n\n- **Never use `dynamic` to mean \"any value\"** — `dynamic` silently disables static type checking, so typos and incompatible operations compile fine and crash at runtime. Use `Object?` plus `is`\u002Fpattern checks.\n\n## Records and patterns\n\nRecords (Dart 3) are immutable, structurally typed bundles. Field names are part of the type — `({int a, int b})` and `({int x, int y})` do not unify.\n\n```dart\n({String name, int age}) parseUser(Map\u003CString, Object?> json) =>\n    (name: json['name'] as String, age: json['age'] as int);\n\nfinal u = parseUser(payload);\nprint('${u.name}: ${u.age}');\n```\n\nUse a class instead of a record when behavior, methods, or computed properties are needed. Records are data only.\n\nSealed types plus switch expressions give exhaustiveness — the compiler enforces every case, no `default` needed:\n\n```dart\nsealed class Shape {}\nclass Circle extends Shape { Circle(this.r); final double r; }\nclass Square extends Shape { Square(this.side); final double side; }\n\ndouble area(Shape s) => switch (s) {\n  Circle(:final r) => 3.14159 * r * r,\n  Square(:final side) => side * side,\n};\n```\n\nIrrefutable patterns crash at runtime when the value does not match — `var [a, b] = list` throws if `list.length != 2`. For fallible matches, use `if (... case ...)`:\n\n```dart\n\u002F\u002F Crashes on length mismatch\nfinal [a, b] = pair;\n\n\u002F\u002F Safe: only runs when shape matches\nif (list case [final a, final b]) {\n  use(a, b);\n}\n```\n\n`when` guards belong inside `case`, not as a separate `if`:\n\n```dart\n\u002F\u002F Wrong\nswitch (point) {\n  case Point(:final x):\n    if (x > 0) handle(x);\n}\n\n\u002F\u002F Correct\nswitch (point) {\n  case Point(:final x) when x > 0:\n    handle(x);\n}\n```\n\n## Async, Future, Stream\n\nWrap `await` in `try`\u002F`catch` (or chain `.catchError`) at the boundary where you can act on failure. `async` propagates errors via the returned `Future` — they do not surface unless awaited.\n\nAvoid `FutureOr\u003CT>` as a return type — callers cannot tell whether to `await`. Pick `T` or `Future\u003CT>`.\n\nFor broadcast vs single-subscription streams: HTTP responses, file reads, and most platform streams are single-subscription. Convert with `.asBroadcastStream()` only when multiple consumers need the same events.\n\nAlways cancel subscriptions in `dispose`\u002Fcleanup:\n\n```dart\nclass _MyState extends State\u003CMyWidget> {\n  StreamSubscription\u003CEvent>? _sub;\n\n  @override\n  void initState() {\n    super.initState();\n    _sub = service.events.listen(_handle);\n  }\n\n  @override\n  void dispose() {\n    _sub?.cancel();\n    super.dispose();\n  }\n}\n```\n\n## Collections\n\nPrefer literals over constructors. Literals are clearer, allow inference, and support `const`:\n\n```dart\n\u002F\u002F Wrong\nfinal xs = List\u003CPoint>();\nfinal m = Map\u003CString, int>();\n\n\u002F\u002F Correct\nfinal xs = \u003CPoint>[];\nfinal m = \u003CString, int>{};\n```\n\nUse spread, `if`, and `for` inside literals rather than imperative `addAll`\u002F`if`\u002F`for` outside:\n\n```dart\nfinal items = [\n  ...defaultItems,\n  if (showExtras) extraItem,\n  for (final id in ids) Item(id),\n];\n```\n\nUse `isEmpty`\u002F`isNotEmpty`, never `length == 0` or `length > 0` — clearer and cheap on lazy iterables where `length` may walk the whole collection.\n\nUse `whereType\u003CT>()` instead of `where((e) => e is T).cast\u003CT>()` — same intent, one call, fewer chances to drop the type.\n\n`final list = [...]` only prevents rebinding the variable; the items remain mutable. For true immutability use `List.unmodifiable(...)` or a `const` literal:\n\n```dart\nfinal mutableItems = [1, 2, 3];        \u002F\u002F can still call .add\nfinal frozen = List\u003Cint>.unmodifiable([1, 2, 3]);\nconst compileTime = [1, 2, 3];          \u002F\u002F const list, deeply immutable\n```\n\n## Classes\n\nPrefer `final` fields. Add a `const` constructor when all fields are `final` and immutable — enables `const` use sites:\n\n```dart\nclass Point {\n  const Point(this.x, this.y);\n  final double x;\n  final double y;\n}\n\nconst origin = Point(0, 0);\n```\n\nClass modifiers express different intents — do not conflate them:\n\n| Modifier | Meaning |\n|----------|---------|\n| `sealed` | Exhaustive switching; cannot be extended outside the library |\n| `final` | Cannot be extended or implemented outside the library |\n| `base` | Can only be extended (not implemented) |\n| `interface` | Can only be implemented (not extended) |\n\nSubclasses do not inherit named constructors — reimplement them in the subclass and forward to `super`.\n\nFactory constructors cannot access `this`. Use them for caching, returning a subtype, validating input before construction, or returning an existing instance:\n\n```dart\nclass Logger {\n  static final _cache = \u003CString, Logger>{};\n\n  factory Logger(String name) => _cache.putIfAbsent(name, () => Logger._(name));\n\n  Logger._(this.name);\n  final String name;\n}\n```\n\nOverride `hashCode` whenever overriding `==`. Avoid overriding `==` on mutable classes — using a mutable instance as a `Set` element or `Map` key breaks the collection when the field changes.\n\n## Errors\n\nCustom failure types `implements Exception`, never `extends Error`:\n\n```dart\nclass PaymentFailed implements Exception {\n  PaymentFailed(this.reason);\n  final String reason;\n  @override\n  String toString() => 'PaymentFailed: $reason';\n}\n```\n\nUse `on Type catch (e, st)` for typed catches with stack traces. `rethrow` preserves the original stack — use it instead of `throw e`:\n\n```dart\ntry {\n  await sendPayment();\n} on TimeoutException catch (e, st) {\n  log.warning('payment timed out', e, st);\n  rethrow;\n} on PaymentFailed catch (e, st) {\n  log.severe('payment failed: ${e.reason}', e, st);\n  return Result.failure(e);\n}\n```\n\n## Style\n\nNaming follows the official guidelines:\n\n| Element | Style | Example |\n|---------|-------|---------|\n| Types, extensions, typedefs, enums | `UpperCamelCase` | `HttpClient`, `Iterable` |\n| Members, parameters, locals, constants | `lowerCamelCase` | `itemCount`, `defaultTimeout` |\n| Libraries, files, directories, prefixes | `lowercase_with_underscores` | `user_profile.dart` |\n\nAcronyms: capitalize only the first letter for 3+ letters (`Http`, `Uri`, `Id`); two-letter acronyms stay fully capitalized (`IO`, `IP`, `OS`).\n\nUse cascade `..` for sequential operations on the same target:\n\n```dart\n\u002F\u002F Wrong\nfinal btn = Button();\nbtn.text = 'Save';\nbtn.onTap = save;\nbtn.enabled = true;\n\n\u002F\u002F Correct\nfinal btn = Button()\n  ..text = 'Save'\n  ..onTap = save\n  ..enabled = true;\n```\n\nTrailing commas drive multi-line `dart format` output — add them in argument lists, parameter lists, and collection literals when you want each item on its own line.\n\nNaming signals aliasing: `to___()` returns a snapshot (independent copy), `as___()` returns a view that reflects future changes. Pick the prefix that matches what the method actually returns.\n\n## Common antipatterns\n\n- **Untyped generics fill with `dynamic`** — `List\u003Cnum>` not bare `List`. A bare `List` is `List\u003Cdynamic>` and discards type checking on every element access.\n- **Prefer `is` checks and patterns over `as` casts** — `as` throws at runtime on type mismatch; `is` and patterns are statically verified.\n\n```dart\n\u002F\u002F Wrong: throws if x is not a String\nfinal s = (x as String).toUpperCase();\n\n\u002F\u002F Correct: pattern; only runs when x is a String\nif (x case final String s) {\n  use(s.toUpperCase());\n}\n```\n\n- **Don't initialize nullable variables to `null` explicitly** — the default for a nullable type is already `null`.\n\n```dart\n\u002F\u002F Wrong\nItem? x = null;\n\n\u002F\u002F Correct\nItem? x;\n```\n\n- **Avoid positional `bool` parameters** — call sites read as `spawn(fn, args, false)` with no clue what `false` means. Use named parameters:\n\n```dart\n\u002F\u002F Wrong\nIsolate.spawn(work, args, false);\n\n\u002F\u002F Correct\nIsolate.spawn(work, args, paused: false);\n```\n\n- **A setter without a matching getter is broken** — `+=`, `??=`, and similar compound operators read before they write, so they fail. Either pair the setter with a getter or expose a regular method.\n","# Dart Coding\n\nMatch the project's existing conventions. When uncertain, read 2-3 existing files to infer the local style. Check `pubspec.yaml` for SDK constraints, `analysis_options.yaml` for lint rules, and any `.dart_tool\u002F` config for code generation. These defaults apply only when the project has no established convention.\n\n## Never rules\n\nThese are unconditional. They prevent bugs and crashes regardless of project style.\n\n- **Never null-check a non-`final` field directly** — Dart's flow analysis only promotes `final`, local, or private variables. After the check, the field could still change between the test and the use. Copy to a local first.\n\n```dart\n\u002F\u002F Wrong: _temp is mutable; not promoted to non-null\nif (_temp != null) {\n  print(_temp.length); \u002F\u002F compile error or stale value\n}\n\n\u002F\u002F Correct: local is promoted\nfinal t = _temp;\nif (t != null) {\n  print(t.length);\n}\n```\n\n- **Never use `!` to \"guarantee\" non-null without prior verification** — `!` is a runtime cast that throws `TypeError` when the value is null. It silently turns a static type error into a production crash. Use `??`, `if`-checks, or pattern matching first.\n- **Never mix `late` with `?`** — `late String?` confuses two distinct states (uninitialized vs explicitly null) and defeats the purpose of `late`. Pick one: `late String` (deferred init, never null) or `String?` (may be null at any time).\n- **Never index a `Map` without a null-check or `!` for known-present keys** — `map['k']` returns `V?`. Calling `.length` on the result without handling null is a compile error in null-safe code; using `!` blindly turns missing keys into runtime crashes.\n\n```dart\n\u002F\u002F Wrong: subscript returns null on missing key\nfinal n = map['k'].length;\n\n\u002F\u002F Correct: handle missing key explicitly\nfinal v = map['k'];\nfinal n = v?.length ?? 0;\n\n\u002F\u002F Correct: assert presence with rationale\nfinal n = map['k']!.length; \u002F\u002F key inserted at line 12, guaranteed present\n```\n\n- **Never discard a `Future`** — without `await` (or explicit `unawaited(...)`), errors silently vanish and ordering is undefined. Enable `unawaited_futures` lint. Use `unawaited(future)` only when you intentionally want fire-and-forget behavior.\n- **Never `await` sequentially in a loop for independent operations** — serializes work that could run in parallel. Use `Future.wait` for fan-out.\n\n```dart\n\u002F\u002F Wrong: serial round-trips\nfor (final id in ids) {\n  results.add(await fetch(id));\n}\n\n\u002F\u002F Correct: concurrent\nfinal results = await Future.wait(ids.map(fetch));\n```\n\n- **Never declare `async` without `await`, `throw`, or a `Future` return inside** — meaningless overhead and confuses callers about whether the function is asynchronous.\n- **Never leave a `StreamSubscription` uncancelled** — leaks memory and continues firing callbacks after the owner is disposed. `await sub.cancel()` in `dispose`\u002Fcleanup paths.\n- **Never re-listen to a single-subscription stream** — throws `StateError`. HTTP, file, and most service streams are single-subscription. Use `.asBroadcastStream()` only when you genuinely need multiple listeners.\n- **Never catch `Error` subtypes** — `StateError`, `ArgumentError`, `RangeError`, etc. signal programming bugs. Catching them hides defects. Catch `Exception` for recoverable failures; let `Error`s crash so they get fixed.\n\n```dart\n\u002F\u002F Wrong: hides programmer bugs\ntry {\n  doWork();\n} on Error catch (_) {\n  \u002F\u002F swallowed StateError, ArgumentError, etc.\n}\n\n\u002F\u002F Correct: catch only recoverable failures\ntry {\n  doWork();\n} on FormatException catch (e, st) {\n  log.warning('bad input', e, st);\n}\n```\n\n- **Never use `dynamic` to mean \"any value\"** — `dynamic` silently disables static type checking, so typos and incompatible operations compile fine and crash at runtime. Use `Object?` plus `is`\u002Fpattern checks.\n\n## Records and patterns\n\nRecords (Dart 3) are immutable, structurally typed bundles. Field names are part of the type — `({int a, int b})` and `({int x, int y})` do not unify.\n\n```dart\n({String name, int age}) parseUser(Map\u003CString, Object?> json) =>\n    (name: json['name'] as String, age: json['age'] as int);\n\nfinal u = parseUser(payload);\nprint('${u.name}: ${u.age}');\n```\n\nUse a class instead of a record when behavior, methods, or computed properties are needed. Records are data only.\n\nSealed types plus switch expressions give exhaustiveness — the compiler enforces every case, no `default` needed:\n\n```dart\nsealed class Shape {}\nclass Circle extends Shape { Circle(this.r); final double r; }\nclass Square extends Shape { Square(this.side); final double side; }\n\ndouble area(Shape s) => switch (s) {\n  Circle(:final r) => 3.14159 * r * r,\n  Square(:final side) => side * side,\n};\n```\n\nIrrefutable patterns crash at runtime when the value does not match — `var [a, b] = list` throws if `list.length != 2`. For fallible matches, use `if (... case ...)`:\n\n```dart\n\u002F\u002F Crashes on length mismatch\nfinal [a, b] = pair;\n\n\u002F\u002F Safe: only runs when shape matches\nif (list case [final a, final b]) {\n  use(a, b);\n}\n```\n\n`when` guards belong inside `case`, not as a separate `if`:\n\n```dart\n\u002F\u002F Wrong\nswitch (point) {\n  case Point(:final x):\n    if (x > 0) handle(x);\n}\n\n\u002F\u002F Correct\nswitch (point) {\n  case Point(:final x) when x > 0:\n    handle(x);\n}\n```\n\n## Async, Future, Stream\n\nWrap `await` in `try`\u002F`catch` (or chain `.catchError`) at the boundary where you can act on failure. `async` propagates errors via the returned `Future` — they do not surface unless awaited.\n\nAvoid `FutureOr\u003CT>` as a return type — callers cannot tell whether to `await`. Pick `T` or `Future\u003CT>`.\n\nFor broadcast vs single-subscription streams: HTTP responses, file reads, and most platform streams are single-subscription. Convert with `.asBroadcastStream()` only when multiple consumers need the same events.\n\nAlways cancel subscriptions in `dispose`\u002Fcleanup:\n\n```dart\nclass _MyState extends State\u003CMyWidget> {\n  StreamSubscription\u003CEvent>? _sub;\n\n  @override\n  void initState() {\n    super.initState();\n    _sub = service.events.listen(_handle);\n  }\n\n  @override\n  void dispose() {\n    _sub?.cancel();\n    super.dispose();\n  }\n}\n```\n\n## Collections\n\nPrefer literals over constructors. Literals are clearer, allow inference, and support `const`:\n\n```dart\n\u002F\u002F Wrong\nfinal xs = List\u003CPoint>();\nfinal m = Map\u003CString, int>();\n\n\u002F\u002F Correct\nfinal xs = \u003CPoint>[];\nfinal m = \u003CString, int>{};\n```\n\nUse spread, `if`, and `for` inside literals rather than imperative `addAll`\u002F`if`\u002F`for` outside:\n\n```dart\nfinal items = [\n  ...defaultItems,\n  if (showExtras) extraItem,\n  for (final id in ids) Item(id),\n];\n```\n\nUse `isEmpty`\u002F`isNotEmpty`, never `length == 0` or `length > 0` — clearer and cheap on lazy iterables where `length` may walk the whole collection.\n\nUse `whereType\u003CT>()` instead of `where((e) => e is T).cast\u003CT>()` — same intent, one call, fewer chances to drop the type.\n\n`final list = [...]` only prevents rebinding the variable; the items remain mutable. For true immutability use `List.unmodifiable(...)` or a `const` literal:\n\n```dart\nfinal mutableItems = [1, 2, 3];        \u002F\u002F can still call .add\nfinal frozen = List\u003Cint>.unmodifiable([1, 2, 3]);\nconst compileTime = [1, 2, 3];          \u002F\u002F const list, deeply immutable\n```\n\n## Classes\n\nPrefer `final` fields. Add a `const` constructor when all fields are `final` and immutable — enables `const` use sites:\n\n```dart\nclass Point {\n  const Point(this.x, this.y);\n  final double x;\n  final double y;\n}\n\nconst origin = Point(0, 0);\n```\n\nClass modifiers express different intents — do not conflate them:\n\n| Modifier | Meaning |\n|----------|---------|\n| `sealed` | Exhaustive switching; cannot be extended outside the library |\n| `final` | Cannot be extended or implemented outside the library |\n| `base` | Can only be extended (not implemented) |\n| `interface` | Can only be implemented (not extended) |\n\nSubclasses do not inherit named constructors — reimplement them in the subclass and forward to `super`.\n\nFactory constructors cannot access `this`. Use them for caching, returning a subtype, validating input before construction, or returning an existing instance:\n\n```dart\nclass Logger {\n  static final _cache = \u003CString, Logger>{};\n\n  factory Logger(String name) => _cache.putIfAbsent(name, () => Logger._(name));\n\n  Logger._(this.name);\n  final String name;\n}\n```\n\nOverride `hashCode` whenever overriding `==`. Avoid overriding `==` on mutable classes — using a mutable instance as a `Set` element or `Map` key breaks the collection when the field changes.\n\n## Errors\n\nCustom failure types `implements Exception`, never `extends Error`:\n\n```dart\nclass PaymentFailed implements Exception {\n  PaymentFailed(this.reason);\n  final String reason;\n  @override\n  String toString() => 'PaymentFailed: $reason';\n}\n```\n\nUse `on Type catch (e, st)` for typed catches with stack traces. `rethrow` preserves the original stack — use it instead of `throw e`:\n\n```dart\ntry {\n  await sendPayment();\n} on TimeoutException catch (e, st) {\n  log.warning('payment timed out', e, st);\n  rethrow;\n} on PaymentFailed catch (e, st) {\n  log.severe('payment failed: ${e.reason}', e, st);\n  return Result.failure(e);\n}\n```\n\n## Style\n\nNaming follows the official guidelines:\n\n| Element | Style | Example |\n|---------|-------|---------|\n| Types, extensions, typedefs, enums | `UpperCamelCase` | `HttpClient`, `Iterable` |\n| Members, parameters, locals, constants | `lowerCamelCase` | `itemCount`, `defaultTimeout` |\n| Libraries, files, directories, prefixes | `lowercase_with_underscores` | `user_profile.dart` |\n\nAcronyms: capitalize only the first letter for 3+ letters (`Http`, `Uri`, `Id`); two-letter acronyms stay fully capitalized (`IO`, `IP`, `OS`).\n\nUse cascade `..` for sequential operations on the same target:\n\n```dart\n\u002F\u002F Wrong\nfinal btn = Button();\nbtn.text = 'Save';\nbtn.onTap = save;\nbtn.enabled = true;\n\n\u002F\u002F Correct\nfinal btn = Button()\n  ..text = 'Save'\n  ..onTap = save\n  ..enabled = true;\n```\n\nTrailing commas drive multi-line `dart format` output — add them in argument lists, parameter lists, and collection literals when you want each item on its own line.\n\nNaming signals aliasing: `to___()` returns a snapshot (independent copy), `as___()` returns a view that reflects future changes. Pick the prefix that matches what the method actually returns.\n\n## Common antipatterns\n\n- **Untyped generics fill with `dynamic`** — `List\u003Cnum>` not bare `List`. A bare `List` is `List\u003Cdynamic>` and discards type checking on every element access.\n- **Prefer `is` checks and patterns over `as` casts** — `as` throws at runtime on type mismatch; `is` and patterns are statically verified.\n\n```dart\n\u002F\u002F Wrong: throws if x is not a String\nfinal s = (x as String).toUpperCase();\n\n\u002F\u002F Correct: pattern; only runs when x is a String\nif (x case final String s) {\n  use(s.toUpperCase());\n}\n```\n\n- **Don't initialize nullable variables to `null` explicitly** — the default for a nullable type is already `null`.\n\n```dart\n\u002F\u002F Wrong\nItem? x = null;\n\n\u002F\u002F Correct\nItem? x;\n```\n\n- **Avoid positional `bool` parameters** — call sites read as `spawn(fn, args, false)` with no clue what `false` means. Use named parameters:\n\n```dart\n\u002F\u002F Wrong\nIsolate.spawn(work, args, false);\n\n\u002F\u002F Correct\nIsolate.spawn(work, args, paused: false);\n```\n\n- **A setter without a matching getter is broken** — `+=`, `??=`, and similar compound operators read before they write, so they fail. Either pair the setter with a getter or expose a regular method.\n",{"name":5,"description":7},"main","08c084f718b2b842cd53622ce0b1a1fb2888ccef","test\u002Fcast-fixtures\u002Fcodex-cli\u002Fregression\u002Fjust-works\u002F.codex\u002Fskills\u002Fdart-coding",1,"https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai","2026-07-15 23:48:12",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add tamarillo-ai\u002Ftheta --skill dart-coding",{"tool":37,"command":38},"bunx","bunx skills add tamarillo-ai\u002Ftheta --skill dart-coding",{"tool":40,"command":41},"pnpm","pnpm dlx skills add tamarillo-ai\u002Ftheta --skill dart-coding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcodex-cli\u002Fregression\u002Fjust-works\u002F.codex\u002Fskills\u002Fdart-coding\u002FSKILL.md",true,[],[46,53,60,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M74FCAJ0RRFRJRQES26329E7","deploy-app","Deploy the application to staging or production environments.","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcursor\u002Fskills\u002Fbasic\u002F.cursor\u002Fskills\u002Fdeploy-app\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M74FC8GPJGCS0KTGKS1CJZZS","deploy","Deploy the application to environments.","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcursor\u002Fcombined\u002Ffull-config\u002F.cursor\u002Fskills\u002Fdeploy\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M74FC5RT3VTNZEK1F7NX5380","building-native-ui","Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.","MIT","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcopilot\u002Fskills\u002Fwith-references\u002F.github\u002Fskills\u002Fbuilding-native-ui\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M74FC1ZGP5R44HPGWWSW6P3B","create-section","Use when creating a new section for the AI Workshop presentation. Guides through title slide setup, layout choices, and content gathering. Activates when user wants to add a new topic section to the slideshow.","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcopilot\u002Fskills\u002Fbasic\u002F.github\u002Fskills\u002Fcreate-section\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M74FBZXSZ7GVP0HCGNR1BVNH","ship-checker","Run a full pre-ship review for this repo. Use when asked if a change is ready to deploy, publish, or ship.","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcopilot\u002Fcombined\u002Feverything\u002F.github\u002Fskills\u002Fship-checker\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M74FBY4N2E3ZERWBRM4S3DE6","lint-check","Run repository linters and report failures.","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcodex-cli\u002Fskills\u002Fagents-path\u002F.agents\u002Fskills\u002Flint-check\u002FSKILL.md",[],[]]