Download the PHP package sandermuller/rector-ecosystem-boost without Composer
On this page you can find all versions of the php package sandermuller/rector-ecosystem-boost. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download sandermuller/rector-ecosystem-boost
More information about sandermuller/rector-ecosystem-boost
Files in sandermuller/rector-ecosystem-boost
Package rector-ecosystem-boost
Short Description Agent skills, coding standards, and PR conventions for the rector / symplify / TomasVotruba ecosystem (boost catalog).
License MIT
Homepage https://github.com/sandermuller/rector-ecosystem-boost
Informations about the package rector-ecosystem-boost
rector-ecosystem-boost
Agent skills, coding standards, and PR conventions for the rector / symplify / TomasVotruba ecosystem — and for contributing to repos you don't own. A Composer-distributed boost catalog: pure-Markdown, no runtime code.
What it ships
Skills (loaded on demand):
oss-contribution— the foreign-repo contribution playbook: read the target's rules first, run its gate, draft maintainer-facing prose for a human (never post it as the agent), one PR at a time, scope ambition to trust.rule-authoring— the canonical shape for an ecosystem rule (Rector / PHPStan / symplify): mirror-path namespace,final+ framework base, ctor injection, bail-early, the test + fixture conventions, no value-object tests. Tuned per repo by therule.*conventions.
Guidelines (always loaded):
rector-ecosystem-house-style— the shared rectorphp / symplify / TomasVotruba coding standards (final classes, strict types, ReflectionProvider-not-runtime, no setters, …); php-tagged.pr-contribution— the ecosystem's PR conventions + anti-slop rules (one feature/PR, tests required, lead-with-a-failing-test, no coverage/Docker padding, why-not-what descriptions); php-tagged.verification-before-completion— evidence-before-claims, with doc-only and intended-red (failing-test) carve-outs.
conventions-schema.json — per-repo slots (gate command, base branch, package kind, PHP floor,
docs path, rule framework / test-case base / identifier scheme) the skills and guidelines resolve at
sync time, so one catalog tunes itself per repo.
Install
Allowlist it and sync with a boost engine
(sandermuller/boost-core or
laravel/boost):
The skill and guidelines fan out into each configured agent's directory (Claude Code, Codex, Cursor,
…). Per-repo values are supplied through withConventions(...) against conventions-schema.json.
License
MIT — see LICENSE.