commit
Use this when the changes and scope are finalized and it's time to commit.
Discover DevOps skills, compare source repositories and read the instructions for each workflow.
Use this when the changes and scope are finalized and it's time to commit.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures u...
Use when preparing to implement instructions by reviewing documentation and TODO.md so the actual work starts with a shared plan.
Show detailed info for a specific project. Use when user asks about a particular project's status, history, or details.
Query and list projects in ~/work/. Use when user asks for project overview, status of all projects, or wants to see what projects exist.
database column setup. Use when you need to create or update a database column
Controller role handling. Use when you need to setup a api endpoint with the right permissions and roles
Building database queries with the Options API. Use when you need to query a model by creating a new query or updating an existing one
Code generation for CRUD endpoints
Use to build proper go unit tests for services, models, and controllers
This skill should be used when analyzing development sessions to extract learnings, determining what constitutes valuable knowledge to capture, creating skills from session insights, or evaluating whether patte...
Working with model instances and fields, use when you need to access fields on a model
controller and API setup and basic patterns. Use when you need controller permissions, controller post data, controller params and queries, or setup a new controller or API route
Standards, conventions, and struct tag reference for models. Use when you need to setup a model field or need to know how to access something in a model
How to work effectively with Inertia, always use when developing frontend features
How to effectively test the application, always use when writing tests
Use when implementing any feature or bugfix, before writing implementation code
How to work effectively with Laravel Wayfinder, always use when developing frontend features
How to work effectively with React, always use when developing frontend components
How to work effectively with Laravel, always use when developing Laravel features
Pest framework syntax reference
Laravel Pint syntax reference
How to work effectively with Tailwind CSS, always use when styling frontend features
How to work effectively with shadcn/ui components, always use when adding UI components
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.