Where this fits

Imagine you're building a Laravel API and need to add email verification, two-factor authentication, and passkey support. You install Fortify, then spend hours wiring up custom response contracts, tweaking redirects, and debugging throttle logic. Your AI agent could do this in minutes—if it actually understood Fortify's internal patterns instead of guessing. The fortify-development skill gives your agent an exact playbook for Laravel's auth backend, activating only when you're working on authentication.

Why agents benefit

• Precise activation – Triggers only on Fortify-related work (login, 2FA, passkeys, profile updates), not on Socialite or Passport, so your agent doesn't waste tokens on irrelevant tasks.
• Deep contextual awareness – Recognizes specific files like app/Actions/Fortify/CreateNewUser and config/fortify.php, letting it suggest edits that match your existing project structure.
• Handles headless scenarios – Understands SPA or API-driven auth, including overriding LoginResponse and customizing login throttling—the tricky parts where most agents just give generic advice.
• Speeds up routine customization – Knows how to modify registration, password reset, and email verification flows without you explaining Laravel's conventions.
• Avoids wrong-package advice – Explicitly excludes Passport and Socialite, preventing the common mistake of mixing OAuth2 or social login into a Fortify-only task.

Practical scenarios

Adding 2FA to a SPA without breaking the frontend

Your agent, guided by the skill, knows exactly which Fortify routes and controllers handle TOTP, QR codes, and recovery codes. It can generate the required Blade or JavaScript stubs, or even expose the right JSON endpoints for your Vue frontend, all while respecting your existing auth guard configuration.

Overriding the default login redirect

You need different redirects for admins and regular users. The skill tells the agent to work with Fortify's LoginResponse contract, so it writes a custom implementation that checks the user's role—no more digging through forgotten docs.

Debugging throttling on a high-traffic auth route

Your login endpoint is getting rate-limited because a misconfigured throttle hit. The agent uses the skill to inspect your config/fortify.php limits and suggests a custom rate limiter, complete with a test case, saving you from trial-and-error.

Add it to your agent workflow

Install the skill with one command:

npx skills add promovaweb/specsfy --skill fortify-development

Then, in your next session, simply describe your task: "Set up email verification and password confirmation for my API's auth endpoints using Fortify." The agent will activate the skill and produce code that matches Laravel's idioms. You can also browse more skills on OpenAgentSkill to see how this one fits into your agent toolkit.

Compare before adopting

Before you commit to this skill, compare it with others that might claim Laravel auth support. Check whether it actually references the correct Fortify files and contracts, look at how recently it was updated (Laravel changes fast), and see if the author maintains other Laravel-specific skills. Also consider whether your team uses a different auth package (like Breeze or Jetstream) - those are not covered here, so weigh the fit.

Why it is worth tracking

This skill has 60 stars and an MIT license, and it's authored by promovaweb under the specsfy project. The real signal is its precise, narrow scope: it targets a single, well-defined framework component and avoids overlap with OAuth or social login. That focus makes it reliable for agents that need to act autonomously on Laravel auth tasks. Track it if you're building agents that handle Laravel backend work—and re-evaluate whenever a new Fortify release lands, to ensure the skill's patterns stay current.