flutter-logging

A guide for adding structured logs to Flutter apps through an app-owned logging interface. It covers log levels, development and production output, error reporting, state changes, and page navigation.

In plain words
What is it for?
Use it to configure debug, info, warning, and error logs, connect Cubit errors to error handling, track routes, and pass logging through constructors.
Why use it?
It makes application problems and user flows easier to trace without letting business code depend directly on a logging package.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/yendangn/flutter-app-builder/flutter-logging
Any agent
npx skills add yendangn/flutter-app-builder --skill flutter-logging
Clone the repo
git clone --depth 1 https://github.com/yendangn/flutter-app-builder

Made for: Claude Code, Codex.

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 666 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00054 $0.00666
Opus 5 $0.00027 $0.00333
Sonnet 5 $0.00011 $0.00133
Haiku 4.5 $0.00005 $0.00067

Measured 2d ago against content hash e47569bf75a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

flutter-logging scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/flutter-logging/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Flutter Logging

Full reference: template.md

Key rules

  • AppLogger is the app-owned interface. Never import package:logger/logger.dart outside logger_impl.dart.
  • Four log levels: debug, info, warn, error. All accept optional error and stackTrace params.
  • LoggerImpl wraps the logger package. Configured with PrettyPrinter in dev/uat, SimplePrinter in prod.
  • Logging is enabled based on AppConfig.enableLogging. Prod builds log only errors.
  • Wire AppLogger into BlocObserver to log state transitions and errors automatically.
  • Route observer (RouteObserver) logs page pushes/pops for screen tracking.
  • Pass AppLogger via constructor injection — never resolve via getIt inside business logic.

AppBlocObserver pattern

Set in bootstrap — logs every cubit state change and routes all bloc errors to ErrorHandler:

class AppBlocObserver extends BlocObserver {
  AppBlocObserver({required AppLogger logger, required ErrorHandler errorHandler})
      : _logger = logger, _errorHandler = errorHandler;
  final AppLogger _logger;
  final ErrorHandler _errorHandler;

  @override
  void onError(BlocBase<dynamic> bloc, Object error, StackTrace stackTrace) {
    super.onError(bloc, error, stackTrace);
    _errorHandler.handleError(error, stackTrace, reason: '${bloc.runtimeType} error');
  }

  @override
  void onChange(BlocBase<dynamic> bloc, Change<dynamic> change) {
    super.onChange(bloc, change);
    _logger.debug('${bloc.runtimeType}: state → ${change.nextState.runtimeType}');
  }
}

Bootstrap wiring:

Bloc.observer = AppBlocObserver(
  logger: getIt<AppLogger>(),
  errorHandler: getIt<ErrorHandler>(),
);

Route observer

AppRouteObserver extends NavigatorObserver — logs screen pushes/pops. Wire into GoRouter observers:

final router = GoRouter(
  observers: [AppRouteObserver(logger: getIt<AppLogger>())],
);

Files

lib/src/core/logging/
  app_logger.dart          ← interface (debug / info / warn / error)
  logger_impl.dart         ← only file that imports package:logger
lib/src/core/bloc/
  app_bloc_observer.dart   ← logs BLoC state changes + routes errors to ErrorHandler
  app_route_observer.dart  ← logs screen push/pop via NavigatorObserver

Read the full file on GitHub · 80 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 80 lines · 54 tokens per session scan A e47569bf75a9

Subscribe to this mod's changes

flutter-logging is a skill published in the GitHub repository yendangn/flutter-app-builder (5 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 666 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens