Define and validate PyroManiac DSL configurations for Ash resources and page modules.
npx skills add https://github.com/frankdugan3/pyro_maniac --skill pyro-maniac
Please help me install this Agent Skill. Skill: pyro-maniac Source: https://github.com/frankdugan3/pyro_maniac/tree/main/usage-rules/skills/pyro-maniac Command: npx skills add https://github.com/frankdugan3/pyro_maniac --skill pyro-maniac
PyroManiac removes the manual overhead of designing and validating Ash Framework UI configuration by turning declarative page definitions into a compiled, inspectable DSL.
Use this skill to define or update a PyroManiac page module and Ash resource so the DSL validates correctly and exposes the intended UI metadata.
High-intent search queries and answers about installing and using this skill.
Use a declarative DSL to model Ash UI configurations for pages, views, forms, searches, navigation, and kanban scenarios. This renderer-agnostic approach defines UI behavior once at compile-time, keeping rendering code separate from page modules.
Ash UI DSLs can use Spark transformers and verifiers for compile-time validation. This catches invalid UI definitions early, ensuring strict DSL rules for view types, forms, and navigation items are enforced before runtime execution.
The best way is using a structured UI DSL that models pages, table views, wizard forms, and navigation links as metadata. This removes manual overhead and provides a consistent, inspectable configuration for Ash resources without embedding rendering logic.
Yes, you can define UI behavior in a renderer-agnostic DSL and pair it with a separate renderer for your stack. This allows creating admin or internal app pages for Ash resources with table views, wizard forms, and navigation links independently.
Strict DSL rules require a PyroManiac.Resource default label for validation to pass. This mandatory label ensures the DSL can properly identify and render Ash resources across different view types and form scenarios.
Yes, Spark-based compile-time validation is required to enforce strict DSL rules for view types, forms, and navigation items. This ensures all page modules and Ash resource configurations are validated correctly during compilation.
mauriciodelrioSet up Vite React SPA routing with createBrowserRouter, auth guards, and Zod-validated search parameters.
ksleungacCompare rendered UI screenshots against ground-truth references to identify layout discrepancies.
shotleybuilderCreate Ash Framework 3.0 domain resources with Elixir, Phoenix, and PostgreSQL.
benswiftBuild and debug Elixir apps with Ash resources and Phoenix LiveView.
