agentleFS
Google CloudKnown publisherGoogleCloudPlatform/devrel-demos/agents/elevating-antigravity/skills/making-forms-demo/SKILL.md

making-forms-demo

Skill397 starsChanged 9 days agoApache-2.0View on GitHub

Interviews the user for critical implementation details needed to generate a Web Form. Manages FORM namespace in `user_prefs.json`. Use when making Web Forms.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Check if user_prefs.json exists in the workspace root.

    line 15
  2. Very specific:

    Use the selected value as FIELD_VALIDATION_TYPE.

    line 23
  3. Very specific:

    Write the user's selected form preferences to a user_prefs.json file in the workspace root directory using the write_to_file tool (or …

    line 34
  4. Very specific:

    Write the selections to user_prefs.json in the workspace root.

    line 47

≈ “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

Making forms

Interviews the user for critical implementation details needed to generate a Web Form.

Workflow Steps

  1. Confirm Intent & Hydrate State: Check if user_prefs.json exists in the workspace root. If present, read the "FORMS" object to identify any previously saved preferences. Tell the user that a form has been identified and that a few questions must be answered (or confirmed) before building the form.
  2. Query Validation Type: Invoke the ask_question tool to present the user with an option selection UI. If previously saved values exist in user_prefs.json, prefix those option strings with "(Current Setting) " and list them first:

    • Question: "How would you like to handle field validation? (select all that apply)"
    • Options: ["Client-side validation", "Server-side validation"]

    Use the selected value as FIELD_VALIDATION_TYPE.

  3. Query Validation Location: Invoke the ask_question tool to present the user with an option selection UI. If a previously saved value exists in user_prefs.json, prefix that option string with "(Current Setting) " and list it first:

    • Question: "How would you like to handle validation messages?"
    • Options: ["Above the field", "Below the field", "Summary Card", "Tooltip"]

    Use the selected value as FIELD_VALIDATION_LOCATION.

  4. Persist User Preferences: Write the user's selected form preferences to a user_prefs.json file in the workspace root directory using the write_to_file tool (or overwrite existing preferences). This guarantees that future agent invocations and subagents are grounded in the user's exact specifications without needing to re-interview them:

    {
      "FORMS": {
        "FIELD_VALIDATION_TYPE": ["<SELECTED_VALUES>"],
        "FIELD_VALIDATION_LOCATION": "<SELECTED_VALUE>"
      }
    }

Mock Skill Instructions

Since this skill is just a mock skill for illustrating how to create interviewer UI within the chat window, don't actually create a form. Instead:

  1. Write the selections to user_prefs.json in the workspace root.
  2. Output the form selections to the user as confirmation using the template below:

For each field: <FIELD_NAME>: <SELECTED_VALUE>

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.