generate-architecture

Generate Laravel package architecture documentation by reading PRD requirements and code standards to output structured markdown files defining package structure, components, and data flow. This ensures clarity on technical organization and folder structure without manual writing.

Laravel package architecture documentation should include package structure, component architecture, data flow, configuration, and extension points. It must reflect PRD requirements, tech stack constraints, and architectural principles like No DDD and pragmatic SOLID.

You can update existing architecture documentation for a Laravel package by re-evaluating the PRD and code standards. The Skill supports updating current docs to ensure adherence to specific architectural principles and technical organization constraints.

This architecture generation approach works without Domain-Driven Design by enforcing a No DDD principle alongside pragmatic SOLID standards. It structures Laravel packages based on technical organization and folder structure rather than domain layers.

The best way to document extension points in a Laravel package is to generate structured markdown files that define component architecture and configuration. This ensures extension points adhere to defined code standards and tech stack constraints.