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.

asas-design-fidelity - Skill

Name: asas-design-fidelity
Author: asas-erp-saas-1

Imported from asas-erp-saas-1/As (docs/engineering-history/branches/055-archive__engineering-history-integrity-2026-10-17/docs/engineering-history/branches/052-archive__engineering-history-2026-10-16/engineering-history/branch-snapshots/045--feat--engineering-workflow-2026-10-16/.agents/skills/asas-design-fidelity/SKILL.md). Install upstream with npx skills add asas-erp-saas-1/As --skill asas-design-fidelity. Copyright stays with the author.

Design Fidelity

Design authority

Product/business semantics come from ASAS architecture/contracts. Visual/design intent comes from accepted Figma/design contracts. Executable UI is repository code. Runtime behavior is tested implementation.

Pipeline

IDEA → UX MODEL → TOKENS → PRIMITIVES → COMPONENTS → PATTERNS → FIGMA → DESIGN REVIEW → DESIGN ACCEPTED → CODEX IMPLEMENTATION → BROWSER QA → VISUAL QA → ACCESSIBILITY QA → RESPONSIVE QA → ACCEPTED.

Figma MCP

Use official Figma MCP when configured. It provides structured design context; it does not guarantee perfect code. Use Code Connect when real ASAS components are stable and mappings are trustworthy.

Acceptance

Check:

component reuse;
variables/tokens;
typography;
spacing/layout constraints;
interaction states;
loading/empty/error states;
Arabic/RTL/French/English;
keyboard/focus/accessibility;
responsive behavior;
real-data density;
mobile/tablet/desktop;
visual regression.

Never fix an architectural component problem with arbitrary CSS. Escalate the contract when design and domain semantics conflict.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install asas-design-fidelity 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.

{ "ocm": "1", "id": "asas-erp-saas-1-as-asas-design-fidelity", "kind": "skill", "name": "asas-design-fidelity", "description": "Turn accepted ASAS Figma design-system intent into implementation-ready contracts and verify responsive, RTL, accessibility and visual fidelity in Codex.", "publisher": "asas-erp-saas-1", "version": "1.0.0", "capabilities": { "domains": [ "coding", "legal" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Turn accepted ASAS Figma design-system intent into implementation-ready contracts and verify responsive, RTL, accessibility and visual fidelity in Codex." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/asas-erp-saas-1/As", "path": "docs/engineering-history/branches/055-archive__engineering-history-integrity-2026-10-17/docs/engineering-history/branches/052-archive__engineering-history-2026-10-16/engineering-history/branch-snapshots/045--feat--engineering-workflow-2026-10-16/.agents/skills/asas-design-fidelity/SKILL.md", "ref": "2672247aab8ce830091db1df83d1b233aa88d17f", "url": "https://github.com/asas-erp-saas-1/As/blob/2672247aab8ce830091db1df83d1b233aa88d17f/docs/engineering-history/branches/055-archive__engineering-history-integrity-2026-10-17/docs/engineering-history/branches/052-archive__engineering-history-2026-10-16/engineering-history/branch-snapshots/045--feat--engineering-workflow-2026-10-16/.agents/skills/asas-design-fidelity/SKILL.md", "key": "asas-erp-saas-1/As/docs/engineering-history/branches/055-archive__engineering-history-integrity-2026-10-17/docs/engineering-history/branches/052-archive__engineering-history-2026-10-16/engineering-history/branch-snapshots/045--feat--engineering-workflow-2026-10-16/.agents/skills/asas-design-fidelity/SKILL.md" } }, "instructions": "# Design Fidelity\n\n## Design authority\n\nProduct/business semantics come from ASAS architecture/contracts. Visual/design intent comes from accepted Figma/design contracts. Executable UI is repository code. Runtime behavior is tested implementation.\n\n## Pipeline\n\n`IDEA → UX MODEL → TOKENS → PRIMITIVES → COMPONENTS → PATTERNS → FIGMA → DESIGN REVIEW → DESIGN ACCEPTED → CODEX IMPLEMENTATION → BROWSER QA → VISUAL QA → ACCESSIBILITY QA → RESPONSIVE QA → ACCEPTED`.\n\n## Figma MCP\n\nUse official Figma MCP when configured. It provides structured design context; it does not guarantee perfect code. Use Cod", "cost": { "context_tokens": 279 } }

asas-design-fidelity

About

Design Fidelity

Design authority

Pipeline

Figma MCP

Acceptance

Use it

Install asas-design-fidelity 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

Manifest

Reviews