agentleFS
Sign inStart free
osocietyosociety/vernet/.github/skills/flutter-feature-iteration/SKILL.md

flutter-feature-iteration

Skill566 starsChanged 13 days agoApache-2.0View on GitHub

Implement or refine Vernet Flutter features and UI, including form controls, network-tool screens, responsive layouts, and focused regression coverage.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this for adding or iteratively refining a Vernet screen, control, or user-visible workflow.

    line 9
  2. Very specific:

    Start from the named screen, behavior, or nearby test.

    line 13
  3. Very specific:

    Follow Vernet's existing boundaries: UI in pages/widgets, network operations in services, structured results in models, and feature state …

    line 14
  4. Distinctive:

    Run the narrowest relevant test, then analyze affected Dart code.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Flutter Feature Iteration

Use this for adding or iteratively refining a Vernet screen, control, or user-visible workflow.

Procedure

  1. Start from the named screen, behavior, or nearby test. State the expected behavior in observable terms and inspect the smallest owning UI/controller/service path before editing.
  2. Follow Vernet's existing boundaries: UI in pages/widgets, network operations in services, structured results in models, and feature state local to the feature. Read ARCHITECTURE.md before structural changes.
  3. Preserve established visual conventions. Make controls work with keyboard, focus, validation, loading, empty, and error states where applicable. Keep actions near the input they operate on when that matches the requested workflow; account for mobile and desktop constraints.
  4. For image or web presentation work, preserve source aspect ratios unless intentional cropping is requested. Check the target section against the current live or reference behavior when supplied; do not overwrite existing assets or copy unrelated design wholesale.
  5. Make the smallest adjacent change and add/update a focused widget or integration test for the visible behavior. Avoid unrelated redesigns and do not put network calls directly in widgets.
  6. Run the narrowest relevant test, then analyze affected Dart code. If an app is attached, hot reload or hot restart and verify the changed interaction on the target screen/device.
  7. Summarize the user-visible change and the exact test/device/viewport used. Call out any requested visual state that could not be verified.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free