symfony-ux

Guides Symfony developers in selecting and combining Stimulus, Turbo, TwigComponent, and LiveComponent for frontend interactivity.

166|12|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/smnandre/symfony-ux-skills --skill symfony-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: symfony-ux
Source: https://github.com/smnandre/symfony-ux-skills/tree/main/skills/symfony-ux
Command: npx skills add https://github.com/smnandre/symfony-ux-skills --skill symfony-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates selecting and orchestrating Symfony UX tools (Stimulus, Turbo, TwigComponent, LiveComponent) to build modern, reactive frontends with minimal JavaScript.

Core Features & Use Cases

  • Central decision framework to guide tool selection based on interactivity, real-time needs, and component scope.
  • Clear guidance on combining tools to deliver SPA-like experiences, server-rendered UI, and real-time patterns in Symfony apps.
  • Real-world scenarios include interactive components, live forms, and partial-page updates.

Quick Start

Create a simple interactive Symfony frontend by starting with Stimulus and TwigComponent, then progressively add Turbo for partial updates and LiveComponent for server-driven interactivity.

Frequently Asked Questions about symfony-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add real-time interactivity to a Symfony app without writing a JavaScript framework?

To add interactivity with minimal JavaScript, Symfony UX combines Stimulus controllers with TwigComponent for reusable UI. This orchestrates reactive frontend behavior by rendering templates server-side and managing state without a heavy JavaScript framework.

When should I use Turbo versus LiveComponent for partial page updates in Symfony?

Use Turbo for frame-based partial page updates and LiveComponent for server-driven reactive state. LiveComponent re-renders individual Twig components via server requests, while Turbo handles broader SPA-like navigation and link interception.

What is the best way to structure interactive Twig components in a Symfony frontend?

The best way to structure interactive Twig components is using TwigComponent for reusable server-rendered UI blocks and Stimulus for light behavior. This isolates presentation logic before progressively adding LiveComponent for dynamic interactions.

Can I build a SPA-like experience using Twig and Symfony UX tools?

Yes, you can build a SPA-like experience using Symfony UX by combining Turbo Drive and Frames for navigation. This intercepts links and form submissions to render partial updates dynamically, avoiding full page reloads while maintaining Twig rendering.

Does Symfony UX require a complex JavaScript build setup to use Stimulus?

Symfony UX requires minimal JavaScript configuration to use Stimulus, relying on lightweight controllers attached to HTML elements. This avoids a complex build pipeline by leveraging standard Twig rendering and server-side state management.