project-setup

A setup workflow for customizing a new app made from a Flutter template. It handles the app name, package identifier, icons, splash screen, supported platforms, and setup validation.

In plain words
What is it for?
Use it when turning the template into a specific app, checking platform cleanup, configuring branding, deciding on Firebase or secrets, generating code, and validating the result.
Why use it?
It avoids inconsistent manual changes and protects sensitive files such as environment settings, signing keys, and encrypted secrets.

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/strvcom/flutter-template/project-setup
Any agent
npx skills add strvcom/flutter-template --skill project-setup
Clone the repo
git clone --depth 1 https://github.com/strvcom/flutter-template

Made for: Claude Code, Codex.

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,437 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.00044 $0.02437
Opus 5 $0.00022 $0.01218
Sonnet 5 $0.00009 $0.00487
Haiku 4.5 $0.00004 $0.00244

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

Security

Grade A, and why

project-setup 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.

.agents/skills/project-setup/SKILL.md · 145 lines

How it starts

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

Flutter Template Project Setup

Use this skill when preparing a new app from this template or reviewing whether setup is complete.

Read First

  • AGENTS.md
  • README.md
  • project_setup/README.md
  • project_setup/lib/configuration.dart
  • makefile
  • docs/PROJECT_OVERVIEW.md
  • docs/PROJECT_GUIDELINES.md

Safety Rules

  • Keep deterministic mutations in the Dart setup tool under project_setup/.
  • Do not touch decrypted .env*, signing files, or extras/secrets/ unless the task explicitly includes secrets or signing setup.
  • Do not hand-edit generated files such as *.g.dart, *.freezed.dart, *.gr.dart, or lib/assets/*.
  • Treat Firebase, notifications, Remote Config, and web configuration as scaffolded until verified in lib/app/setup/setup_app.dart.

Setup Workflow

  1. Inspect the requested app name, package name, supported platforms, flavors, Firebase plan, and secret/signing needs.
  2. Update project_setup/lib/configuration.dart for:
    • icon variants and colors
    • splash background colors and platforms
    • old/new app name
    • old/new package name
  3. Verify setup image inputs:
    • project_setup/resources/icon.png must be 900x900
    • project_setup/resources/splash.png must be 768x768
  4. Run make setup from the repository root and select the needed setup operation.
  5. If platform support changes, run the Platform Cleanup Workflow below.
  6. If Firebase support changes, run the Firebase Workflow below.
  7. If secrets or signing material are needed, use the secrets-bootstrap workflow.
  8. Run the AI Workflow Tooling Check below so repo-local skills and scripts are usable.
  9. Update the README First steps checklist to mark any completed setup items with [x].
  10. Run make gen after setup changes that affect routes, localization, generated assets, or annotations.
  11. Validate with fvm flutter analyze and the relevant tests.

AI Workflow Tooling Check

Use this when setting up a new clone, preparing AI workflows, or debugging skill scripts.

Read the full file on GitHub · 145 lines

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 · 145 lines · 44 tokens per session scan A 3cbdead03721

Subscribe to this mod's changes

project-setup is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 2,437 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

orca-emulator-android

Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…

stablyai/orca · 104 tokens

speckit-analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

unoplatform/uno · 32 tokens

add-sample

Create a SamplesApp sample page with correct theming and attributes. Use when adding UI samples for controls.

unoplatform/uno · 21 tokens

mapping-to-snomed

Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…

maziyarpanahi/openmed · 205 tokens

android-tombstone-symbolication

Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…

dotnet/skills · 176 tokens

auditing-subgroup-fairness

Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…

maziyarpanahi/openmed · 148 tokens