stacdev/stac

stac-screen-builder

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.

First seen Feb 9, 2026

Installation

$ npx skills add stacdev/stac --skill stac-screen-builder

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from stacdev/stac.

npx skills add stacdev/stac

Browse all from stacdev/stac

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 920
License LICENSE
Default branch main
Open issues 15
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,805 B
  • docs SUMMARY.md 276 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 78 installs

SKILL.md

Stac Screen Builder

Overview

Use this skill to convert feature requirements into maintainable Stac DSL screens and theme definitions.

Workflow

  1. Translate user requirements into route names, states, and actions.
  2. Select widgets using references/widget-selector.md.
  3. Select actions using references/action-recipes.md.
  4. Apply style patterns from references/style-recipes.md.
  5. Apply route semantics from references/navigation-patterns.md.
  6. Scaffold files using scripts when requested.

Required Inputs

  • Target screen name (snake_case recommended).
  • Desired interactions (navigation, network, forms, state changes).
  • Whether a theme reference is needed.

Output Contract

  • Return valid Stac DSL snippets with @StacScreen or @StacThemeRef.
  • Keep generated screen names stable and explicit.
  • Use built-in Stac widgets/actions first, then custom extensions if needed.

References

  • Read references/widget-selector.md to choose layout and interactive widgets.
  • Read references/action-recipes.md for navigation/form/network/state actions.
  • Read references/style-recipes.md for color, spacing, and text style patterns.
  • Read references/navigation-patterns.md for stack-safe navigation actions.

Scripts

  • scripts/new_screen.py --screen-name <name> --out-dir <path> [--with-navigation]
  • scripts/newthemeref.py --theme-name <name> --out-file <path>

Templates

  • assets/templates/screen.dart.tmpl
  • assets/templates/theme_ref.dart.tmpl