leeovery
- 68 skills
- 0 followers
- 8 hours ago last updated
- ▌ Laravel Dtos · leeovery bundleData Transfer Objects using Spatie Laravel Data. Use when creating or modifying DTOs, data objects, formatters, transformers, or structured data handling.
- ▌ Laravel Quality · leeovery bundleCode quality tooling with PHPStan, Pint, and strict types. Use when configuring or running static analysis, code style, or linting.
- ▌ Laravel Routing · leeovery bundleRoute configuration, route model binding, and authorization. Use when defining routes, configuring model binding, or setting up route-level authorization.
- ▌ Laravel Policies · leeoveryAuthorization policies for resource access control. Use when creating or modifying policies, permissions, or ability checks.
- ▌ Laravel Validation · leeovery bundleForm request validation and comprehensive validation testing. Use when creating or modifying form requests, validation rules, or validation tests.
- ▌ Laravel Value Objects · leeovery bundleImmutable value objects for domain values. Use when creating or modifying value objects like money, coordinates, or other domain primitives.
- ▌ Laravel Query Builders · leeoveryCustom query builders for type-safe, composable database queries. Use when creating or modifying query builders, query scopes, or complex database queries.
- ▌ Nuxt Forms · leeovery bundleForm handling with XForm component and useFormBuilder. Use when creating forms, handling validation errors, managing form state, or building form-based slideovers and modals.
- ▌ Nuxt Pages · leeovery bundleFile-based routing with page patterns for lists, details, and navigation. Use when creating pages, defining page meta (permissions, layouts), implementing list/detail patterns, or setting up breadcrumbs and headers.
- ▌ Nuxt Config · leeovery bundleNuxt and app configuration files. Use when configuring nuxt.config.ts, app.config.ts, environment variables, runtime config, or understanding how configuration flows through the application.
- ▌ Nuxt Layers · leeovery bundleWorking with Nuxt layers (base, nuxt-ui, x-ui) that provide shared functionality. Use when understanding layer architecture, importing from layers, extending layer functionality, or creating new layers.
- ▌ Nuxt Testing · leeovery bundleTesting strategy across unit, component, composable, API integration, and E2E layers. Use when adding tests, choosing the right tier for a piece of behaviour, setting up vitest or Playwright, or designing test seams for Nitro-side effects.
- ▌ Laravel Jobs · leeovery bundleBackground jobs and event listeners for async processing. Use when creating or modifying jobs, queues, listeners, or event-driven workflows.
- ▌ Nuxt Components · leeovery bundleVue component patterns with Composition API and script setup. Use when creating components, understanding script setup order convention, organizing component directories, or implementing component patterns like slideovers, modals, and tables.
- ▌ Laravel Enums · leeoveryBacked enums with labels and business logic. Use when defining or modifying enums, status values, or fixed option sets.
- ▌ Nuxt Composables · leeovery bundleCreating custom Vue composables with proper patterns. Use when building reusable stateful logic, shared state management, or encapsulating feature-specific behavior.
- ▌ Nuxt Server Data · leeovery bundleServer-side data layer with Drizzle ORM + Cloudflare D1 + NuxtHub. Use when designing schema, generating and applying migrations, querying from Nitro routes, sharing types between client and server, or testing DB writes.
- ▌ Laravel Models · leeovery bundleEloquent model patterns and database layer. Use when creating or modifying models, relationships, casts, or observers.
- ▌ Nuxt Architecture · leeovery bundleFoundational architecture for Nuxt 4 + Vue 3 + Nuxt UI applications. Use when starting new projects, understanding project structure, or making architectural decisions about directory organization, technology choices, and pattern selection.
- ▌ Laravel Actions · leeoveryAction-oriented architecture for Laravel — invokable classes containing domain logic. Use when creating or modifying actions, business logic, or domain operations.
- ▌ Laravel Testing · leeovery bundleComprehensive testing patterns with Pest. Use when writing or modifying tests, mocking, factories, or test patterns.
- ▌ Nuxt Design Tokens · leeovery bundleDesign tokens and theming via Tailwind 4 `@theme static` and Nuxt UI semantic classes. Use when registering custom type scales, motion curves, brand palettes, or contextual CSS overrides; also when building dark-mode-correct surfaces and View Transitions.
- ▌ Laravel Packages · leeovery bundlePackage development and extraction of reusable code. Use when creating, extracting, or modifying composer packages.
- ▌ Laravel Services · leeoveryService layer for external API integration using manager pattern and Saloon. Use when integrating external APIs or third-party services.
- ▌ Laravel Providers · leeovery bundleService providers, bootstrapping, and application configuration. Use when modifying service providers, booters, bootstrap logic, or app-level configuration.
- ▌ Laravel Exceptions · leeovery bundleCustom exceptions with static factories and HTTP responses. Use when creating or modifying exceptions or error handling.
- ▌ Laravel Controllers · leeovery bundleThin HTTP-layer controllers with zero domain logic. Use when creating or modifying controllers, handling HTTP concerns, or structuring web vs API layers.
- ▌ Laravel Architecture · leeovery bundleHigh-level architecture decisions, patterns, and project structure. Use when deciding which pattern to use, organizing code, or making structural decisions.
- ▌ Laravel Multi Tenancy · leeovery bundleMulti-tenant application architecture patterns. Use when working with tenant isolation, tenant scoping, or multi-tenant systems.
- ▌ Laravel State Machines · leeovery bundleState machines using Spatie Model States for complex state transitions. Use when implementing or modifying state machines, transitions, or transition validation.
- ▌ Workflow Start · leeovery bundleUnified workflow entry point. Discovers state, shows all active work, and routes to start or continue skills.
- ▌
- ▌
- ▌ Workflow Migrate · leeovery bundleMigrations run via `engine boot` (`node .claude/skills/workflow-engine/scripts/engine.cjs boot`, called in Step 0 of `workflow-start`) — this skill is never invoked. The directory remains the home of the migration machinery:
- ▌
- ▌
- ▌ Workflow Discovery · leeovery bundleThe universal first phase. Shape the work the user is bringing — confirm what kind of work it is, sketch its outline — then persist it and route into the pipeline.
- ▌
- ▌ Workflow Review Entry · leeovery bundleAct as **precise intake coordinator**. Follow each step literally without interpretation. Do not engage with the subject matter — your role is preparation, not processing.
- ▌ Workflow Continue Epic · leeovery bundleContinue an in-progress epic. Shows full phase-by-phase state and routes to the appropriate phase skill.
- ▌ Workflow Scoping Entry · leeovery bundleAct as **precise intake coordinator**. Follow each step literally without interpretation. Do not engage with the subject matter — your role is preparation, not processing.
- ▌ Workflow Planning Entry · leeovery bundleAct as **precise intake coordinator**. Follow each step literally without interpretation. Do not engage with the subject matter — your role is preparation, not processing.
- ▌ Workflow Research Entry · leeovery bundleAct as **precise intake coordinator**. Follow each step literally without interpretation. Do not engage with the subject matter — your role is preparation, not processing.
- ▌
- ▌ Workflow Continue Bugfix · leeovery bundleContinue an in-progress bugfix. Determines current phase and routes to the appropriate phase skill.
- ▌
- ▌ Workflow Continue Feature · leeovery bundleContinue an in-progress feature. Determines current phase and routes to the appropriate phase skill.
- ▌ Workflow Discussion Entry · leeovery bundleAct as **precise intake coordinator**. Follow each step literally without interpretation. Do not engage with the subject matter — your role is preparation, not processing.
- ▌ Workflow Experiment Entry · leeovery bundleAct as **precise intake coordinator**. Follow each step literally without interpretation. Do not engage with the subject matter — your role is preparation, not processing.
- ▌
- ▌
- ▌ Workflow Continue Quickfix · leeovery bundleContinue an in-progress quick-fix. Determines current phase and routes to the appropriate phase skill.
- ▌
- ▌
- ▌ Workflow Investigation Entry · leeovery bundleAct as **precise intake coordinator**. Follow each step literally without interpretation. Do not engage with the subject matter — your role is preparation, not processing.
- ▌ Workflow Specification Entry · leeovery bundleAct as **precise intake coordinator**. Follow each step literally without interpretation. Do not engage with the subject matter — your role is preparation, not processing.
- ▌ Workflow Implementation Entry · leeovery bundleAct as **precise intake coordinator**. Follow each step literally without interpretation. Do not engage with the subject matter — your role is preparation, not processing.
- ▌
- ▌ Workflow Legacy Research Split · leeovery bundleAct as **curator + interviewer**. Walk the user through decomposing broad research files — each holding multiple themes — into topic-scoped files plus matching discovery-map items.
- ▌
- ▌ Workflow Continue Cross Cutting · leeovery bundleContinue an in-progress cross-cutting concern. Determines current phase and routes to the appropriate phase skill.
- ▌
- ▌ Workflow Log Bug · leeoveryCapture a bug report as a markdown file in the workflow inbox. Use when the user wants to log, note, or save a bug for later.
- ▌ Workflow Log Idea · leeoveryCapture an idea as a markdown file in the workflow inbox. Use when the user wants to log, note, or save an idea for later.
- ▌ Prose Test · leeoveryRun prose-logic test cases — one orchestrator agent per case walks the real prose against a materialised world and asserts the result, reporting back a verdict. Scope by diff (default), case ids, or --all.
- ▌ Review Work · leeovery bundleAdversarially review work just built on this project — strict adherence to CLAUDE.md and CONVENTIONS.md, broken logic, dead ends, invalid paths, regressions, and historical artefacts left in the prose. Dispatches finder agents, verifies what they return, lands fixes as new stack layers or into the PR still under review. Use whenever the user asks to review the work, do a review pass, check for regressions or convention adherence, or dispatch review sub-agents.
- ▌ Workflow Log Quickfix · leeoveryCapture a quick-fix as a markdown file in the workflow inbox. Use when the user wants to log a trivially scoped mechanical change for later.
- ▌ Create Output Format · leeovery bundleScaffold a new planning output format adapter. Creates a format directory with all required files implementing the output format contract.