ui-agent-routing

Wire active UI spec packages into agent routing files for CLAUDE, Gemini, Cursor, and Copilot.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/ThorStarlord/interface-skills --skill ui-agent-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-agent-routing
Source: https://github.com/ThorStarlord/interface-skills/tree/main/skills/ui-agent-routing
Command: npx skills add https://github.com/ThorStarlord/interface-skills --skill ui-agent-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents AI coding agents from editing implementation code using stale or incomplete UI specification references by wiring the active spec package into the repo’s agent-facing routing files.

Core Features & Use Cases

  • Agent-facing routing updates: Ensures CLAUDE.md, AGENTS.md, GEMINI.md, Cursor/Copilot rules, route maps, and per-directory context files point to the active spec package index.
  • Deprecated path redirects: Identifies old spec paths used by agents and creates DEPRECATED.md redirect notices so the routing layer stays unambiguous.
  • Report vs patch outputs: Produces a routing report with an exact edit plan, or applies bounded marker edits in patch mode after approval.

Quick Start

Use ui-agent-routing after a UI spec package is complete or recovered, so agents reliably find and read the active spec before touching any related UI implementation code.

Frequently Asked Questions about ui-agent-routing

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

FAQPage Schema
How do I stop AI coding agents from using stale UI specifications when editing implementation code?

Deprecated path redirects are handled by creating a DEPRECATED.md file containing redirect notices. This identifies old spec paths previously used by agents and ensures the routing layer remains unambiguous across the repository.

How do I update CLAUDE.md and Cursor rules to point at a recovered UI spec package?

You verify end-to-end routing chain traversability by scanning agent-facing files and confirming they correctly reference the active 00-index.md. The Skill produces a routing report to validate the complete chain across all agent documentation.

When do I need to update agent routing files for UI spec packages?

You need to update agent routing files when a UI spec package is complete, recovered, or newly created. It is also required when routes were moved, deprecated, or previously missing from agent documentation across CLAUDE, Gemini, Cursor, and Copilot.

Does this agent routing process apply to Copilot and Gemini repository rules?

Yes, the agent routing process applies to Copilot and Gemini repository rules, alongside CLAUDE.md, AGENTS.md, and Cursor rules. It updates all agent-facing routing files and per-directory context files to reference the active spec package index.

Can I generate a routing report instead of directly patching agent documentation files?

Yes, you can generate a routing report with an exact edit plan instead of patching files directly. In report mode you get the full routing analysis, while patch mode applies bounded marker edits only after explicit approval.