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.

section-redesign - Prompt - OpenSmartRoute

Name: section-redesign
Author: FatherSonOne

Prompt file imported from FatherSonOne/Pulse-1 (.claude/commands/section-redesign.md). Fill in {{arguments}} before use. Copyright stays with the author.

Section Redesign — Triple-Mockup → Polish → Implementation Plan

End-to-end Pulse section redesign workflow. Audits the section's current code, generates 3 distinct design directions as a single HTML playground (paths A/B/C in _design-playground/), assists you picking + iterating, polishes the chosen direction, then produces a phased implementation handoff doc with an exhaustive feature-disposition matrix.

Target section: {{arguments}}

How to use

Invoke this command with the section name as the argument. If you don't pass one, the agent will ask.

Examples:

/section-redesign Email
/section-redesign Calendar
/section-redesign Contacts
/section-redesign Glimpse threads
/section-redesign Dashboard
/section-redesign            ← will ask which section

What happens

The agent runs the section-redesign skill, which walks six phases:

Phase	What happens	Stop point
0 — Setup	Confirm section + locate source	Confirmed
1 — Reconnaissance	Read the section's components/stores/services; summarize the feature surface in ~150 words	You give any biases or just say "go"
2 — 3 Mockups	Generate `_design-playground/<section>-redesign.html` with 3 distinct directions (paths A/B/C, switchable via top bar, both themes, fake Pulse sidebar). Headless-verify with Playwright.	You open the HTML and pick a path
3 — User picks	Save the choice as a project memory; acknowledge	You say "iterate", "polish", "make the plan", or stop
4 — Hybrid/iterate	(Optional) Generate 2–3 hybrid integration patterns; re-verify	You pick the hybrid variant
5 — Polish	(Optional) Add targeted polish: transitions, micro-interactions, edge states, keyboard shortcuts, state preservation, action toasts, done states	You say "good" or "more X"
6 — Handoff	(Optional) Audit current code (Explore subagent + ground-truth reads), build feature-disposition matrix (every feature → preserved / moved / deferred / removed), write phased plan to `docs/<SECTION>_REDESIGN_HANDOFF_<YYYY-MM-DD>.md`, update memory	Doc delivered

You drive the cadence. The agent does NOT auto-advance through phases.

What you get

A playground at _design-playground/<section>-redesign.html — self-contained, runs in any browser, dark + light themes, 3 (or more after hybridizing) explorable design directions
Verification screenshots at _design-playground/_shots/<section>-*.png
A memory entry at ~/.claude/projects/f--pulse1/memory/project_pulse_<section>_redesign_direction.md recording your chosen direction
An implementation handoff doc (only if you reach Phase 6) at docs/<SECTION>_REDESIGN_HANDOFF_<YYYY-MM-DD>.md — phased, with a complete feature disposition matrix; self-contained enough for a builder agent to pick up cold

What it does NOT do

No production code changes. This skill produces docs + playgrounds. Implementation is delegated to a separate builder agent reading the handoff doc.
No commits. Per CLAUDE.md, only commits when explicitly asked.
No feature dropping. The Phase 6 disposition matrix is the contract — anything not mapped is a bug in the doc, and the agent will surface it as a "Decisions needed" gap rather than silently drop it.

Reference — worked example

The Email section, May 2026 — produced via this exact workflow:

Playground: _design-playground/email-redesign.html
Verify script: _design-playground/_verify-email.mjs
Chosen direction: Path A · Inline Toggle (Cockpit-as-main + segmented-pill Triage mode)
Memory: ~/.claude/projects/f--pulse1/memory/project_pulse_email_redesign_direction.md
Handoff doc: docs/EMAIL_HYBRID_REDESIGN_HANDOFF_2026-05-27.md

Compare your output against these — they're the gold standard.

Related commands

/design-playground — single-section playground with controls/sliders (different pattern: knobs to tune one design, not 3 directions to compare)
/style-section — apply Pulse premium dark CSS to an existing section (visual-only refresh; no architectural change)
/section-deep-dive — discovery + diagnosis on an existing section (no redesign output)
/ui-enhance — dual-agent UI/UX enhancement plan (more focused on incremental polish than rethink)

Pick /section-redesign when you want to reimagine a section, not refresh it.

Install section-redesign 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.

# Section Redesign — Triple-Mockup → Polish → Implementation Plan End-to-end Pulse section redesign workflow. Audits the section's current code, generates 3 distinct design directions as a single HTML playground (paths A/B/C in `_design-playground/`), assists you picking + iterating, polishes the chosen direction, then produces a phased implementation handoff doc with an exhaustive feature-disposition matrix. **Target section:** {{arguments}} --- ## How to use Invoke this command with the section name as the argument. If you don't pass one, the agent will ask. Examples: ``` /section-redesign Email /section-redesign Calendar /section-redesign Contacts /section-redesign Glimpse threads /section-redesign Dashboard /section-redesign ← will ask which section ``` --- ## What happens The agent runs the [`section-redesign` skill](../skills/section-redesign/SKILL.md), which walks six phases: | Phase | What happens | Stop point | |-------|--------------|-----------| | **0 — Setup** | Confirm section + locate source | Confirmed | | **1 — Reconnaissance** | Read the section's components/stores/services; summarize the feature surface in ~150 words | You give any biases or just say "go" | | **2 — 3 Mockups** | Generate `_design-playground/<section>-redesign.html` with 3 distinct directions (paths A/B/C, switchable via top bar, both themes, fake Pulse sidebar). Headless-verify with Playwright. | You open the HTML and pick a path | | **3 — User picks** | Save the choice as a project memory; acknowledge | You say "iterate", "polish", "make the plan", or stop | | **4 — Hybrid/iterate** | (Optional) Generate 2–3 hybrid integration patterns; re-verify | You pick the hybrid variant | | **5 — Polish** | (Optional) Add targeted polish: transitions, micro-interactions, edge states, keyboard shortcuts, state preservation, action toasts, done states | You say "good" or "more X" | | **6 — Handoff** | (Optional) Audit current code (Explore subagent + ground-truth reads), build feature-disposition matrix (every feature → preserved / moved / deferred / removed), write phased plan to `docs/<SECTION>_REDESIGN_HANDOFF_<YYYY-MM-DD>.md`, update memory | Doc delivered | You drive the cadence. The agent does NOT auto-advance through phases. --- ## What you get - **A playground** at `_design-playground/<section>-redesign.html` — self-contained, runs in any browser, dark + light themes, 3 (or more after hybridizing) explorable design directions - **Verification screenshots** at `_design-playground/_shots/<section>-*.png` - **A memory entry** at `~/.claude/projects/f--pulse1/memory/project_pulse_<section>_redesign_direction.md` recording your chosen direction - **An implementation handoff doc** (only if you reach Phase 6) at `docs/<SECTION>_REDESIGN_HANDOFF_<YYYY-MM-DD>.md` — phased, with a complete feature disposition matrix; self-contained enough for a builder agent to pick up cold --- ## What it does NOT do - **No production code changes.** This skill produces docs + playgrounds. Implementation is delegated to a separate builder agent reading the handoff doc. - **No commits.** Per CLAUDE.md, only commits when explicitly asked. - **No feature dropping.** The Phase 6 disposition matrix is the contract — anything not mapped is a bug in the doc, and the agent will surface it as a "Decisions needed" gap rather than silently drop it. --- ## Reference — worked example The Email section, May 2026 — produced via this exact workflow: - Playground: [`_design-playground/email-redesign.html`](../../_design-playground/email-redesign.html) - Verify script: [`_design-playground/_verify-email.mjs`](../../_design-playground/_verify-email.mjs) - Chosen direction: Path A · Inline Toggle (Cockpit-as-main + segmented-pill Triage mode) - Memory: `~/.claude/projects/f--pulse1/memory/project_pulse_email_redesign_direction.md` - Handoff doc: [`docs/EMAIL_HYBRID_REDESIGN_HANDOFF_2026-05-27.md`](../../docs/EMAIL_HYBRID_REDESIGN_HANDOFF_2026-05-27.md) Compare your output against these — they're the gold standard. --- ## Related commands - `/design-playground` — single-section playground with controls/sliders (different pattern: knobs to tune one design, not 3 directions to compare) - `/style-section` — apply Pulse premium dark CSS to an existing section (visual-only refresh; no architectural change) - `/section-deep-dive` — discovery + diagnosis on an existing section (no redesign output) - `/ui-enhance` — dual-agent UI/UX enhancement plan (more focused on incremental polish than rethink) Pick `/section-redesign` when you want to **reimagine** a section, not refresh it.

{ "prompt": "# Section Redesign — Triple-Mockup → Polish → Implementation Plan\n\nEnd-to-end Pulse section redesign workflow. Audits the section's current code, generates 3 distinct design directions as a single HTML playground (paths A/B/C in `_design-playground/`), assists you picking + iterating, polishes the chosen direction, then produces a phased implementation handoff doc with an exhaustive feature-disposition matrix.\n\n**Target section:** {{arguments}}\n\n---\n\n## How to use\n\nInvoke this command with the section name as the argument. If you don't pass one, the agent will ask.\n\nExamples:\n\n```\n/section-redesign Email\n/section-redesign Calendar\n/section-redesign Contacts\n/section-redesign Glimpse threads\n/section-redesign Dashboard\n/section-redesign ← will ask which section\n```\n\n---\n\n## What happens\n\nThe agent runs the [`section-redesign` skill](../skills/section-redesign/SKILL.md), which walks six phases:\n\n| Phase | What happens | Stop point |\n|-------|--------------|-----------|\n| **0 — Setup** | Confirm section + locate source | Confirmed |\n| **1 — Reconnaissance** | Read the section's components/stores/services; summarize the feature surface in ~150 words | You give any biases or just say \"go\" |\n| **2 — 3 Mockups** | Generate `_design-playground/<section>-redesign.html` with 3 distinct directions (paths A/B/C, switchable via top bar, both themes, fake Pulse sidebar). Headless-verify with Playwright. | You open the HTML and pick a path |\n| **3 — User picks** | Save the choice as a project memory; acknowledge | You say \"iterate\", \"polish\", \"make the plan\", or stop |\n| **4 — Hybrid/iterate** | (Optional) Generate 2–3 hybrid integration patterns; re-verify | You pick the hybrid variant |\n| **5 — Polish** | (Optional) Add targeted polish: transitions, micro-interactions, edge states, keyboard shortcuts, state preservation, action toasts, done states | You say \"good\" or \"more X\" |\n| **6 — Handoff** | (Optional) Audit current code (Explore subagent + ground-truth reads), build feature-disposition matrix (every feature → preserved / moved / deferred / removed), write phased plan to `docs/<SECTION>_REDESIGN_HANDOFF_<YYYY-MM-DD>.md`, update memory | Doc delivered |\n\nYou drive the cadence. The agent does NOT auto-advance through phases.\n\n---\n\n## What you get\n\n- **A playground** at `_design-playground/<section>-redesign.html` — self-contained, runs in any browser, dark + light themes, 3 (or more after hybridizing) explorable design directions\n- **Verification screenshots** at `_design-playground/_shots/<section>-*.png`\n- **A memory entry** at `~/.claude/projects/f--pulse1/memory/project_pulse_<section>_redesign_direction.md` recording your chosen direction\n- **An implementation handoff doc** (only if you reach Phase 6) at `docs/<SECTION>_REDESIGN_HANDOFF_<YYYY-MM-DD>.md` — phased, with a complete feature disposition matrix; self-contained enough for a builder agent to pick up cold\n\n---\n\n## What it does NOT do\n\n- **No production code changes.** This skill produces docs + playgrounds. Implementation is delegated to a separate builder agent reading the handoff doc.\n- **No commits.** Per CLAUDE.md, only commits when explicitly asked.\n- **No feature dropping.** The Phase 6 disposition matrix is the contract — anything not mapped is a bug in the doc, and the agent will surface it as a \"Decisions needed\" gap rather than silently drop it.\n\n---\n\n## Reference — worked example\n\nThe Email section, May 2026 — produced via this exact workflow:\n\n- Playground: [`_design-playground/email-redesign.html`](../../_design-playground/email-redesign.html)\n- Verify script: [`_design-playground/_verify-email.mjs`](../../_design-playground/_verify-email.mjs)\n- Chosen direction: Path A · Inline Toggle (Cockpit-as-main + segmented-pill Triage mode)\n- Memory: `~/.claude/projects/f--pulse1/memory/project_pulse_email_redesign_direction.md`\n- Handoff doc: [`docs/EMAIL_HYBRID_REDESIGN_HANDOFF_2026-05-27.md`](../../docs/EMAIL_HYBRID_REDESIGN_HANDOFF_2026-05-27.md)\n\nCompare your output against these — they're the gold standard.\n\n---\n\n## Related commands\n\n- `/design-playground` — single-section playground with controls/sliders (different pattern: knobs to tune one design, not 3 directions to compare)\n- `/style-section` — apply Pulse premium dark CSS to an existing section (visual-only refresh; no architectural change)\n- `/section-deep-dive` — discovery + diagnosis on an existing section (no redesign output)\n- `/ui-enhance` — dual-agent UI/UX enhancement plan (more focused on incremental polish than rethink)\n\nPick `/section-redesign` when you want to **reimagine** a section, not refresh it.", "variables": [ "arguments" ], "notes": "End-to-end Pulse section redesign workflow. Audits the section's current code, generates 3 distinct design directions as a single HTML playground (paths A/B/C in `_design-playground/`), assists you picking + iterating, polishes the chosen direction, then produces a phased implementation handoff doc with an exhaustive feature-disposition matrix.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/FatherSonOne/Pulse-1", "path": ".claude/commands/section-redesign.md", "ref": "95b5031ff692c46c25846a3a0d0fe5a8b4f1b868", "url": "https://github.com/FatherSonOne/Pulse-1/blob/95b5031ff692c46c25846a3a0d0fe5a8b4f1b868/.claude/commands/section-redesign.md", "key": "FatherSonOne/Pulse-1/.claude/commands/section-redesign.md" } } }

section-redesign

About

Section Redesign — Triple-Mockup → Polish → Implementation Plan

How to use

What happens

What you get

What it does NOT do

Reference — worked example

Related commands

Install section-redesign 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