[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DJHDP5NF2S8VCEYZ01AB5G":3,"skill-same:01M7DJHDP5NF2S8VCEYZ01AB5G":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7DJHDP5NF2S8VCEYZ01AB5G","latency-critical-systems",null,"Optimize and verify latency-sensitive systems — realtime dashboards, market data feeds, streaming agents, execution gateways, queues, and caches — by tracking p50\u002Fp95\u002Fp99 latency, freshness age, and queue depth, mapping hot paths, and running live readbacks. Use when p95 latency, throughput, or data freshness matters.","paooll\u002Fmobileappproj","paooll","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F167894352?v=4","01M7BJHFPFXNSYP2P9JVMD4KQ1","John Paul S. Penola","01M7DHFGHHAZ4ZVR21PG8ZGH5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpaooll\u002Fmobileappproj\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fskills\u002Flatency-critical-systems\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: latency-critical-systems\ndescription: Optimize and verify latency-sensitive systems — realtime dashboards, market data feeds, streaming agents, execution gateways, queues, and caches — by tracking p50\u002Fp95\u002Fp99 latency, freshness age, and queue depth, mapping hot paths, and running live readbacks. Use when p95 latency, throughput, or data freshness matters.\nlicense: MIT\nmetadata:\n  origin: ECC\ntools: Read, Write, Edit, Bash, Grep, Glob\n---\n\n# Latency Critical Systems\n\nUse this skill when the user cares about realtime behavior, hot paths, streaming\nfreshness, or execution speed. This includes HFT-like infrastructure, but the\nskill is engineering-focused. It does not authorize live trading or financial\nadvice.\n\n## Split The Metrics\n\nDo not collapse everything into \"fast.\" Track:\n\n- p50, p95, and p99 latency;\n- throughput;\n- freshness age;\n- queue depth;\n- cache hit rate;\n- provider\u002FAPI response time;\n- browser render time;\n- correctness under load;\n- failure and retry behavior.\n\n## Map The Hot Path\n\nWrite the path from user\u002Fevent to final visible state:\n\n```text\nsource event -> provider API -> ingest worker -> queue -> cache -> edge route\n-> client stream -> browser render -> user-visible state\n```\n\nThen measure each segment separately.\n\n## Optimization Order\n\n1. Remove unnecessary round trips.\n2. Cache stable reads with freshness metadata.\n3. Batch small calls and writes.\n4. Move compute closer to the data or the user.\n5. Split hot and cold paths.\n6. Apply backpressure before queues grow unbounded.\n7. Use streaming only when it improves freshness or user experience.\n8. Add canaries for stale data, degraded providers, and bad cache state.\n\n## Verification\n\nUse live readbacks when a deployed surface exists:\n\n- HTTP timing and response headers;\n- provider freshness timestamp;\n- queue or job state;\n- edge\u002Fcache state;\n- browser verification for actual UI freshness;\n- logs around retries and degraded mode.\n\nFor market-data or execution-adjacent paths, also verify orderbook age, VWAP\nassumptions, provider status, and kill-switch behavior before calling the path\nready.\n\n## Guardrails\n\n- Do not optimize latency by dropping required validation.\n- Do not hide stale data behind fast cache hits.\n- Do not claim millisecond behavior from client labels without measurement.\n- Do not run live orders, destructive migrations, or customer-impacting deploys\n  without an explicit approval gate.\n- Keep secrets and private payloads out of logs and benchmark artifacts.\n","# Latency Critical Systems\n\nUse this skill when the user cares about realtime behavior, hot paths, streaming\nfreshness, or execution speed. This includes HFT-like infrastructure, but the\nskill is engineering-focused. It does not authorize live trading or financial\nadvice.\n\n## Split The Metrics\n\nDo not collapse everything into \"fast.\" Track:\n\n- p50, p95, and p99 latency;\n- throughput;\n- freshness age;\n- queue depth;\n- cache hit rate;\n- provider\u002FAPI response time;\n- browser render time;\n- correctness under load;\n- failure and retry behavior.\n\n## Map The Hot Path\n\nWrite the path from user\u002Fevent to final visible state:\n\n```text\nsource event -> provider API -> ingest worker -> queue -> cache -> edge route\n-> client stream -> browser render -> user-visible state\n```\n\nThen measure each segment separately.\n\n## Optimization Order\n\n1. Remove unnecessary round trips.\n2. Cache stable reads with freshness metadata.\n3. Batch small calls and writes.\n4. Move compute closer to the data or the user.\n5. Split hot and cold paths.\n6. Apply backpressure before queues grow unbounded.\n7. Use streaming only when it improves freshness or user experience.\n8. Add canaries for stale data, degraded providers, and bad cache state.\n\n## Verification\n\nUse live readbacks when a deployed surface exists:\n\n- HTTP timing and response headers;\n- provider freshness timestamp;\n- queue or job state;\n- edge\u002Fcache state;\n- browser verification for actual UI freshness;\n- logs around retries and degraded mode.\n\nFor market-data or execution-adjacent paths, also verify orderbook age, VWAP\nassumptions, provider status, and kill-switch behavior before calling the path\nready.\n\n## Guardrails\n\n- Do not optimize latency by dropping required validation.\n- Do not hide stale data behind fast cache hits.\n- Do not claim millisecond behavior from client labels without measurement.\n- Do not run live orders, destructive migrations, or customer-impacting deploys\n  without an explicit approval gate.\n- Keep secrets and private payloads out of logs and benchmark artifacts.\n",{"name":5,"tools":24,"license":15,"metadata":25,"description":7},"Read, Write, Edit, Bash, Grep, Glob",{"origin":26},"ECC","main","d963cf076b6bdfdaecaeb6c8e2ccf70a211ce59d",".claude\u002Fskills\u002Fecc\u002Fskills\u002Flatency-critical-systems","https:\u002F\u002Fgithub.com\u002Fpaooll\u002Fmobileappproj","reprange-701b7.web.app","https:\u002F\u002Fgithub.com\u002Fpaooll","2026-10-31 21:59:30",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add paooll\u002Fmobileappproj --skill latency-critical-systems",{"tool":40,"command":41},"bunx","bunx skills add paooll\u002Fmobileappproj --skill latency-critical-systems",{"tool":43,"command":44},"pnpm","pnpm dlx skills add paooll\u002Fmobileappproj --skill latency-critical-systems","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpaooll\u002Fmobileappproj\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fskills\u002Flatency-critical-systems\u002FSKILL.md",true,[],[49,57,64,71,79,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":53,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7DKDB0VCC62VYFD3Q7Z64RB","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","https:\u002F\u002Fgithub.com\u002Fpaooll\u002Fmobileappproj\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpaooll\u002Fmobileappproj\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7DKB92VFAKB7QMD82S34WPN","ponytail","Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says \"ponytail\", \"be lazy\", \"lazy mode\", \"simplest solution\", \"minimal solution\", \"yagni\", \"do less\", or \"shortest path\", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).","https:\u002F\u002Fgithub.com\u002Fpaooll\u002Fmobileappproj\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7DK62TK747KVMMM3X3HGG1B","verification-loop","Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS\u002FFAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.","https:\u002F\u002Fgithub.com\u002Fpaooll\u002Fmobileappproj\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DJYKJPAM3KJPX2A63FF91X","returns-reverse-logistics","Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpaooll\u002Fmobileappproj\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fskills\u002Freturns-reverse-logistics\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7DJXGXWN9FGQ0Y7465PP9D0","recursive-decision-ledger","Run repeated rollouts (\"Prime Gauss\" style recursive prompting) while keeping an append-only decision ledger of trials, marks, coherence checks, and promotion gates, so recursive confidence never auto-approves live trading, deploy, or destructive actions. Use when the user asks for repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail.","https:\u002F\u002Fgithub.com\u002Fpaooll\u002Fmobileappproj\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fskills\u002Frecursive-decision-ledger\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7DJTYNVHN8YPDNPFS8AWZ56","quality-nonconformance","Quality control and non-conformance management for regulated manufacturing (FDA 21 CFR 820, IATF 16949, AS9100): NCR lifecycle and disposition, 5-Why\u002FIshikawa\u002Ffault-tree\u002F8D root cause analysis, CAPA systems, SPC interpretation, AQL sampling, and supplier quality audits. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.","https:\u002F\u002Fgithub.com\u002Fpaooll\u002Fmobileappproj\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fskills\u002Fquality-nonconformance\u002FSKILL.md",[],[]]