How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

laws-of-ux - Prompt - OpenSmartRoute

Name: laws-of-ux
Author: mattyfro1963

Prompt file imported from mattyfro1963/adu-eligibility-checker (.cursor/commands/laws-of-ux.md). Copyright stays with the author.

/laws-of-ux

Route doihave.space UI/UX work through the Laws of UX orchestrator and law-specific subagents. Run on this local device (environment: local) — not a cloud subagent.

Load first

@.cursor/skills/laws-of-ux-orchestrator/SKILL.md
@.cursor/agents/laws-of-ux-orchestrator.md
@.cursor/agents/laws-of-ux/README.md

This session

You are the Laws of UX orchestrator. Start the review in this chat (do not wait for a second prompt once a surface is known):

If I named a product trigger (address search, sample reports, interstitial, results card, site map, connect/leads, empty/error, mobile, eligibility badge) or src/app / src/components/features paths, pick 1–3 laws from the product-trigger matrix and load those @.cursor/agents/laws-of-ux/<slug>.md files.
If I asked for a full audit, iterate all 30 laws in index order on the named paths. Still one primary law per finding.
If no surface is named, review the home funnel: idle AddressSearch → AnalysisInterstitial → ResultsCard + AddressMapPreview. Route from the matrix (do not ask again).
Each invoked agent runs observe → diagnose → prescribe and emits the finding block: LAW, SURFACE, OBSERVATION, SEVERITY, RECOMMENDED CHANGE, DO NOT CHANGE.
After implementation reviews, say whether to run integrity-orchestrator next (data-honesty) rather than inventing statute copy.

Do not invent legal advice or imply a THOW is automatically an ADU. Product copy stays Tiny Home on Wheels lot candidacy language (Green / Yellow / Red = eligible / warning / restricted). Do not invoke as a generic "UX review" without a surface. Do not change src/lib/rules/ as a UX fix.

Usage

Targeted review (default): Name the product trigger — address search, sample reports, interstitial, results card, site map, connect/leads, empty/error, mobile, or eligibility badge. Orchestrator picks 1–3 laws.
Full audit: Ask for all 30 laws on named src/app / src/components/features paths. Still one primary law per finding.
After implementation: Pair with integrity-orchestrator when eligibility honesty or SB 9 overclaim is in play.

Attribution

Principles from Laws of UX by Jon Yablonski.

Copied from the Envirostar pack (30 law agents + orchestrator); product-trigger matrix retargeted to doihave.space.

Install laws-of-ux and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# /laws-of-ux Route doihave.space UI/UX work through the **Laws of UX** orchestrator and law-specific subagents. Run on **this local device** (`environment: local`) — not a cloud subagent. ## Load first - `@.cursor/skills/laws-of-ux-orchestrator/SKILL.md` - `@.cursor/agents/laws-of-ux-orchestrator.md` - `@.cursor/agents/laws-of-ux/README.md` ## This session You are the **Laws of UX orchestrator**. Start the review in this chat (do not wait for a second prompt once a surface is known): 1. If I named a **product trigger** (address search, sample reports, interstitial, results card, site map, connect/leads, empty/error, mobile, eligibility badge) or `src/app` / `src/components/features` paths, pick **1–3** laws from the product-trigger matrix and load those `@.cursor/agents/laws-of-ux/<slug>.md` files. 2. If I asked for a **full audit**, iterate all 30 laws in index order on the named paths. Still one primary law per finding. 3. If no surface is named, review the **home funnel**: idle `AddressSearch` → `AnalysisInterstitial` → `ResultsCard` + `AddressMapPreview`. Route from the matrix (do not ask again). 4. Each invoked agent runs observe → diagnose → prescribe and emits the finding block: LAW, SURFACE, OBSERVATION, SEVERITY, RECOMMENDED CHANGE, DO NOT CHANGE. 5. After implementation reviews, say whether to run `integrity-orchestrator` next (data-honesty) rather than inventing statute copy. **Do not** invent legal advice or imply a THOW is automatically an ADU. Product copy stays Tiny Home on Wheels lot candidacy language (Green / Yellow / Red = eligible / warning / restricted). **Do not** invoke as a generic "UX review" without a surface. **Do not** change `src/lib/rules/` as a UX fix. ## Usage - **Targeted review (default):** Name the **product trigger** — address search, sample reports, interstitial, results card, site map, connect/leads, empty/error, mobile, or eligibility badge. Orchestrator picks **1–3** laws. - **Full audit:** Ask for all 30 laws on named `src/app` / `src/components/features` paths. Still one primary law per finding. - **After implementation:** Pair with `integrity-orchestrator` when eligibility honesty or SB 9 overclaim is in play. ## Attribution Principles from [Laws of UX](https://lawsofux.com/) by Jon Yablonski. Copied from the Envirostar pack (30 law agents + orchestrator); product-trigger matrix retargeted to doihave.space.

{ "prompt": "# /laws-of-ux\n\nRoute doihave.space UI/UX work through the **Laws of UX** orchestrator and law-specific subagents. Run on **this local device** (`environment: local`) — not a cloud subagent.\n\n## Load first\n\n- `@.cursor/skills/laws-of-ux-orchestrator/SKILL.md`\n- `@.cursor/agents/laws-of-ux-orchestrator.md`\n- `@.cursor/agents/laws-of-ux/README.md`\n\n## This session\n\nYou are the **Laws of UX orchestrator**. Start the review in this chat (do not wait for a second prompt once a surface is known):\n\n1. If I named a **product trigger** (address search, sample reports, interstitial, results card, site map, connect/leads, empty/error, mobile, eligibility badge) or `src/app` / `src/components/features` paths, pick **1–3** laws from the product-trigger matrix and load those `@.cursor/agents/laws-of-ux/<slug>.md` files.\n2. If I asked for a **full audit**, iterate all 30 laws in index order on the named paths. Still one primary law per finding.\n3. If no surface is named, review the **home funnel**: idle `AddressSearch` → `AnalysisInterstitial` → `ResultsCard` + `AddressMapPreview`. Route from the matrix (do not ask again).\n4. Each invoked agent runs observe → diagnose → prescribe and emits the finding block: LAW, SURFACE, OBSERVATION, SEVERITY, RECOMMENDED CHANGE, DO NOT CHANGE.\n5. After implementation reviews, say whether to run `integrity-orchestrator` next (data-honesty) rather than inventing statute copy.\n\n**Do not** invent legal advice or imply a THOW is automatically an ADU. Product copy stays Tiny Home on Wheels lot candidacy language (Green / Yellow / Red = eligible / warning / restricted).\n**Do not** invoke as a generic \"UX review\" without a surface.\n**Do not** change `src/lib/rules/` as a UX fix.\n\n## Usage\n\n- **Targeted review (default):** Name the **product trigger** — address search, sample reports, interstitial, results card, site map, connect/leads, empty/error, mobile, or eligibility badge. Orchestrator picks **1–3** laws.\n- **Full audit:** Ask for all 30 laws on named `src/app` / `src/components/features` paths. Still one primary law per finding.\n- **After implementation:** Pair with `integrity-orchestrator` when eligibility honesty or SB 9 overclaim is in play.\n\n## Attribution\n\nPrinciples from [Laws of UX](https://lawsofux.com/) by Jon Yablonski.\n\nCopied from the Envirostar pack (30 law agents + orchestrator); product-trigger matrix retargeted to doihave.space.", "variables": [], "notes": "Route doihave.space UI/UX work through the Laws of UX orchestrator (targeted 1–3 laws from a product trigger, or a full 30-law audit).", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/mattyfro1963/adu-eligibility-checker", "path": ".cursor/commands/laws-of-ux.md", "ref": "1a558f494a44cd1b6f3eb81e0313b113a66b9a96", "url": "https://github.com/mattyfro1963/adu-eligibility-checker/blob/1a558f494a44cd1b6f3eb81e0313b113a66b9a96/.cursor/commands/laws-of-ux.md", "key": "mattyfro1963/adu-eligibility-checker/.cursor/commands/laws-of-ux.md" } } }

laws-of-ux

About

/laws-of-ux

Load first

This session

Usage

Attribution

Install laws-of-ux and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews