Composer Standards
by Convext
Composer dependency management for PHP
Rules (22)
Config
Config in env vars, not code. Never commit .env. Commit .env.example. Never hardcode secrets.
Database
Passwords: bcrypt. API keys: encrypt. PII: field-level encryption. Never log sensitive data.
Dependencies
Use latest stable versions. Fix breaking changes—don't avoid upgrades. Check official registries.
Git
Small, focused commits. Use: feat/fix/refactor/test/docs/chore. Each commit independently deployable.
Llm Behavior
User and tests define done. Don't redefine scope or declare partial progress as complete.
You wrote every line. No 'pre-existing issues'—only issues you haven't fixed yet.
No excuses: 'pre-existing', 'unrelated', 'tedious', 'for now'. Recognize and continue working.
Python
Use `uv` (not pip/poetry/pipenv). 100x faster, lockfile support, built-in venv. Commands: `uv add`, `uv run`.
pyproject.toml for deps, uv.lock (commit it), .python-version, src/ layout. Python 3.12+.
Rails
Rails.application.credentials for secrets. `rails credentials:edit`. Environment-specific credentials. Never commit master.key.
Security
Auth: bcrypt/argon2 for passwords, rate limiting, secure sessions/tokens. Authz: check permissions on every request, use policy objects or middleware.
Allowlists, not denylists. Validate type/length/format. Sanitize HTML. Parameterized queries only.
Force SSL, redirect HTTP→HTTPS, secure cookies (Secure/HttpOnly/SameSite), HSTS headers.
Testing
Fix failures immediately. No skipping, no "pre-existing issues." Own the codebase state—a test suite with ignored tests can't be trusted.
Test real instances. Mocking the class under test hides bugs.
Test public interfaces, inputs/outputs. Tests must survive refactoring. Don't test private methods.
1) Write failing test 2) Minimum code to pass 3) Refactor. Every line has a reason.
Mock only: external HTTP APIs, time, filesystem side effects, third-party services. Use real implementations for internal services, database, and business logic.
One logical concept per test. Multiple asserts OK if same concept. Clear test names describing behavior.
Use consistent test data setup: fixtures for stable reference data, factories for dynamic scenarios. Avoid inline object creation scattered throughout tests.
Workflow
Verify changes locally: run app, run tests, check for errors. CI catches environment issues, not basic bugs.
Format → Lint → Test before every commit. Never rely on CI for basic checks.
Language Standards (1)
Use this Ruleset
Sign in to adopt or fork this ruleset
Sign in with GitHubStatistics
- Rules
- 22
- Standards
- 1
- Projects using
- 0
- Created
- Jan 15, 2026