application-architecture-standard
Defines structural rules for Laravel architecture, layering, and code organization
55
Quality
61%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/application-architecture-standard/SKILL.mdPurpose
Single source of truth for application structure and architectural boundaries.
1. Layering Rules
Presentation Layer
- Controllers
- Form Requests (validation only)
No business logic allowed.
Application Layer
- Services
- DTOs
- Transformers
Holds all business logic orchestration.
Domain Layer
- Models Represents state and invariants only.
Infrastructure Layer
- API clients
- External services
Must be replaceable and contain no business logic.
2. Service Rules
- Business logic lives in services.
- Services must remain framework-agnostic except for Laravel infrastructure (Eloquent, DB transactions, HTTP client, logging).
- No view/UI concerns inside services.
- DTOs are used for structured data transfer where transformation, validation, or reuse is required.
- They are optional for internal service calls when validated arrays are sufficient.
3. Dependency Rules
- Constructor injection only
- No service locators
- No hidden dependencies
4. Architecture Integrity
- No cross-layer leakage
- Strict separation of concerns
- Refactoring must preserve behavior
- Repository
- Bottelet/DaybydayCRM
- Commit
fb83b36
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.