routr

Plugin routr from marketplace routr in TeckTinkerere/ROUTR. Commands read from the repo's manifest — 11 days ago.

Skills (29)

• routr-agents

  Design multi-agent systems, agent loops, and eval harnesses. Use when: building agents, agent operating loop, research/self-correction loop, harness, memory, tools, context engineering, eval loop. Not for: a single AI SDK chat/RAG feature (→ routr-ai).

• routr-ai

  Build AI features with Vercel AI SDK (chat, agents, RAG, tools). Use when: chatbot, LLM, streaming, embeddings, tool calling, AI SDK, RAG. Not for: multi-agent architecture or eval harness (→ routr-agents); chat UI styling only (→ routr-frontend).

• routr-catalog

  Skill install registry and paths for all routr-* routers. Use when: a router says a child skill is missing, install commands, skill aliases, or bundle profiles.

• routr-database

  SQL, Postgres, Supabase schema and queries. Use when: migrations, RLS, slow queries, database design, Supabase. Not for: ORM or client-library setup (→ routr-integrate); wrong query results, cause unknown (→ routr-debug).

• routr-debug

  Find and fix bugs: reproduce → locate → fix. Use when: errors, crashes, failing or flaky tests, stack trace, 'why is this broken', root cause. Not for: known fix ready to commit (→ routr-ship); no bug, just understanding (→ routr-explore); failed video render (→ routr-video).

• routr-deploy

  Deploy to Vercel, preview environments, or app stores. Use when: deploy, go live, preview URL, production release, EAS submit, TestFlight; deploy-then-verify requests start here. Not for: writing the code (→ routr-ship); QA of an already-live site (→ routr-qa).

• routr-depth-debug

  Structured debugging when systematic-debugging is not installed. Use when: routr-debug bootstrap fails, child debug skill missing, or agent about to guess fixes.

• routr-depth-frontend

  Distinctive UI design when frontend-design is not installed. Use when: routr-frontend bootstrap fails, building UI without Anthropic frontend-design skill, or output looks like generic AI template.

• routr-depth-plan

  Brainstorm and PRD gate when brainstorming skill is not installed. Use when: routr-plan bootstrap fails, greenfield feature without Obra brainstorming, or user wants plan before code.

• routr-depth-security

  Minimum OWASP-style security audit process when semgrep and rules-auditor skills are not installed. Use when: routr-security bootstrap fails, child security skill missing, or agent about to ship a security opinion with no structured process behind it.

• routr-depth-ship

  Commit and PR discipline when caveman-commit is not installed. Use when: routr-ship needs commit message format, or user asks to ship without commit helper skill.

• routr-depth-test

  Test writing patterns when webapp-testing is not installed. Use when: routr-test bootstrap fails, adding tests without Anthropic webapp-testing skill.

• routr-explore

  Explain how the codebase works without changing code. Use when: 'how does X work', architecture, onboarding, where is this defined, walk me through. Not for: as-built specs or product drift (→ routr-spec); a specific bug (→ routr-debug); changing code (→ routr-ship).

• routr-frontend

  Build or redesign UI (pages, components, design system). Use when: new screen, landing page, layout, Tailwind, shadcn, 'make it look good', redesign, dashboard UI. Not for: animation (→ routr-motion); logic bugs (→ routr-debug); multi-screen feature with no spec (→ routr-plan).

• routr-integrate

  Integrate a third-party library using up-to-date docs. Use when: 'how do I use X', SDK setup, API syntax, version migration, configure library. Not for: internal codebase exploration (→ routr-explore); debugging a library error (→ routr-debug).

• routr-marketing

  Marketing copy, SEO audits, and growth content. Use when: landing copy, SEO, meta tags, ads, CRO, App Store listing, blog post, growth. Not for: building the landing page UI (→ routr-frontend).

• routr-mobile

  Build Expo or React Native apps (screens, navigation, native UI). Use when: mobile app, Expo, React Native, iOS, Android, native screen. Not for: web-only UI (→ routr-frontend); EAS build/submit, TestFlight or Play Store release (→ routr-deploy).

• routr-motion

  Add or polish animations (Framer Motion, scroll, transitions). Use when: animate, motion, micro-interactions on UI that already exists. Not for: building new pages or components (→ routr-frontend).

• routr-perf

  Performance: Core Web Vitals, bundle size, re-renders, slow APIs, N+1 queries, memory leaks, caching. Use when: slow page, high INP, big bundle, leak growing. Not for: wrong output (routr-debug), one query (routr-database), redesign (routr-frontend), animating (routr-motion).

• routr-plan

  Plan future work: brainstorm, PRD, stress-test ideas. Use when: new multi-screen feature, new spec or PRD, 'grill my plan', brainstorm, architecture decision. Not for: as-built reconciliation (→ routr-spec); implement now (→ routr-ship); UI layout (→ routr-frontend).

• routr-qa

  Test the app in a real browser (click, screenshot, smoke test). Use when: QA, E2E, 'open the site and check', smoke test of an already-deployed preview. Not for: deploying first (→ routr-deploy); writing test files (→ routr-test); fixing a bug you find (→ routr-debug).

• routr-refactor

  Improve code structure without changing behavior. Use when: refactor, tech debt, extract module, clean up code, restructure. Not for: fixing bugs or changing behavior (→ routr-debug / routr-ship).

• routr-review

  Review a PR or diff for bugs, style, and React best practices. Use when: code review, 'review my changes', before merge, PR feedback. Not for: writing the fix yourself (→ routr-ship).

• routr-router

  Pick the right ROUTR workflow when the task is unclear. Use when: not sure which skill, 'what approach', multiple tasks apply, 'help me with this', starting a new task, or user didn't name a specific router.

• routr-security

  Security pass on code, auth, and cloud rules. Use when: security audit, vulnerabilities, RLS, secrets in code, 'is this secure'. Not for: non-security bugs (→ routr-debug).

• routr-ship

  Make a small fix, verify it, and commit or open a PR. Use when: 'fix this', known change, patch, tests must pass, ready to ship, commit, open PR, merge this change. Not for: unknown root cause (→ routr-debug); building new UI (→ routr-frontend).

• routr-spec

  Reconcile existing products. Use when: compare current app vs original PRD, as-built spec, stale docs, product drift/evolution, incremental reconciliation. Not for: unbuilt features (→ routr-plan); code walkthroughs (→ routr-explore); implement fixes (→ routr-ship).

• routr-test

  Write and run tests (TDD, unit, E2E, Playwright). Use when: add tests, TDD, coverage, failing test suite, 'write tests for this'. Not for: browser smoke test (→ routr-qa); diagnosing why a test fails (→ routr-debug).

• routr-video

  Pick and run the right video workflow (launch, product marketing, data-driven, Remotion, HyperFrames). Use when: make a video, promo, explainer, /brag, render MP4, failed or blank render, motion graphic, captions, avatar video. Not for: in-app UI animation (→ routr-motion).

Similar plugins