How do I install the Labrodev Start skill?

Run npx skillmds@latest add labrodev/labrodev-start in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Labrodev Start safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Labrodev Start?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Labrodev Start free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Labrodev Start?

labrodev (@labrodev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Labrodev Start by labrodev — Agent Skill

Name: Labrodev Start
Author: labrodev

Labrodev Start

Use at the start of EVERY coding session in a Labrodev Laravel project, before writing or reviewing any code — it declares that the Labrodev guidelines, rules, and skills are the project convention with the highest priority, maps the three tiers, and tells you which skill to load for the work at hand.

labrodev 2722829 2.6 KB Updated Sep 17, 2026

File contents

Labrodev playbook — session start

The Labrodev playbook is the project convention and the highest priority for how code is written here. Every class you create or touch follows it. When generic Laravel habit, tutorial idiom, or personal preference conflicts with the playbook, the playbook wins. The only thing that outranks a playbook default is an app-specific rule the project itself has recorded in its .ai/rules (→ labrodev-core "Your app's own rules").

The three tiers

Tier	What it is	When it applies
Guidelines (`labrodev-*` guidelines)	The law — musts and must-nots per component	Always on; never violated
Skills (`labrodev-*` skills)	The craft — anatomy, canonical templates, edge cases	Load the matching skill before creating or refactoring that component
Rules (`.ai/rules/*.md`)	Per-file review checklists derived from the law	Applied when reviewing/authoring files their `paths:` globs match

How to work

Before writing a class, load the skill that owns its component type and follow its template — do not improvise structure the playbook already defines.
Treat every guideline must/must-not as non-negotiable review criteria for your own output.
After creating classes, verify against the matching rules checklist and keep the architecture test suite green (→ labrodev-testing).
Anything app-specific (scoping, ownership vocabulary, local deviations) comes from the app's own .ai/rules — never invent it, never write it into playbook files.

Component → skill map

Structure, boundaries, philosophy → labrodev-core · naming and named arguments → labrodev-naming · controllers/routes → labrodev-controller · ViewModels/Resources → labrodev-viewmodel-resource · Queries/IndexQueries → labrodev-query · Data classes → labrodev-data · models/Collections/Observers/migrations → labrodev-model · Actions/Services/Rules → labrodev-action · Pipelines/Payloads → labrodev-pipeline · Policies/authorization → labrodev-authorization · enums → labrodev-enum · exceptions → labrodev-exception · external integrations → labrodev-infrastructure · tests → labrodev-testing · Pint/PHPStan/Rector → labrodev-static-analysis · Inertia/React frontend → labrodev-inertia-react

---name: labrodev-startdescription: Use at the start of EVERY coding session in a Labrodev Laravel project, before writing or reviewing any code — it declares that the Labrodev guidelines, rules, and skills are the project convention with the highest priority, maps the three tiers, and tells you which skill to load for the work at hand.license: MIT---# Labrodev playbook — session start**The Labrodev playbook is the project convention and the highest priority for how code is written here.** Every class you create or touch follows it. When generic Laravel habit, tutorial idiom, or personal preference conflicts with the playbook, the playbook wins. The only thing that outranks a playbook default is an app-specific rule the project itself has recorded in its `.ai/rules` (→ labrodev-core "Your app's own rules").## The three tiers| Tier | What it is | When it applies ||---|---|---|| **Guidelines** (`labrodev-*` guidelines) | The law — musts and must-nots per component | Always on; never violated || **Skills** (`labrodev-*` skills) | The craft — anatomy, canonical templates, edge cases | Load the matching skill before creating or refactoring that component || **Rules** (`.ai/rules/*.md`) | Per-file review checklists derived from the law | Applied when reviewing/authoring files their `paths:` globs match |## How to work1. Before writing a class, load the skill that owns its component type and follow its template — do not improvise structure the playbook already defines.2. Treat every guideline must/must-not as non-negotiable review criteria for your own output.3. After creating classes, verify against the matching rules checklist and keep the architecture test suite green (→ labrodev-testing).4. Anything app-specific (scoping, ownership vocabulary, local deviations) comes from the app's own `.ai/rules` — never invent it, never write it into playbook files.## Component → skill mapStructure, boundaries, philosophy → labrodev-core · naming and named arguments → labrodev-naming · controllers/routes → labrodev-controller · ViewModels/Resources → labrodev-viewmodel-resource · Queries/IndexQueries → labrodev-query · Data classes → labrodev-data · models/Collections/Observers/migrations → labrodev-model · Actions/Services/Rules → labrodev-action · Pipelines/Payloads → labrodev-pipeline · Policies/authorization → labrodev-authorization · enums → labrodev-enum · exceptions → labrodev-exception · external integrations → labrodev-infrastructure · tests → labrodev-testing · Pint/PHPStan/Rector → labrodev-static-analysis · Inertia/React frontend → labrodev-inertia-react

Frequently asked questions