agentleFS
Sign inStart free
kkxdevkkxdev/claude-skills/skills/laravel-knowledge/templates/CLAUDE.md

claude-skills / templates

CLAUDE.md1 starsChanged 13 days agoMITView on GitHub

- Framework: Laravel {{LARAVEL_LOCKED}} ({{LARAVEL_CONSTRAINT}}; PHP {{PHP}}) {{STACK_BULLETS}} Tests: {{TEST_COMMAND}} (see Testing warning first). Always read .ai/domain/known-gotchas.md first before {{GOTCHA_TRIGGERS_SHORT}}. {{TOP_RISKS}} Where this file and .ai/ disagree, .ai/ was cross-checked more recently; code on disk beats both. file:line citations are a snapshot — re-verify before relying on one for a risky change. TODO: Domain owner input required = unknown. Each agent prompt says which .ai/domain/ files to read for its role.

  • Reads credentials

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always read .ai/domain/known-gotchas.md first: before {{GOTCHA_TRIGGERS_SHORT}}.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

{{PROJECT}} — Claude Code Guide

Project Overview

{{ONE_PARAGRAPH}}

  • Framework: Laravel {{LARAVEL_LOCKED}} ({{LARAVEL_CONSTRAINT}}; PHP {{PHP}}) {{STACK_BULLETS}}

Repository Layout

Standard Laravel layout. Non-obvious bits only (dead route files, symlinked dirs, disabled observers, where schema lives, counts): {{LAYOUT_BULLETS}}

Technology Stack

One short paragraph + queue/auth/auditing facts. Flag installed-but-unused packages ("verify before rely").

Key Commands

{{COMMANDS}}

Tests: {{TEST_COMMAND}} (see Testing warning first).

Architecture Patterns

Data Flow (numbered, request → controller → ... → queue/search), Multi-datastore strategy, Models, Background Jobs, Cron/Scheduler.

Environment & Configuration

.env.example → .env, custom config files, per-environment connections.

Testing

Framework, suites, test env, warnings (e.g. no isolated database).

Coding Conventions

Controllers/services/validation/views/jobs/models/observers conventions, evidenced only.

Domain Knowledge Base (.ai/)

.ai/ holds the code-verified knowledge base (index: .ai/AGENTS.md, hard facts: .ai/project.yaml). Not auto-loaded; before work on a subsystem read the matching file:

Touching…Read
{{DOMAIN_TABLE}}

Always read .ai/domain/known-gotchas.md first before {{GOTCHA_TRIGGERS_SHORT}}. {{TOP_RISKS}}

Where this file and .ai/ disagree, .ai/ was cross-checked more recently; code on disk beats both. file:line citations are a snapshot — re-verify before relying on one for a risky change. TODO: Domain owner input required = unknown.

Agents

Four Claude Code sub-agents in .claude/agents/. Invoke by name (e.g. "use Vidura to review this diff"):

AgentFilePurpose
Arjuna.claude/agents/dev.mdFeature development, bug fixes, new endpoints
Vidura.claude/agents/review.mdCode review, PR analysis, security checks
Yudhishthira.claude/agents/qa.mdTest writing, coverage, QA
Krishna.claude/agents/architect.mdSystem design, architectural decisions, refactor strategy

Each agent prompt says which .ai/domain/ files to read for its role.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free