agentleFS
build-dezineerbuild-dezineer/skills-nuxt4-tw-webapp/skills/auth/SKILL.md

auth

Skill0 starsChanged 44 days agoApache-2.0View on GitHub

Authentication pages covering login, register, forgot/reset password, OTP/MFA and verify-email in four layouts: minimal card, split-screen, full-bleed background and multi-step wizard. Includes password strength, show/hide toggles, field errors and global error banners. Use when building auth or onboarding flows.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ci-cd, error-handling and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JohnJBorenSkill

    ci-cd

    CI/CD pipeline design, GitHub Actions, testing automation, and deployment strategies

    Also in 4 projects that use this

  • MicrosoftSkill

    error-handling

    统一错误处理系统。在添加 API 端点、修改错误处理、添加前端 API 调用、编写错误相关测试时使用。

    Also in 5 projects that use this

  • diego-tobalinaSkill

    logging

    Logging best practices for Java (SLF4J/Logback) and Node.js (Winston/Pino). Use for structured logging, log levels, and avoiding sensitive data exposure.

    Also in 3 projects that use this

  • SentrySkill

    github-issues

    Create, update, comment on, label, and inspect GitHub issues with concise, evidence-backed content. Use when users ask to open, edit, view, close, reopen, or triage GitHub issues — including tracking bugs, features, or tasks. Prefer this skill over generic repository tools for issue operations; do not use for pull requests, branches, pushes, or PR creation order questions.

    Also in 3 projects that use this

  • wrsmith108Skill

    docker

    Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.

    Also in 3 projects that use this

  • SentrySkill

    ui-design

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Read references/fields.md for the shared field patterns every variant uses: inputs, field errors, password show/hide, global error banner, …

    line 33
  2. Very specific:

    Standard auth pages: always use definePageMeta({ layout: 'auth' }).

    line 78
  3. Very specific:

    All icons from lucide-vue-next, validated against lucide-icons.txt

    line 91

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “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

Auth Skill

When to use

Any page handling user authentication: login, register, forgot-password, reset-password, verify-email, OTP/MFA. Read SPEC.md to choose the right layout variant for the product's brand character.

Quick decision

SPEC.md describes...Jump to
"clean", "simple", "functional", any SaaSMinimal card
"marketing", "hero", "brand panel", "premium"Split-screen
"bold", "immersive", "lifestyle", "photography"Full-bleed
"onboarding", "multi-step", "wizard"Multi-step

Read references/fields.md for the shared field patterns every variant uses: inputs, field errors, password show/hide, global error banner, submit button, password strength bar, and OTP inputs.

Four layout variants

VariantChoose when SPEC.md describes…Layout meta
Minimal cardClean SaaS, functional, any general productlayout: 'auth'
Split-screenMarketing-forward product, premium conversion feellayout: false
Full-bleed backgroundBold brand, visual product, lifestyle feellayout: false
Multi-step wizardOnboarding-heavy register, MFA flows, progressive disclosurelayout: 'auth'

The auth layout (layouts/auth.vue) centers its slot content and shows a floating theme toggle. Variants that need full-viewport control use layout: false and reproduce the theme toggle manually.


Auth page types

PageRoutePrimary fieldsSecondary links
Login/loginemail, password (show/hide), remember meForgot password, Register
Register/registername, email, password (strength bar), confirm passwordLogin
Forgot password/forgot-passwordemailBack to login
Reset password/reset-passwordnew password, confirm password—
OTP / MFA/mfa6-digit code (individual inputs)Resend code
Verify email/verify-emailNo form — success illustration + resend button—

Required imports

SymbolSource
AlertCircle, Eye, EyeOff, Loader2, Sun, Moon, CheckCirclelucide-vue-next
ref, computed, onMounted, watchvue
cn~/utils/cn
NuxtLink#components

Validate every icon against app/assets/lucide-icons.txt.


Non-negotiables

  1. Standard auth pages always use definePageMeta({ layout: 'auth' }). Split-screen and Full-bleed use layout: false and manually reproduce the theme toggle
  2. Card surface: bg-card border border-border rounded-xl shadow-sm (Variant 1), bg-card/95 backdrop-blur-xl rounded-2xl shadow-2xl (Variant 3 over image)
  3. Card max-width: max-w-sm (login, forgot, MFA) — max-w-md (register with more fields)
  4. Submit button always full-width (w-full)
  5. Submit button shows Loader2 animate-spin + disabled during loading — no double-submit
  6. Global error banner: bg-destructive/10 text-destructive with AlertCircle — never hardcoded red
  7. Field-level errors displayed BELOW the field — never only as border color
  8. Password fields always have Eye/EyeOff toggle — never plain type="password" without it
  9. Secondary navigation uses <NuxtLink> — never <a href>
  10. OTP inputs: auto-advance on digit entry, auto-backspace to previous on delete
  11. Card entrance animation always present (scoped @keyframes card-in with prefers-reduced-motion guard)
  12. Multi-step uses <Transition name="slide-down" mode="out-in"> for step changes
  13. <form @submit.prevent="handleSubmit"> — never bare button @click without a form wrapper
  14. All icons from lucide-vue-next, validated against lucide-icons.txt
  15. Dark mode state in Variants 2/3: always persist to localStorage, toggle .dark on <html>
  16. SFC block order: <script setup> → <template> → <style scoped>

Colour & polish

  • Focus rings on every field; brand panel on split layouts.

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.