Coding Standard Laravel Package

Product Decisions This Supports

• Enforce consistency in PHP/Laravel codebases to reduce technical debt and onboarding friction.
• Accelerate onboarding for new developers by standardizing coding practices (e.g., naming conventions, PSR compliance).
• Leverage ShipMonk’s internal standards if building a package for ShipMonk’s ecosystem (e.g., internal tools, shared libraries).
• Build vs. Buy: Justify adopting this over generic standards (e.g., slevomat/coding-standard) if ShipMonk-specific rules (e.g., custom naming, business logic patterns) are critical.
• Roadmap alignment: Use as a foundation for future Laravel/PHP projects requiring strict quality gates (e.g., CI/CD integration, pre-release checks).

When to Consider This Package

• Use this if:

  • Your team is part of ShipMonk’s ecosystem and needs alignment with their internal standards.
  • You prioritize ShipMonk-specific conventions (e.g., custom naming, framework integrations) over generic PSR rules.
  • You’re building a Laravel/PHP package for ShipMonk and need to meet their baseline quality requirements.

• Look elsewhere if:

  • You need a generic, widely adopted standard (e.g., slevomat/coding-standard, PSR12).
  • Your project requires custom rules not covered by ShipMonk’s standard (e.g., domain-specific logic).
  • You’re working outside ShipMonk’s ecosystem and don’t need their proprietary conventions.
  • The package’s maturity is unclear (low stars, recent release date; validate with ShipMonk’s engineering team).

How to Pitch It (Stakeholders)

For Executives: "This package standardizes ShipMonk’s PHP/Laravel coding practices, reducing bugs and developer ramp-up time. By adopting it, we ensure consistency across our ecosystem—critical for scaling internal tools and third-party packages. It’s a lightweight, MIT-licensed solution that aligns with ShipMonk’s existing workflows, saving time on custom rule-sets."

For Engineering: *"This is ShipMonk’s internal phpcs configuration, built on top of slevomat/coding-standard. It enforces their conventions (e.g., naming, PSR compliance) out-of-the-box. Perfect for:

• New projects needing ShipMonk alignment.
• CI/CD pipelines to auto-fix issues pre-merge.
• Code reviews to reduce bikeshedding over style. Tradeoff: Less flexible than generic standards, but saves reinventing the wheel for ShipMonk-specific needs. Recommend pairing with phpcbf for auto-fixes."*