agentleFS
nowo-technowo-tech/GenerativeSeoKitBundle/.github/copilot-instructions.md

GenerativeSeoKitBundle

Copilot instructions0 starsChanged 17 days agoMITView on GitHub

Use this when suggesting code, tests, documentation, or CI changes for this repository.

We split this copilot-instructions.md into the rules it gives an agent

9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this when suggesting code, tests, documentation, or CI changes for this repository.

    line 3
  2. Very specific:

    Prefer PHP 8 attributes for configuration and metadata.

    line 9
  3. Very specific:

    Follow PSR-12 and project conventions in .php-cs-fixer.dist.php.

    line 13
  4. Very specific:

    Use strict comparison (===) where appropriate.

    line 14
  5. Very specific:

    Keep changes minimal and consistent with existing patterns in src/ and tests/.

    line 15
  6. Distinctive:

    Only README.md at repository root (no extra root markdown files).

    line 21
  7. Very specific:

    Do not add Co-authored-by: Cursor (or similar) trailers to commits.

    line 22
  8. Distinctive:

    Add or update tests for new behaviour.

    line 26
  9. Very specific:

    Never add AI co-author trailers: no Co-authored-by: Cursor / cursoragent@cursor.com, no Co-Authored-By: Claude … / noreply@anthropic.com …

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions 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
copilot-instructions.md

AI contribution guidelines (Nowo Symfony bundle)

Use this when suggesting code, tests, documentation, or CI changes for this repository.

Scope

  • This is a Symfony bundle published under nowo-tech/generative-seo-kit-bundle on Packagist (GenerativeSeoKitBundle).
  • Respect the PHP and Symfony version ranges declared in composer.json (PHP 8.2+, Symfony 7.4 / 8.x).
  • Prefer PHP 8 attributes for configuration and metadata. Do not introduce doctrine/annotations for new code.

Code

  • Follow PSR-12 and project conventions in .php-cs-fixer.dist.php.
  • Use strict comparison (===) where appropriate.
  • Keep changes minimal and consistent with existing patterns in src/ and tests/.
  • Align with composer cs-check, composer phpstan, and composer test expectations.

Documentation

  • User-facing documentation is English under docs/ per Nowo bundle standards.
  • Only README.md at repository root (no extra root markdown files).
  • Do not add Co-authored-by: Cursor (or similar) trailers to commits.

Tests

  • Add or update tests for new behaviour; keep coverage in line with README and CI.

Commits

  • Never add AI co-author trailers: no Co-authored-by: Cursor / cursoragent@cursor.com, no Co-Authored-By: Claude … / noreply@anthropic.com (REQ-GIT-001).

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.