
Fits your framework. Fits your workflow.
Use the framework with Laravel, Symfony, Yii3 or plain PHP. Keep your existing dependency injection, caching and deployment workflows — without locking your application into a new ecosystem.
Fits the stack you already run
Bridges for your framework, behaviors as container services, and help for your coding agent.
Framework bridges
Symfony, Laravel and Yii3 bridges register your behaviors and warm the cache with your framework’s own commands.
Pick your frameworkYour container
Behavior classes are PSR-11 services that take their dependencies from your application container.
See howAI coding agents
An Agent Skill teaches Claude Code and other agents to write behaviors, wire the bridges and debug them.
Read the guide
Install the bridge for your framework
Each bridge registers your behaviors from the container and warms the cache with your framework's own commands. The Agent Skill teaches your coding agent the 4.x API.
- SymfonyBundle 4.0
Behaviors registered automatically, a web profiler panel, and weaving during cache:warmup.
Symfony guidecomposer require goaop/goaop-symfony-bundle - LaravelBridge 2.0
Auto-discovery, behaviors from config or a container tag, and php artisan aop:warmup.
Laravel guidecomposer require goaop/goaop-laravel-bridge - Yii3Bridge 1.0
Wired through yiisoft/config, with ./yii aop:warmup for deploys.
Yii3 guidecomposer require goaop/goaop-yii3-bridge - AI coding agentsAgent Skill
Teaches Claude Code and other agents to write behaviors, wire the bridges and debug one that does not run.
AI agents guide/plugin marketplace add goaop/framework
Behaviors take dependencies from your app
Register each behavior class lazily in the kernel: it is built on the first call that runs it, after your application has attached its container. Weaving and cache warm-up never create one.
protected function configureAop(AspectContainer $container): void{ // Runs on the first advice call, when the application container is already attached $container->addLazyService( MonitorAspect::class, static fn(AspectContainer $container) => new MonitorAspect($container->getService(LoggerInterface::class)), );} // Once the application container existsApplicationAspectKernel::getInstance()->getContainer()->setDelegate($psrContainer);#[Around('execution(public App\Order\OrderService->placeOrder(*))')]/** @param MethodInvocation<OrderService, Order> $invocation */public function measure(MethodInvocation $invocation): Order{ return $invocation->proceed(); // PHPStan knows this is an Order}Fits in, stays out of the way
No lock-in
With attribute pointcuts your domain classes use only your own attributes and never import the framework.
Behaviors as services
Each behavior class (an aspect) is a PSR-11 service. setDelegate() lets it take dependencies from your application container.
Typed joinpoints
Joinpoints carry generics such as MethodInvocation<OrderService, Order>, so PHPStan and your IDE know the types.
Everything else in the box
- Pure PHPNo extensions. No black boxes. Just PHP.
- Intercept anythingNo method is off limits.
- Property hooksIntercept every property read and write.
- DebuggableNo magic you can't step through.
- PerformanceZero cost without behaviors, under 1 µs with them.
- Pointcut languageSelect exactly the code you mean, and try it live.
- Class extensionsNew interfaces and traits for existing classes.