Latency-Critical Systems Playbook
Engineering discipline for realtime systems with Muse: track p50/p95/p99, map the hot path, optimize in the right order, and verify with live readbacks. Never trade validation for speed.
- What
- Engineering discipline for realtime systems with Muse: track p50/p95/p99, map the hot path, optimize in the right order, and verify with live readbacks. Never trade validation for speed.
- Cost
- Free
- Needs
- Use "Latency-Critical Systems Playbook" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an engineering playbook that makes Muse treat latency as a set of separate, measurable quantities instead of one vague "fast". The skill splits the metrics: p50, p95, and p99 latency, throughput, freshness age, queue depth, cache hit rate, provider response time, browser render time, correctness under load, and failure/retry behavior. Then it maps the hot path from source event to user-visible state (source event, provider API, ingest worker, queue, cache, edge route, client stream, browser render) and measures each segment separately, so optimization effort lands where the time actually goes. The optimization order is strict: remove unnecessary round trips first, cache stable reads with freshness metadata, batch small calls, move compute closer to data or user, split hot and cold paths, apply backpressure before queues grow unbounded, use streaming only when it improves freshness, add canaries for stale data and degraded providers. Verification uses live readbacks against the deployed surface: HTTP timing and headers, provider freshness timestamps, queue and edge state, browser verification of actual UI freshness, logs around retries and degraded mode. Hard guardrails: never optimize latency by dropping required validation, never hide stale data behind fast cache hits, never claim millisecond behavior from client labels without measurement, never run live orders, destructive migrations, or customer-impacting deploys without an explicit approval gate, and keep secrets out of logs and benchmark artifacts. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: this is engineering-focused and does not authorize live trading or financial advice; for market-data or execution-adjacent paths, verify orderbook age, VWAP assumptions, provider status, and kill-switch behavior before calling the path ready. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Latency-Critical Systems Playbook" with your Muse. Prerequisites: none to install. Pure guidance; a latency-sensitive system to optimize helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/latency-critical-systems/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Help me cut p95 latency on [endpoint/pipeline]" or "Map the hot path for [user flow] and measure each segment." 3. Work through the metrics split and optimization order with Muse. Verify with live readbacks against the deployed surface. Tip: measure each hot-path segment separately before optimizing; most teams guess wrong about where the time goes. Safety: a skill is plain-text instructions; it runs nothing by itself. Never run live orders, destructive migrations, or customer-impacting deploys without an explicit approval gate.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.