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
- Distinctive: line 3
Use this when suggesting code, tests, documentation, or CI changes for this repository.
- Very specific: line 9
Prefer PHP 8 attributes for configuration and metadata.
- Very specific: line 13
Follow PSR-12 and project conventions in .php-cs-fixer.dist.php.
- Very specific: line 14
Use strict comparison (===) where appropriate.
- Very specific: line 15
Keep changes minimal and consistent with existing patterns in src/ and tests/.
- Distinctive: line 21
Only README.md at repository root (no extra root markdown files).
- Very specific: line 22
Do not add Co-authored-by: Cursor (or similar) trailers to commits.
- Distinctive: line 26
Add or update tests for new behaviour.
- Very specific: line 30
Never add AI co-author trailers: no Co-authored-by: Cursor / cursoragent@cursor.com, no Co-Authored-By: Claude … / noreply@anthropic.com …
≈ “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.
Files
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-bundleon 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/annotationsfor 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/andtests/. - Align with
composer cs-check,composer phpstan, andcomposer testexpectations.
Documentation
- User-facing documentation is English under
docs/per Nowo bundle standards. - Only
README.mdat 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, noCo-Authored-By: Claude …/noreply@anthropic.com(REQ-GIT-001).
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository15 other files it gives its agents.
- .cursor/rules/00-global.mdcCursor rule
- .cursor/rules/01-git-commits.mdcCursor rule
- .cursor/rules/10-php-symfony-bundle.mdcCursor rule
- .cursor/rules/40-tests-quality.mdcCursor rule
- .cursor/rules/50-docs-and-release.mdcCursor rule
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
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
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.

