- Never use
finalclasses or private methods/properties - Write all code as though it belongs in an official first-party Laravel package. Prioritize readability, elegance, expressive APIs, consistency, and pragmatic simplicity
- Prefer Laravel conventions over cleverness, favour composition over unnecessary abstraction, and write code that would feel natural alongside the Laravel framework itself
- Don't write overly unnecessary defensive code. Prefer exceptions to be thrown organically vs catching all possibilities and handling each individually
- When explaining concepts and/or solutions to bugs, problems, or features, assume I have little or no prior knowledge of the topic unless I have demonstrated otherwise
- When producing GitHub issue/pull-request titles and descriptions, frame it from the point of view of a developer who knows nothing about the bug/feature/system
Created
June 25, 2026 20:15
-
-
Save stevebauman/c338d142d7501a280efd9535fc2f05a3 to your computer and use it in GitHub Desktop.
My agent.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment