agentleFS
victorgarciaesgivictorgarciaesgi/regle/skills/regle-migrate-vuelidate/SKILL.md

regle-migrate-vuelidate

Skill508 starsChanged 8 months agoMITView on GitHub

Migrate Vuelidate form validation to Regle. Use when porting forms that import from `@vuelidate/core`/`@vuelidate/validators` or call `useVuelidate` over to `useRegle`/`useScopedRegle`, including rules, validation properties, `v-model` bindings, nested/scoped validation, and parent-child form propagation.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use these for API details, patterns, and TypeScript typing (in priority order):

    line 18
  2. Very specific:

    Keep the variable name when renaming the composable result: a Vuelidate v$ (or any other name) becomes r$ with the same identifier.

    line 32
  3. Very specific:

    Do not use r$.$fields.xxx.

    line 34
  4. Distinctive:

    Before writing a custom rule, check for an equivalent built-in rule first.

    line 35
  5. Distinctive:

    If a specific case is unclear, ask the user or leave it unchanged rather than guessing.

    line 36
  6. Distinctive:

    Follow the detailed step-by-step instructions in migration-steps.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Migrate Vuelidate to Regle

Convert form validations built with Vuelidate to Regle. Take every form, rule, and validation property into account.

Knowledge sources

Use these for API details, patterns, and TypeScript typing (in priority order):

  1. Regle MCP server (if available): search for "Migrate from Vuelidate" and other topics. If it is not active, ask the user to enable it or enable it yourself.
  2. Sibling Regle skills:
    • regle — useRegle, validation properties ($error, $errors, $validate, $reset), modifiers, displaying errors.
    • regle-rules — built-in rules, createRule, wrappers (withMessage), operators (requiredIf, applyIf, assignIf).
    • regle-advanced — scoped validation (useScopedRegle, useCollectScope), collections, async rules, server errors, $self.
    • regle-schemas — schema-based validation (Zod, Valibot, ArkType) when a form uses a schema.
    • regle-typescript — inferRules, typing rules and props (RegleRoot, InferRegleRoot, SuperCompatibleRegleRoot).
  3. Docs / LLM-friendly references: https://reglejs.dev/introduction/migrate-from-vuelidate, https://reglejs.dev/llms.txt (glossary), https://reglejs.dev/llms-full.txt (full docs).

Global rules

  • $autoDirty is true by default in Regle — do not set it, and remove manual $touch() calls.
  • Keep the variable name when renaming the composable result: a Vuelidate v$ (or any other name) becomes r$ with the same identifier.
  • Bind form values to the *.$value properties from Regle.
  • Do not use r$.$fields.xxx; access fields directly as r$.xxx.
  • Before writing a custom rule, check for an equivalent built-in rule first.
  • If a specific case is unclear, ask the user or leave it unchanged rather than guessing.

Workflow

Copy this checklist and track progress:

- [ ] 1. Identify the Vuelidate form
- [ ] 2. Replace the imports
- [ ] 3. Replace the state
- [ ] 4. Replace the validation rules
- [ ] 5. Replace the validation properties
- [ ] 6. Replace binding events
- [ ] 7. Replace nested-component validation (scoped)
- [ ] 8. Inspect form propagation (parent <-> child)
- [ ] 9. Self-review and run typecheck + lint

Follow the detailed step-by-step instructions in migration-steps.

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.