skills/stac-quickstart/SKILL.md
Help initialize and validate a Stac-enabled Flutter project and ship a first server-driven screen. Use when users ask to set up Stac CLI, run stac init/build/deploy, verify project prerequisites, or troubleshoot first-run setup and missing configuration files.
npx skillsauth add stacdev/stac stac-quickstartInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to set up Stac in a Flutter project, verify required files, and complete the first build/deploy loop safely.
scripts/check_environment.sh to verify local tooling.scripts/validate_project_layout.py --project-root <path> to confirm Stac project structure.references/setup-checklist.md.references/cli-workflow.md.references/project-layout.md.references/setup-checklist.md when beginning a fresh setup.references/cli-workflow.md when sequencing stac commands.references/project-layout.md when validating missing files or wrong structure.scripts/check_environment.sh: verifies flutter, dart, and stac availability.scripts/validate_project_layout.py: validates required Stac project files.development
Diagnose Stac build, deploy, rendering, caching, and navigation issues using repeatable checks. Use when users report stac build finding no screens, deploy mismatches, runtime unknown widget/action errors, cache staleness, or migration regressions.
development
Build Stac DSL screens and themes from product requirements with safe defaults and reusable templates. Use when users ask to create or refactor StacScreen files, map UI requirements to Stac widgets/actions/styles, or scaffold new screen/theme files.
tools
Scaffold and integrate custom Stac widgets and actions with parsers and registration checks. Use when users ask to build new StacParser or StacActionParser implementations, generate custom model classes, or verify parser registration inside Stac.initialize.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.