New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Laravel Development Workflow

by sickn33 in sickn33/agentic-awesome-skills

Build and fix existing Laravel applications through root-cause diagnosis, repository-native implementation, regression coverage, and risk-based verification.

MITAuto-check passedBackend & APIs

Install Laravel Development Workflow

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill laravel-development-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills laravel-development-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/laravel-development-workflow .claude/skills/laravel-development-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
laravel-development-workflow
GitHub stars
47k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
710 words
Files
1
Skills in repo
1,493
Repo updated
First seen
Licence
MIT

At a glance

Build and fix existing Laravel applications through root-cause diagnosis, repository-native implementation, regression coverage, and risk-based verification.

  • Works in 5 steps: Reproduce the failure through the… → Trace the data and control flow to the… → Add or update a regression test that… → …
  • Tasks that involve Backend development
  • SKILL.md covers When to Use, Establish the Contract, Fix Bugs at the Cause and Build Features in the Existing…, plus 4 more sections
  • Calls php

What it does

Laravel Development Workflow is an agent skill from sickn33/agentic-awesome-skills. Build and fix existing Laravel applications through root-cause diagnosis, repository-native implementation, regression coverage, and risk-based verification.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Backend development and Root cause analysis. It works with Laravel. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Backend development
  • Tasks that involve Root cause analysis

Example prompts

  • “/laravel-development-workflow”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Reproduce the failure through the narrowest reliable path.
  2. Trace the data and control flow to the actionable root cause.
  3. Add or update a regression test that fails for that cause when practical.
  4. Implement the smallest fix that restores the intended invariant.
  5. Demonstrate that the regression test passes and that nearby behavior still works.

What it can do on your machine

Read from SKILL.md and the folder at commit 680176d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • php

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Laravel Development Workflow loads about 1.4k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 710 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 680176d, republished under its MIT licence (© sickn33). 710 words, ~1,449 tokens.

Download SKILL.mdSave it as .claude/skills/laravel-development-workflow/SKILL.md (or your agent's skills folder).
name
laravel-development-workflow
description
Build and fix existing Laravel applications through root-cause diagnosis, repository-native implementation, regression coverage, and risk-based verification.
category
development
risk
critical
source
community
source_repo
Junaid-PK/laravel-development-workflow
source_type
community
date_added
2026-09-02
author
Junaid-PK
tags
laravel, php, debugging, testing, development
tools
claude, codex, cursor, gemini
license
MIT

Laravel Development Workflow

Make the requested Laravel behavior correct, maintainable within the existing application, and supported by evidence that matches the change's risk.

When to Use

  • Use when implementing a feature in an existing Laravel application.
  • Use when diagnosing and fixing a Laravel bug at its actionable root cause.
  • Use when a Laravel change needs regression coverage and proportionate verification.
  • Use when the project already has architectural or testing conventions that must be preserved.

Establish the Contract

Before editing:

  • Read the repository instructions and inspect the relevant routes, models, controllers, actions or services, requests, policies, jobs, events, tests, and schema.
  • Trace the current behavior far enough to identify the actual change boundary and existing conventions.
  • Turn the request into a compact set of scenarios, important edge cases, and verifiable acceptance criteria. Keep this analysis in the working notes unless the user requests a separate artifact.
  • Identify authorization, validation, transaction, queue, cache, and concurrency concerns only where they can affect this behavior.

Scale the analysis to the task. A focused validation fix does not need the same ceremony as a new multi-role workflow.

Fix Bugs at the Cause

For a bug:

  1. Reproduce the failure through the narrowest reliable path.
  2. Trace the data and control flow to the actionable root cause.
  3. Add or update a regression test that fails for that cause when practical.
  4. Implement the smallest fix that restores the intended invariant.
  5. Demonstrate that the regression test passes and that nearby behavior still works.

Do not substitute retries, broad exception handling, disabled validation, extra timeouts, or error suppression for a root-cause fix. If the failure cannot be reproduced locally, state what evidence is missing and use the strongest available static or targeted verification.

Build Features in the Existing Shape

  • Reuse the application's established patterns and naming.
  • Keep business rules in the layer where this codebase already places comparable rules.
  • Use Eloquent relationships, form requests, policies, actions, services, events, or jobs when they improve this change or match local conventions—not as mandatory ceremony.
  • Treat authorization and validation as explicit behavior at the system boundary.
  • Preserve backwards compatibility unless the request requires a breaking change.
  • Keep migrations reversible and safe for the application's supported database engines.

Create factories, seeders, fixtures, or a disposable command only when realistic data is needed for development or durable test coverage. Do not leave one-off scaffolding in the product solely to exercise a small change.

Show full SKILL.md (308 more words)Show less

Verify Proportionately

Discover the project's supported commands from its configuration and documentation. Prefer this order:

  1. Run the narrowest affected test or reproduce the original failure.
  2. Run the relevant feature, unit, or integration test group.
  3. Run static analysis, formatting, and linting configured by the repository.
  4. Run the broader suite when the change's reach or project policy warrants it.

Cover the critical observable behavior, including the happy path and whichever edge cases, validation rules, permissions, database effects, events, notifications, jobs, or API contracts are actually affected. Avoid tests that only mirror implementation details.

Common commands may include:

bash
php artisan test --filter=RelevantTest
vendor/bin/pest --filter=RelevantTest
vendor/bin/phpstan analyse
vendor/bin/pint --dirty

Use the commands the project provides; do not install or configure tools merely because they appear in this example.

Preserve the User's Environment

  • Keep the change inside the requested application behavior and preserve unrelated working-tree changes.
  • Do not run destructive database operations, production commands, deployments, credential changes, or external account actions unless the user or repository instructions explicitly place them in scope.
  • Avoid exposing secrets in commands, logs, test output, or completion evidence.
  • Prefer local, reversible verification and narrowly targeted data changes.

Completion Evidence

Before handing off, verify each acceptance criterion against current behavior. Report:

  • what changed and why it fixes or implements the requested behavior;
  • the scenarios and important edge cases covered;
  • the exact checks run and their results;
  • any check that could not run, with the concrete reason and remaining risk.

Do not claim completion from code inspection alone when executable verification is available.

Limitations

  • This workflow requires an existing Laravel application and adapts to that repository's architecture and tooling; it does not impose a complete project structure.
  • It cannot prove production behavior when the required services, data, credentials, or environment are unavailable, so any unverified risk must be reported explicitly.
  • It does not authorize destructive database work, production changes, deployments, credential changes, or external account actions.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/laravel-development-workflow of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 680176d

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Laravel Development Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Laravel Development Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Laravel Development Workflow this skillsickn33/agentic-awesome-skills47k1 repos~1.4kAutomated safety check: PassMIT
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
Fortify Developmentcoollabsio/coolify63k4 repos~1.9kAutomated safety check: PassMIT
Laravel Best Practicesanonaddy/anonaddy4.9k13 repos~1.2kAutomated safety check: PassMIT
Laravel Actionscoollabsio/coolify63k—~2.4kAutomated safety check: PassApache-2.0
Infer Conventionsanonaddy/anonaddy4.9k5 repos~3.1kAutomated safety check: PassMIT

Similar skills

  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed

  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed

  • Laravel Best Practices

    anonaddy/anonaddy

    Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code.

    4.9k GitHub starsUsed in 13 repos~1.2k tokens
    Backend & APIsAuto-check passed

  • Laravel Actions

    coollabsio/coolify

    Build, refactor, and troubleshoot Laravel Actions using lorisleiva/laravel-actions.

    63k GitHub stars~2.4k tokensUpdated today
    Backend & APIsAuto-check passed

  • Infer Conventions

    anonaddy/anonaddy

    A skill your agent uses to analyze how a Laravel application is actually written and record its conventions as shared rules.

    4.9k GitHub starsUsed in 5 repos~3.1k tokens
    Backend & APIsAuto-check passed

  • Geoflow

    yaojingang/GEOFlow

    Operate/develop GEOFlow CLI/Laravel/admin/API, topics/专题 and topic tasks, theme libraries/replication, sites/leads/Agent, channel sync and legacy yao-geoflow-cli/design/template migration.

    3.8k GitHub stars~722 tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,493 skills in this repo

  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed

  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed

  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Laravel Development Workflow

What does Laravel Development Workflow do?

Build and fix existing Laravel applications through root-cause diagnosis, repository-native implementation, regression coverage, and risk-based verification. Laravel Development Workflow is an agent skill from sickn33/agentic-awesome-skills. Build and fix existing Laravel applications through root-cause diagnosis, repository-native implementation, regression coverage, and risk-based verification.

When should I use Laravel Development Workflow?

Laravel Development Workflow fits situations like: tasks that involve Backend development; tasks that involve Root cause analysis.

How do I install Laravel Development Workflow in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill laravel-development-workflow -a claude-code`. Or copy the skill folder (skills/laravel-development-workflow in sickn33/agentic-awesome-skills) into .claude/skills/laravel-development-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Laravel Development Workflow in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill laravel-development-workflow -a codex`. Or copy the skill folder (skills/laravel-development-workflow in sickn33/agentic-awesome-skills) into .agents/skills/laravel-development-workflow in your project. Codex loads it when a task matches its description.

Can I use Laravel Development Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill laravel-development-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/laravel-development-workflow, .gemini/skills/laravel-development-workflow, .github/skills/laravel-development-workflow and .opencode/skills/laravel-development-workflow in your project.

What does Laravel Development Workflow need to run?

Going by SKILL.md and its folder, Laravel Development Workflow needs the command-line tools its instructions call (php).

Does Laravel Development Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Laravel Development Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Laravel Development Workflow use?

Laravel Development Workflow is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Laravel Development Workflow use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Laravel Development Workflow?

Skills that share tags, products or a category with Laravel Development Workflow: Configuring Horizon (coollabsio/coolify, 63k stars), Fortify Development (coollabsio/coolify, 63k stars), Laravel Best Practices (anonaddy/anonaddy, 4.9k stars) and Laravel Actions (coollabsio/coolify, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Laravel Development Workflow?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,379 GitHub stars. The repository holds 1,493 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.