intent

Route design tasks across strategy, research, and execution sub-skills.

116|9|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ghaida/intent --skill intent-ghaida
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intent
Source: https://github.com/ghaida/intent/tree/main/skills/intent
Command: npx skills add https://github.com/ghaida/intent --skill intent-ghaida

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Intent provides a centralized routing and context-management system for design practice, enabling teams to surface, route, and govern interconnected skills with ethical guardrails and anti-pattern guidance.

Core Features & Use Cases

  • Routing layer that connects strategy, research, IA, copy, and evaluation into a coherent practice
  • Context gathering and knowledge loading from a foundational UX knowledge base and anti-pattern catalog
  • Governance, coordination, and problem-framing support across multiple UX disciplines for design programs

Quick Start

Invoke Intent to initialize project context and route to the relevant design skill for your current task.

Frequently Asked Questions about intent

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

FAQPage Schema
What is a design routing layer and how does it connect UX strategy to execution?

A design routing layer contextualizes UX work by connecting strategy, research, and execution. It governs interconnected disciplines and produces intentional design decisions by loading foundational knowledge and anti-pattern guidance.

How do I route design tasks across multiple UX disciplines during project kickoff?

Invoke the routing layer at kickoff to initialize project context. It frames the problem, gathers relevant knowledge, and routes your current task to the appropriate sub-skill for research, IA, or evaluation.

Can I use this to manage context and prevent anti-patterns in UX governance?

Yes, you can use it to manage context and prevent anti-patterns in UX governance. It provides an anti-pattern catalog and an ethics framework to coordinate strategy, content, and evaluation across design programs.

Does this approach require dependencies to mediate between sub-skills?

No dependencies are required. It operates independently as a foundational routing layer, mediating between 14 sub-skills by leveraging internal references, a knowledge base, and an ethics framework.

What is the best way to frame UX problems using an ethics framework and strategy routing?

The best way to frame UX problems is through centralized context management. It connects strategy routing with an ethics framework to surface guardrails, ensuring problem framing aligns with governance and intentional design.

When should I not use a centralized routing layer for design work?

Avoid using a centralized routing layer for isolated, single-discipline tasks that do not require governance. It is designed to mediate interconnected sub-skills, so simple projects without cross-disciplinary strategy needs may not benefit.