laravel-11-12-app-guidelines
Guidelines and workflow for working on Laravel 11 or Laravel 12 applications across common stacks (API-only or full-stack), including optional Docker Compose/Sail, Inertia + React, Livewire, Vue, Blade, Tailwind v4, Fortify, Wayfinder, PHPUnit, Pint, and Laravel Boost MCP tools. Use when implementing features, fixing bugs, or making UI/backend changes while following project-specific instructions (AGENTS.md, docs/).
What this skill does
# Laravel 11/12 App Guidelines ## Overview Apply a consistent workflow for Laravel 11/12 apps with optional frontend stacks, Dockerized commands, and Laravel Boost tooling. ## Quick Start - Read repository instructions first: `AGENTS.md`. If `docs/` exists, read `docs/README.md` and relevant module docs before decisions. - Detect the stack and command locations; do not guess. - Use Laravel Boost `search-docs` for Laravel ecosystem guidance; use Context7 only if Boost docs are unavailable. - Follow repo conventions for naming, UI language, docs-first policies, and existing component patterns. ## Stack Detection - Check `composer.json`, `package.json`, `docker-compose.*`, and `config/*` to confirm: - Docker Compose/Sail vs host commands - API-only vs full-stack - Frontend framework (Inertia/React, Livewire, Vue, Blade) - Auth (Fortify, Sanctum, Passport, custom) ## Laravel 11/12 Core Conventions - Use the Laravel 11/12 structure: configure middleware, exceptions, and routes in `bootstrap/app.php`; service providers in `bootstrap/providers.php`; console configuration in `routes/console.php`. - Use Eloquent models and relationships first; avoid raw queries and `DB::` unless truly necessary. - Create Form Request classes for validation instead of inline validation. - Prefer named routes and `route()` for URL generation. - When altering columns, include all existing attributes in the migration to avoid dropping them. - Ask before destructive database operations (e.g., reset/rollback/fresh). ## API-Only Mode - Use `routes/api.php`; avoid Inertia and frontend assumptions. - Prefer API Resources and versioning if the repo already uses them. - Follow the repo's auth stack (Sanctum/Passport/custom) and response format conventions. - Do not require Vite/Tailwind/NPM unless the repo already includes them. ## Inertia + React + Wayfinder (if present) - Use `Inertia::render()` for server-side routing; place pages under `resources/js/Pages` unless the repo says otherwise. - Use `<Form>` or `useForm` for Inertia forms; add skeleton/empty states for deferred props. - Use `<Link>` or `router.visit()` for navigation. - Use Wayfinder named imports for tree-shaking; avoid default imports; regenerate routes after changes if required. ## Livewire / Vue / Blade (if present) - Follow existing component patterns and conventions; do not mix frameworks unless the repo already does. - Keep UI strings in the repo's expected language. ## Tailwind CSS v4 (if present) - Use `@import "tailwindcss";` and `@theme` for tokens. - Avoid deprecated utilities; use replacements (e.g., `shrink-*`, `grow-*`, `text-ellipsis`). - Use `gap-*` for spacing between items; follow existing dark mode conventions if present. ## Testing and Formatting - Use PHPUnit; generate tests with `php artisan make:test --phpunit` and prefer feature tests. - Run the minimal relevant tests (`php artisan test <file>` or `--filter=`). - Run `vendor/bin/pint --dirty` before finalizing code changes. - After minimal tests pass, offer to run the full test suite. ## Laravel Boost MCP Tools (when available) - `search-docs` before changing behavior or using framework features. - `list-artisan-commands` to confirm Artisan options. - `list-routes` to inspect routing changes. - `tinker` for PHP debugging and `database-query` for read-only DB checks. - `browser-logs` to inspect frontend errors. - `get-absolute-url` for sharing project URLs. - See `references/boost-tools.md` for query patterns and tool usage tips. ## Output Expectations - Preserve existing architecture, structure, and dependencies unless the user explicitly requests changes. - Reuse existing components and follow local patterns. - Ask concise clarifying questions when repo guidance is missing or ambiguous.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.