add-route

Add routes to the Petal Pro Phoenix router with enforced live_session and scope conventions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/johngrandson/orkestry --skill add-route-johngrandson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-route
Source: https://github.com/johngrandson/orkestry/tree/main/.claude/skills/add-route
Command: npx skills add https://github.com/johngrandson/orkestry --skill add-route-johngrandson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely adds routes to the Petal Pro Phoenix router, enforcing live_session grouping, pipeline selection, scope conventions, and the modularized route macro pattern to prevent routing conflicts.

Core Features & Use Cases

  • Enforces live_session grouping and shared pipelines when adding new routes to maintain consistency.
  • Validates placement in router.ex and within lib/petal_pro_web/routes/ to ensure correct scope and macro usage.
  • Prevents routing conflicts by applying guardrails and clear guidance during route creation across common app structures (public, authenticated, and admin scopes).

Quick Start

Provide the route you want to add as an argument and let the skill apply the correct live_session scope, pipelines, and route macro conventions.

Frequently Asked Questions about add-route

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

FAQPage Schema
How do I add new routes to a Petal Pro Phoenix router without causing routing conflicts?

Adding routes safely requires enforcing live_session grouping, pipeline selection, and scope conventions. Validating placement within router.ex and modular route files prevents routing conflicts across public, authenticated, and admin scopes.

What is the correct way to use live_session and scope macros in Elixir Phoenix routing?

Using live_session and scope macros correctly involves grouping routes by authentication state and applying shared pipelines. This maintains consistent routing patterns and ensures modular route macro usage across the application structure.

Can I add an admin route to lib/petal_pro_web/routes/ and automatically apply the correct pipeline?

Yes, you can add an admin route to the dedicated routes files and have the correct pipeline applied. Guardrails validate exact routing macros and scope usage to ensure the admin pipeline configuration is correctly enforced.

Why does my Phoenix router throw a routing conflict when adding a new live_session?

A routing conflict when adding a live_session usually occurs due to incorrect scope placement or missing pipeline configuration. Applying modular route macro conventions and validating exact routing macros prevents these structural conflicts.

What's the best way to manage modular route macros across public, authenticated, and admin scopes in Phoenix?

The best way to manage modular route macros is enforcing consistent patterns across router.ex and dedicated route files. Validating scope usage and pipeline configuration ensures correct macro deployment across all application scopes.