Routing Gallery

The gallery is generated from root-level route-cases/*.json files. Each case is intentionally public-safe and includes the selected route, omitted skills, tags, and review notes.

These public-safe canonical route cases show how fuzzy requests become one Primary skill plus focused Supporting skills.

Submit a route case

All tags adr anti-over-routing api architecture auth browser ci connector contract database debugging dependencies design docs docs-site frontend git github maintenance performance permissions regression release review security simple-task source-map static-site typed-client verification vue writing

api

API contract sync

Add account preference fields to a backend endpoint and update the generated frontend client.

The endpoint, OpenAPI schema, typed client, and compatibility tests must ship together.

API / Contract lifecycle > Backend-to-frontend sync

Selected skills

• Primary: api-guidelines-skill
• Supporting: openapi-to-typescript
• Supporting: qa-test-planner

Reason

The contract shape is the main decision, while client generation and compatibility tests reduce rollout risk.

Omitted on purpose

• frontend-design: This is a contract propagation task, not a visual design change.
• database-optimizer: No query performance concern is described.

Public safety: Uses fictional account preference language only. Source JSON

architecture

Architecture decision record

Write an ADR for splitting a reporting feature into ingestion, storage, and dashboard layers.

The team needs a concise decision record with tradeoffs, constraints, and follow-up risks.

Architecture / ADR > Reporting pipeline > Layered decision

Selected skills

• Primary: architecture-designer
• Supporting: c4-architecture
• Supporting: spec-miner

Reason

Architecture owns the decision, C4 clarifies system boundaries, and spec mining extracts constraints from the request.

Omitted on purpose

• database-optimizer: The decision record is not yet optimizing a concrete query.
• frontend-debugging-workflow: No rendered frontend defect is being debugged.

Public safety: Uses fictional reporting architecture context. Source JSON

connector

Connector permission triage

Diagnose why a repository connector can list issues but cannot open pull request comments.

The failure appears only when the agent needs review-thread context from the connected repository.

Connector / GitHub > Permission boundary > Review context

Selected skills

• Primary: github:github
• Supporting: systematic-debugging
• Supporting: qa-test-planner

Reason

The connector is the source of truth; debugging isolates the permission boundary and QA defines the reauthentication check.

Omitted on purpose

• frontend-debugging-workflow: No browser-rendered bug is described.
• database-optimizer: The failure is not related to persistence or queries.

Public safety: Mentions repository connector behavior without naming a private repository. Source JSON

docs

Copy-edit boundary

Rewrite a short release announcement so it is clearer and less repetitive.

The user provided the full text and only wants sharper wording.

Docs / Writing > Small rewrite > No implementation

Selected skills

• Primary: writing-clearly-and-concisely

Reason

The work is prose editing, so adding implementation, release, or test skills would create unnecessary context.

Omitted on purpose

• code-documenter: The task is not creating or restructuring technical docs.
• qa-test-planner: No behavior or verification surface is changing.

Public safety: No user-provided announcement text is included. Source JSON

database

Database performance triage

Investigate a dashboard query that became slow after adding a new filter.

The feature is already implemented, but the dashboard now feels delayed for larger public sample datasets.

Database / Performance > Query regression > Feature filter

Selected skills

• Primary: database-optimizer
• Supporting: systematic-debugging
• Supporting: qa-test-planner

Reason

Query planning is the main work, with causal debugging to isolate the regression and tests to preserve the fix.

Omitted on purpose

• frontend-design: The issue is reported as delayed data retrieval, not a layout or visual problem.
• code-documenter: Documentation should wait until the performance behavior is understood.

Public safety: Describes a generic dashboard query with no real table names. Source JSON

maintenance

Dependency update risk

Update a documentation site dependency and investigate one failing build step.

The dependency bump is small, but the build fails during static generation.

Maintenance / Dependencies > Static site build > Regression isolation

Selected skills

• Primary: dependency-updater
• Supporting: systematic-debugging
• Supporting: qa-test-planner

Reason

Dependency management owns the bump, debugging isolates the build regression, and QA defines the validation gate.

Omitted on purpose

• frontend-design: The task is dependency and build behavior, not visual redesign.
• code-documenter: Docs content should not change until the dependency issue is solved.

Public safety: No real package incident details are included. Source JSON

docs

Documentation source-map cleanup

Clean up stale documentation links after moving examples into a new folder.

Readers need source links that still point to the files behind the published docs.

Docs / Source map > Link integrity > Public docs

Selected skills

• Primary: code-documenter
• Supporting: spec-miner
• Supporting: qa-test-planner

Reason

Documentation owns the reader-facing shape; spec mining finds stale source assumptions, and QA defines link checks.

Omitted on purpose

• api-guidelines-skill: No API contract is being designed.
• frontend-design: The site layout is not the main defect.

Public safety: Uses generic documentation locations only. Source JSON

frontend

Frontend design refresh

Improve the first screen of a public documentation site so new developers understand the value faster.

The page already works, but the visual hierarchy, CTA order, and mobile scan path need refinement.

Frontend / Product surface > Public docs landing > Conversion polish

Selected skills

• Primary: frontend-design
• Supporting: playwright
• Supporting: qa-test-planner

Reason

Design owns the page hierarchy, Playwright verifies responsive rendering, and QA defines the public-page acceptance checks.

Omitted on purpose

• database-optimizer: The site page is static and has no query performance concern.
• api-guidelines-skill: No API contract is being changed.

Public safety: Public docs-site language is generic. Source JSON

release

Release readiness gate

Prepare a documentation-focused patch release after the branch is implemented.

The branch needs validation evidence, release notes, a clean commit boundary, and a tagged release.

Release / Final gate > Docs patch > Tag and publish

Selected skills

• Primary: finishing-a-development-branch
• Supporting: commit-work
• Supporting: qa-test-planner

Reason

Release readiness owns the gate, commit work keeps history reviewable, and QA preserves verification evidence.

Omitted on purpose

• database-optimizer: There is no database runtime change.
• frontend-design: The release process is the primary concern, not a new interface design.

Public safety: Release language is project-generic. Source JSON

security

Security-sensitive review

Review an authentication middleware change before it is merged.

The change touches request identity, token validation, and error handling around protected routes.

Security / Review > Auth middleware > Merge readiness

Selected skills

• Primary: codex-security:security-scan
• Supporting: codex-security:threat-model
• Supporting: receiving-code-review
• Supporting: qa-test-planner

Reason

Security review leads, threat modeling frames abuse cases, review handling tracks comments, and QA defines protected-route coverage.

Omitted on purpose

• frontend-design: The change is request security behavior, not interface design.
• database-optimizer: The task does not mention persistence performance.

Public safety: Uses generic authentication middleware context. Source JSON

simple-task

Simple command boundary

Show the current Git branch and latest commit summary.

The user only needs a direct local command result, not a multi-skill workflow.

Simple task > Direct command > No router expansion

Selected skills

• Primary: no-skill-needed

Reason

A simple status request should be answered directly without loading unrelated skills.

Omitted on purpose

• finishing-a-development-branch: The user did not ask to complete or release the branch.
• commit-work: No commit operation is requested.

Public safety: Boundary case uses generic Git status language. Source JSON

frontend

Vue browser regression

Fix a Vue settings form that loses selected values after a page refresh.

The bug is visible in the browser and needs a repeatable regression check before merge.

Frontend / Vue / UI > Browser regression > State persistence

Selected skills

• Primary: frontend-debugging-workflow
• Supporting: vue-composition-patterns-skill
• Supporting: playwright
• Supporting: qa-test-planner

Reason

Start where the rendered bug appears, inspect Vue state, capture a browser regression, and define acceptance coverage.

Omitted on purpose

• database-optimizer: The reported symptom is client state loss rather than slow data access.
• api-guidelines-skill: No backend contract change is currently in scope.

Public safety: Uses generic settings-form behavior. Source JSON

Submit a case

Use the route case issue template when you want to propose a new public-safe example. Keep real customer names, local paths, hostnames, credentials, and private repository details out of the submission.

Run these checks before opening a pull request:

python scripts/validate-route-cases.py route-cases
python scripts/build-route-gallery.py --check