Skills and the Claude Code plugin

• larecipe-write-docs reads the code first, searches the existing docs, sets sources:, prefers live references to pasted values, adds the page to the navigation and runs larecipe:validate. It also holds the onboarding workflow and its audience presets.
• larecipe-update-docs runs larecipe:affected, changes only what the code change made wrong, keeps every unrelated sentence, validates, and summarizes the docs change in one line. It also carries the translation workflow.
• larecipe-audit-docs looks for drifted pages, pages without sources:, weak descriptions, undocumented routes, commands, models and events, and broken samples. It sorts its findings as P1 (wrong or unsafe), P2 (missing) and P3 (weak), and fixes only what you ask.
• larecipe-upgrade-v2 works through custom Vue components, theme CSS, Blade inside Markdown and everything the upgrade report flags as manual. See Upgrade from v2.

Each SKILL.md uses only the portable Agent Skills keys: name, description, and at most license, compatibility, metadata and allowed-tools. No agent-specific keys, so every agent reads them the same way. This is larecipe-write-docs:

---
name: larecipe-write-docs
description: Write new LaRecipe docs pages from this app's code. Use when asked to document a feature, an API, an artisan command or part of the codebase, to add a page or section to the docs, or to run LaRecipe onboarding (starter docs for product users, API consumers, package users or an internal team).
license: MIT
compatibility: A Laravel app with larecipe/larecipe installed, so php artisan larecipe:* works. The larecipe MCP server is recommended and required for database doc sets.
metadata:
  author: larecipe
  version: "3.0"
---

Each SKILL.md stays under 500 lines. The details live in a references/ folder the agent opens only when it needs them.

A skill that describes a component or a key that does not exist teaches an agent to write broken pages. So the references that describe LaRecipe's dialect are generated from code by larecipe:agents, not written by hand:

Your own components appear in the catalog marked "(defined by this app)", so an agent writing your docs knows they exist and what their props are. Each generated file starts with a line saying it was generated by php artisan larecipe:agents and should not be edited.

The other references are written by hand and ship as they are: writing-style.md, live-references.md and database-sets.md (kept identical across the skills that carry them), the onboarding presets in larecipe-write-docs, the translation workflow in larecipe-update-docs, and the v2 mapping in larecipe-upgrade-v2.

When laravel/boost is installed, Boost distributes skills for the whole app, and LaRecipe writes no copies of its own. The skills ship from the package's resources/boost/skills/ folder: run php artisan boost:install (or boost:update) and select larecipe/larecipe, and Boost copies them into each agent's folder.

larecipe:agents still matters with Boost. It finds the copies Boost wrote (in .claude/skills, .agents/skills, .github/skills, .cursor/skills and the other folders Boost uses) and regenerates their references, so your own components show up there too. See agent instructions.

The plugin bundles:

• the four skills, from resources/boost/skills/;
• the pre-push and SessionStart hooks, from claude-plugin/hooks.json;
• a /larecipe:onboard command, from claude-plugin/commands/onboard.md, which runs the onboarding workflow of larecipe-write-docs for the audiences you name (product, api, package, internal);
• the local larecipe MCP server.

To have every teammate's Claude Code offer it, register the marketplace and enable the plugin in the project's .claude/settings.json:

{
  "extraKnownMarketplaces": {
    "larecipe": {
      "source": { "source": "github", "repo": "saleem-hadad/larecipe" }
    }
  },
  "enabledPlugins": {
    "larecipe@larecipe": true
  }
}

The plugin's hooks run the plugin's own copy of larecipe-hook, which then runs php artisan larecipe:hook in your app. The plugin is installed for you, not for one project, so the hook does nothing in a project without LaRecipe: it looks for the nearest Laravel app, stops at the git repository's root, and acts only when that app has larecipe/larecipe installed or required. Elsewhere it lets every command through.

Three things to know before you choose the plugin over the installer's files:

• The installer's files come first. The plugin starts the MCP server with php ${CLAUDE_PROJECT_DIR}/artisan larecipe:mcp, a route that is not yet verified end to end. The .mcp.json that larecipe:install writes is the recommended way to connect the server.
• Its references come from the package, not from your app. The plugin's skills never list your own components. Install the skills into the repository as well when you have custom components.
• One set of hooks is enough. With the plugin's hooks on, install with larecipe:install --no-hooks so the check does not run twice on every push.