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.

layouts - Skill - OpenSmartRoute

Imported from tongthanhdat009/OnlineMarket (frontend-customer/src/layouts/AGENTS.md). Install upstream with npx skills add tongthanhdat009/OnlineMarket --skill layouts. Copyright stays with the author.

layouts

Purpose

Storefront shells.

Key Files

File	Description
`StoreLayout.tsx`	181 lines. Exports `StoreLayout` — the header, the category nav, the outlet, the AI assistant mount and the footer — plus `AuthLayout`.
`AccountLayout.tsx`	48 lines. Exports `AccountLayout` — the `/account` side nav (profile, security, orders, bills, refunds) around the outlet.

For AI Agents

Working In This Directory

StoreLayout wraps every public page; AuthLayout wraps the login and register pages, which sit outside StoreLayout in ../app/router.tsx.
AccountLayout renders inside the ProtectedRoute branch — it may assume a signed-in customer.
The AI assistant is mounted in StoreLayout, not in a page. Do not mount it a second time.
The header reads the cart count from useCart() and the session from useAuth() — both come from ../app/providers.tsx.

Testing Requirements

npm run build --prefix frontend-customer.
npm test --prefix frontend-customer -- --run.
No layout test. Verify manually: browse anonymously, sign in, open /account.

Common Patterns

The layouts use useOutlet/Outlet for the page slot — the route tree defines the child, the layout provides the chrome.
Vietnamese copy and the storefront tokens from ../styles.css.

Dependencies

Internal

../app/router.tsx — where the layouts are placed in the route tree
../app/providers.tsx — useAuth, useCart, useToast
../components/store-ui.tsx — buttons and search
../components/StoreFooter.tsx — the footer
../components/ai/AiAssistant.tsx — the AI assistant mount

External

react-router-dom 7.18.4 — Outlet, NavLink

Install layouts 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.

layouts

About

layouts

Purpose

Key Files

For AI Agents

Working In This Directory

Testing Requirements

Common Patterns

Dependencies

Internal

External

Install layouts 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