router-first-use-guide
Explain the quickest reliable way to use the router hierarchy for a new task or new harness installation.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- router-first-use-guide
- tags
- [ "core", "routing", "onboarding", "v1" ]
- version
- 1.0.0
- description
- Explain the quickest reliable way to use the router hierarchy for a new task or new harness installation.
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档SOURCE.md419 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Purpose
Give first-time users a short, practical guide for starting with the router hierarchy without loading the entire suite.
Use when
- A person or harness is using the suite for the first time.
- You want a quick-start explanation of how the main router and category routers work together.
- The task needs a minimal starter workflow.
Required inputs
- The incoming task or role.
- Whether the category is already obvious.
- Whether reusable context already exists.
Safety/authority
- Default to draft-only work.
- Do not pretend the suite requires runtime setup or integrations.
- Keep the first-use flow minimal and easy to follow.
Workflow
- Start with
agency-routerif the task family is not obvious. - Let the main router resolve context with
context-loader. - Move to one category router only if category-specific clarification is still needed.
- Load 1–2 specialist skills after the router chooses the right lane.
- Use
skill-handoff-protocolif the work passes from one skill to the next.
Output format
- Best first step: ...
- Router path to use: ...
- Context prerequisite: ...
- Suggested starter stack: ...
- Next step prompt: ...
Quality checks
- The guide starts small.
- The router hierarchy is explained in practical terms.
- Context resolution is included.
- The result stays portable across harnesses.
Related skills
agency-router, context-loader, skill-selection-guide, skill-handoff-protocol
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.