Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Agents
pepperfm/ai-guidelines
claude-code
cursor
guidelines
boost
skills
cli
installer
presets
verification

pepperfm/ai-guidelines is the shared source of AI guidance used by downstream Laravel projects. Treat guideline/skill edits as product changes: stale or overly broad instructions are multiplied across every consumer.

Install
php artisan boost:add-skill pepperfm/ai-guidelines

Save this content to: AGENTS.md

# Repository Guidelines

## Purpose

`pepperfm/ai-guidelines` is the shared source of AI guidance used by downstream Laravel projects. Treat guideline/skill edits as product changes: stale or overly broad instructions are multiplied across every consumer.

## Architecture

```text
bin/                          # Composer CLI entrypoint
src/Cli/                      # CLI, config, installer, presets
resources/guidelines/         # authored always-on guideline sources
resources/boost/guidelines/   # generated Boost entrypoint only
resources/boost/skills/       # modular on-demand skills
resources/boost/output-styles/# output styles
scripts/                      # build helpers
```

### Source vs generated files

- Edit `resources/guidelines/**/*.md`.
- Do **not** edit `resources/boost/guidelines/core.blade.php` by hand.
- Rebuild it with `php scripts/build-boost-guidelines.php`.
- Keep authored `.md` files out of `resources/boost/guidelines/`; Boost scans that directory and would duplicate context.

## Guidance design

- Always-on guidelines contain only durable invariants.
- Detailed PHP/Laravel conventions belong in `laravel-php-style`.
- Command/test workflows belong in `laravel-sail-and-tests`.
- Fast-moving library/component APIs belong in MCP or version-aware official docs.
- Do not add a skill just to mirror external documentation.
- Project-specific file paths/classes do not belong in this shared package unless they describe this repository itself.
- If a guideline mentions an API, prefer rules that tell the agent how to determine the installed version instead of hard-coding a current major.

Nuxt UI skills are intentionally not shipped. Keep only minimal integration invariants in the `nuxt-ui` preset and rely on current MCP/docs for component API.

## Coding style

- PHP 8.3+, `declare(strict_types=1);`.
- PSR-12 formatting, 4-space indentation, one class per file.
- CLI option names use kebab-case.
- Prefer small explicit changes over adding abstraction to the installer.

## Verification

For PHP changes:

```bash
php -l src/Cli/Installer.php
php -l src/Cli/Skills.php
php -l scripts/build-boost-guidelines.php
```

For guideline changes:

```bash
php scripts/build-boost-guidelines.php
php scripts/build-boost-guidelines.php --check
```

For CLI behavior:

```bash
php bin/pfm-guidelines list
php bin/pfm-guidelines sync --dry-run --no-interaction --presets=laravel
```

The repository currently has no automated test suite. Do not claim validation that was not actually run.

## Pull requests

- Keep commit messages short and imperative.
- Explain downstream behavior changes in the PR body.
- Update `README.md` whenever CLI/preset/package behavior changes.

Repository Guidelines

Purpose

pepperfm/ai-guidelines is the shared source of AI guidance used by downstream Laravel projects. Treat guideline/skill edits as product changes: stale or overly broad instructions are multiplied across every consumer.

Architecture

bin/                          # Composer CLI entrypoint
src/Cli/                      # CLI, config, installer, presets
resources/guidelines/         # authored always-on guideline sources
resources/boost/guidelines/   # generated Boost entrypoint only
resources/boost/skills/       # modular on-demand skills
resources/boost/output-styles/# output styles
scripts/                      # build helpers

Source vs generated files

  • Edit resources/guidelines/**/*.md.
  • Do not edit resources/boost/guidelines/core.blade.php by hand.
  • Rebuild it with php scripts/build-boost-guidelines.php.
  • Keep authored .md files out of resources/boost/guidelines/; Boost scans that directory and would duplicate context.

Guidance design

  • Always-on guidelines contain only durable invariants.
  • Detailed PHP/Laravel conventions belong in laravel-php-style.
  • Command/test workflows belong in laravel-sail-and-tests.
  • Fast-moving library/component APIs belong in MCP or version-aware official docs.
  • Do not add a skill just to mirror external documentation.
  • Project-specific file paths/classes do not belong in this shared package unless they describe this repository itself.
  • If a guideline mentions an API, prefer rules that tell the agent how to determine the installed version instead of hard-coding a current major.

Nuxt UI skills are intentionally not shipped. Keep only minimal integration invariants in the nuxt-ui preset and rely on current MCP/docs for component API.

Coding style

  • PHP 8.3+, declare(strict_types=1);.
  • PSR-12 formatting, 4-space indentation, one class per file.
  • CLI option names use kebab-case.
  • Prefer small explicit changes over adding abstraction to the installer.

Verification

For PHP changes:

php -l src/Cli/Installer.php
php -l src/Cli/Skills.php
php -l scripts/build-boost-guidelines.php

For guideline changes:

php scripts/build-boost-guidelines.php
php scripts/build-boost-guidelines.php --check

For CLI behavior:

php bin/pfm-guidelines list
php bin/pfm-guidelines sync --dry-run --no-interaction --presets=laravel

The repository currently has no automated test suite. Do not claim validation that was not actually run.

Pull requests

  • Keep commit messages short and imperative.
  • Explain downstream behavior changes in the PR body.
  • Update README.md whenever CLI/preset/package behavior changes.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
elsayed85/laravel-api-exceptions
ouhssini/laravel-demo-mode
daworks/ncloud-outbound-mailer-driver
gp247/cms
ignibyte/aic-gates
nexa-merchant/blog
novasa/laravel-language-center
opencage/geocode
adolfoholzer/parameters
livenetworks/ln-starter
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
cgv/localized-resource