Weave Code
Lucid Laravel Package
lucidarch/lucid
Lucid is a Laravel package for building scalable, maintainable apps with Domain-Driven Design and Clean Architecture. It provides Artisan commands to generate domains, actions, services, repositories, and tests, keeping business logic organized.
Build scalable Laravel apps without compromising code quality and the least amount of technical debt. Effortless code navigation, onboarding and reviews. Tailored for Microservices and mindful of Monoliths.
Frequently asked questions about Lucid
- What is Lucid and what problem does it solve in Laravel?
- Lucid is an opinionated Laravel package that provides structure and Artisan generators for Domain-Driven Design and Clean Architecture. It helps organize business logic into domains, features, actions, services, and repositories so code navigation, onboarding, and design reviews are more consistent. It is best for greenfield services, modular monoliths, and microservice templates rather than legacy apps with entrenched conventions.
- How do I install and configure Lucid in a Laravel application?
- Install it via Composer and follow the package documentation to register the Lucid service provider and publish any configuration. It integrates with Laravel Artisan commands so you can generate domains, actions, services, repositories, and tests. Validate Composer constraints and Laravel and PHP versions before adopting it in an existing app.
- Which Laravel and PHP versions does Lucid support?
- The package targets Laravel and PHP teams using Composer, Artisan, and service providers, but you should confirm the exact supported Laravel and PHP constraints in its Composer file and documentation. Check compatibility with your current Laravel major, testing stack, static analysis, and CI pipeline before adoption. Its upgrade policy across Laravel majors should be reviewed as part of dependency assessment.
- Is Lucid a runtime framework or just code generation?
- Lucid is primarily an opinionated structure with Artisan generators and conventional PHP classes, but it can introduce coupling through base classes and service-provider integration. You should verify how much runtime coupling exists in queues, events, and generated base classes. The architecture can often be adopted manually if the package stalls, which lowers abandonment risk.
- Can I use Lucid in an existing Laravel monolith?
- Brownfield adoption is feasible as a bounded pilot, not as a big-bang rewrite. Map one low-risk feature or domain into Lucid concepts, wrap existing behavior incrementally, and document where legacy code remains. Avoid rewriting working code solely to satisfy the structure, and govern coupling and convention drift.
- How does Lucid support testing?
- Lucid provides Artisan commands to generate tests alongside domains, actions, services, and repositories, encouraging test coverage at architectural boundaries. You should still validate generated tests against PHPUnit or Pest, static analysis, and your CI pipeline. Confirm queue, event, and scheduler behavior in staging, not only local development.
- Is Lucid suitable for microservices?
- Lucid is tailored for microservices and mindful of monoliths, but it does not design service boundaries, data ownership, or deployment topology for you. It is most useful as a service template and review vocabulary when teams consistently follow the conventions. Treat it as an architecture aid, not a silver bullet for microservice decomposition.
- What are the production risks of adopting Lucid?
- The main risks are architectural lock-in, convention drift, Laravel-major upgrade friction, and limited public production evidence compared with mainstream Laravel tooling. With modest community signals, teams should assess release cadence, security policy, test coverage, and maintainer responsiveness. Governance is required to prevent feature sprawl and hidden coupling between domains.
- Can I adopt Lucid's architecture without the package?
- Yes, the underlying Domain-Driven Design and Clean Architecture patterns can be implemented manually with Laravel conventions. That gives you an exit strategy if package maintenance slows or generated structure becomes too coupled. Document the boundaries and base abstractions you rely on so you can replace the package incrementally.
- How does Lucid compare to other Laravel DDD or modular packages?
- Lucid is opinionated and prescriptive, emphasizing explicit domains, features, actions, services, and repositories with Artisan generators. Alternatives may offer different trade-offs in modularity, runtime features, or community support. Evaluate fit against your team's willingness to follow conventions, Laravel version support, and long-term maintenance signals.
Weaver
How can I help you explore Laravel packages today?