[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDBB9JJ7N54C6NVQPQV09H":3,"skill-same:01M6MDBB9JJ7N54C6NVQPQV09H":69},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6MDBB9JJ7N54C6NVQPQV09H","performance-audit",null,"Systematic performance investigation workflow. Use when performance regressions are suspected, before and after optimisation work, or as a pre-release gate for performance-critical features. Produces a baseline, identifies the real bottleneck, and validates improvement with hard numbers.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fperformance-audit\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"performance audit","audit","performance","use","when","features","improvement","for","with","critical","as","systematic","gate","bottleneck","work","before and after","investigation","baseline","release","performance investigation","workflow","2026-11-10 10:12:30",false,"---\nname: performance-audit\ndescription: Systematic performance investigation workflow. Use when performance regressions are suspected, before and after optimisation work, or as a pre-release gate for performance-critical features. Produces a baseline, identifies the real bottleneck, and validates improvement with hard numbers.\n---\n\n# Performance Audit\n\n## The Law\n\n```\nA PERFORMANCE CLAIM WITHOUT NUMBERS IS AN OPINION.\n\"I think it's faster\" is not a result.\n\"p95 latency dropped from 480ms to 42ms on a 1000-item dataset\" is a result.\n```\n\n## When to Use\n\n- Before any optimisation work (establish baseline first)\n- When a performance regression is reported\n- As a pre-release gate on performance-critical features\n- After an optimisation to validate the improvement\n\n## Audit Workflow\n\n### Step 1: Define the Performance Goal\n\nBefore measuring anything, define what \"good\" looks like:\n\n| Category | Example target |\n|----------|---------------|\n| API latency | p95 \u003C 200ms at 100 concurrent users |\n| Page load | First Contentful Paint \u003C 1.5s on 4G |\n| Mobile frame rate | 60fps during scroll, 0 jank frames |\n| Build time | Full build \u003C 3 minutes |\n| Memory | Peak heap \u003C 512MB under load |\n| Bundle size | JS bundle \u003C 250KB gzipped |\n\nIf no target exists, the first audit establishes the baseline that becomes the target.\n\n### Step 2: Measure the Baseline\n\nRun the benchmark **before any changes**. Record:\n- Tool used and exact command\n- Input size and conditions\n- Raw numbers (min, p50, p95, p99, max)\n- System state (CPU, memory, concurrent users)\n\n```markdown\n## Baseline — YYYY-MM-DD\n\n**Feature:** User search endpoint\n**Tool:** k6\n**Command:** `k6 run --vus 50 --duration 60s scripts\u002Fsearch-load-test.js`\n**Input:** 1000-user dataset, query=\"test\"\n\n| Metric | Value |\n|--------|-------|\n| p50 | 45ms |\n| p95 | 380ms |\n| p99 | 720ms |\n| Error rate | 0.2% |\n| Throughput | 210 req\u002Fs |\n```\n\n### Step 3: Profile — Find the Real Bottleneck\n\nUse the appropriate tool for the stack. Read the output. Don't guess.\n\n**Web APIs**\n```bash\n# Node.js — CPU profile\nnode --prof app.js\n# Run load test, then:\nnode --prof-process isolate-*.log > profile.txt\n\n# Python — flame graph\npip install py-spy\npy-spy record -o profile.svg --pid $(pgrep -f \"python app.py\")\n\n# Go — pprof\ngo tool pprof http:\u002F\u002Flocalhost:6060\u002Fdebug\u002Fpprof\u002Fprofile?seconds=30\n\n# Database — slow query log\nEXPLAIN (ANALYZE, BUFFERS, FORMAT JSON) SELECT ...;\n```\n\n**Frontend**\n```bash\n# Bundle analysis\nnpx webpack-bundle-analyzer stats.json\nnpx source-map-explorer dist\u002Fmain.js\n\n# Runtime: Chrome DevTools → Performance tab\n# Record interaction → identify long tasks (>50ms)\n\n# Lighthouse CI\nnpx lhci autorun\n```\n\n**Mobile**\n- Android: Android Studio → Profiler → CPU\u002FMemory\u002FNetwork\n- iOS: Xcode → Instruments → Time Profiler\n- Flutter: `flutter run --profile` → DevTools → Performance overlay\n\n### Step 4: Report the Finding\n\nState the bottleneck with evidence, not assumption:\n\n```markdown\n## Bottleneck Found\n\n**Location:** `UserSearchService.search()` — lines 45-67\n**Evidence:** pprof shows 78% of CPU time in this function\n**Root cause:** For each of 50 search results, a separate `getUserById()` DB call is made (N+1 query)\n**Impact:** 47 sequential DB calls per request × ~8ms each = ~376ms per request\n```\n\n### Step 5: Apply One Change\n\nSingle change. Document hypothesis and expected impact before applying:\n\n```markdown\n## Change Applied\n\n**Hypothesis:** Replacing per-item DB lookups with a single JOIN will eliminate 46 of the 47 DB calls\n**Change:** `UserSearchService.search()` — replace loop + `getUserById()` with `getUsersByIds(ids)` JOIN\n**Files modified:** `src\u002Fservices\u002FUserSearchService.ts`\n**Expected impact:** p95 latency from 380ms to \u003C 50ms\n```\n\n### Step 6: Re-Measure and Compare\n\nRun the **exact same benchmark** from Step 2.\n\n```markdown\n## After Optimisation — YYYY-MM-DD\n\n**Change:** N+1 query replaced with single JOIN\n\n| Metric | Before | After | Delta |\n|--------|--------|-------|-------|\n| p50 | 45ms | 12ms | -73% |\n| p95 | 380ms | 38ms | -90% |\n| p99 | 720ms | 65ms | -91% |\n| Error rate | 0.2% | 0.1% | -50% |\n| Throughput | 210 req\u002Fs | 890 req\u002Fs | +324% |\n\n**Verdict:** IMPROVEMENT CONFIRMED\n**Root cause validated:** DB calls per request: 47 → 1\n**No regression:** error rate stable, memory unchanged\n```\n\n### Step 7: Verdict\n\n| Verdict | Criteria |\n|---------|---------|\n| **IMPROVEMENT CONFIRMED** | Measurable improvement on target metric, no regression elsewhere |\n| **INCONCLUSIVE** | No measurable change — hypothesis was wrong; identify next bottleneck |\n| **REGRESSION** | Change made things worse — revert immediately, re-diagnose |\n| **GOAL MET** | Target from Step 1 achieved — further optimisation not required |\n\n## Performance Budget (Pre-Release Gate)\n\nFor release-critical features, define performance budgets in `docs\u002Fperformance-budgets.md`:\n\n```yaml\napi_latency:\n  endpoint: POST \u002Fapi\u002Fsearch\n  p95_ms: 200\n  measured_with: k6\n  load: 100 concurrent users\n\nbundle_size:\n  entry: main.js\n  max_gzip_kb: 250\n  measured_with: webpack-bundle-analyzer\n\nmobile_fps:\n  screen: SearchScreen\n  min_fps: 60\n  tool: Android Profiler\n```\n\nCI fails if any budget is exceeded. Performance is a feature — it regresses like any other feature.\n","# Performance Audit\n\n## The Law\n\n```\nA PERFORMANCE CLAIM WITHOUT NUMBERS IS AN OPINION.\n\"I think it's faster\" is not a result.\n\"p95 latency dropped from 480ms to 42ms on a 1000-item dataset\" is a result.\n```\n\n## When to Use\n\n- Before any optimisation work (establish baseline first)\n- When a performance regression is reported\n- As a pre-release gate on performance-critical features\n- After an optimisation to validate the improvement\n\n## Audit Workflow\n\n### Step 1: Define the Performance Goal\n\nBefore measuring anything, define what \"good\" looks like:\n\n| Category | Example target |\n|----------|---------------|\n| API latency | p95 \u003C 200ms at 100 concurrent users |\n| Page load | First Contentful Paint \u003C 1.5s on 4G |\n| Mobile frame rate | 60fps during scroll, 0 jank frames |\n| Build time | Full build \u003C 3 minutes |\n| Memory | Peak heap \u003C 512MB under load |\n| Bundle size | JS bundle \u003C 250KB gzipped |\n\nIf no target exists, the first audit establishes the baseline that becomes the target.\n\n### Step 2: Measure the Baseline\n\nRun the benchmark **before any changes**. Record:\n- Tool used and exact command\n- Input size and conditions\n- Raw numbers (min, p50, p95, p99, max)\n- System state (CPU, memory, concurrent users)\n\n```markdown\n## Baseline — YYYY-MM-DD\n\n**Feature:** User search endpoint\n**Tool:** k6\n**Command:** `k6 run --vus 50 --duration 60s scripts\u002Fsearch-load-test.js`\n**Input:** 1000-user dataset, query=\"test\"\n\n| Metric | Value |\n|--------|-------|\n| p50 | 45ms |\n| p95 | 380ms |\n| p99 | 720ms |\n| Error rate | 0.2% |\n| Throughput | 210 req\u002Fs |\n```\n\n### Step 3: Profile — Find the Real Bottleneck\n\nUse the appropriate tool for the stack. Read the output. Don't guess.\n\n**Web APIs**\n```bash\n# Node.js — CPU profile\nnode --prof app.js\n# Run load test, then:\nnode --prof-process isolate-*.log > profile.txt\n\n# Python — flame graph\npip install py-spy\npy-spy record -o profile.svg --pid $(pgrep -f \"python app.py\")\n\n# Go — pprof\ngo tool pprof http:\u002F\u002Flocalhost:6060\u002Fdebug\u002Fpprof\u002Fprofile?seconds=30\n\n# Database — slow query log\nEXPLAIN (ANALYZE, BUFFERS, FORMAT JSON) SELECT ...;\n```\n\n**Frontend**\n```bash\n# Bundle analysis\nnpx webpack-bundle-analyzer stats.json\nnpx source-map-explorer dist\u002Fmain.js\n\n# Runtime: Chrome DevTools → Performance tab\n# Record interaction → identify long tasks (>50ms)\n\n# Lighthouse CI\nnpx lhci autorun\n```\n\n**Mobile**\n- Android: Android Studio → Profiler → CPU\u002FMemory\u002FNetwork\n- iOS: Xcode → Instruments → Time Profiler\n- Flutter: `flutter run --profile` → DevTools → Performance overlay\n\n### Step 4: Report the Finding\n\nState the bottleneck with evidence, not assumption:\n\n```markdown\n## Bottleneck Found\n\n**Location:** `UserSearchService.search()` — lines 45-67\n**Evidence:** pprof shows 78% of CPU time in this function\n**Root cause:** For each of 50 search results, a separate `getUserById()` DB call is made (N+1 query)\n**Impact:** 47 sequential DB calls per request × ~8ms each = ~376ms per request\n```\n\n### Step 5: Apply One Change\n\nSingle change. Document hypothesis and expected impact before applying:\n\n```markdown\n## Change Applied\n\n**Hypothesis:** Replacing per-item DB lookups with a single JOIN will eliminate 46 of the 47 DB calls\n**Change:** `UserSearchService.search()` — replace loop + `getUserById()` with `getUsersByIds(ids)` JOIN\n**Files modified:** `src\u002Fservices\u002FUserSearchService.ts`\n**Expected impact:** p95 latency from 380ms to \u003C 50ms\n```\n\n### Step 6: Re-Measure and Compare\n\nRun the **exact same benchmark** from Step 2.\n\n```markdown\n## After Optimisation — YYYY-MM-DD\n\n**Change:** N+1 query replaced with single JOIN\n\n| Metric | Before | After | Delta |\n|--------|--------|-------|-------|\n| p50 | 45ms | 12ms | -73% |\n| p95 | 380ms | 38ms | -90% |\n| p99 | 720ms | 65ms | -91% |\n| Error rate | 0.2% | 0.1% | -50% |\n| Throughput | 210 req\u002Fs | 890 req\u002Fs | +324% |\n\n**Verdict:** IMPROVEMENT CONFIRMED\n**Root cause validated:** DB calls per request: 47 → 1\n**No regression:** error rate stable, memory unchanged\n```\n\n### Step 7: Verdict\n\n| Verdict | Criteria |\n|---------|---------|\n| **IMPROVEMENT CONFIRMED** | Measurable improvement on target metric, no regression elsewhere |\n| **INCONCLUSIVE** | No measurable change — hypothesis was wrong; identify next bottleneck |\n| **REGRESSION** | Change made things worse — revert immediately, re-diagnose |\n| **GOAL MET** | Target from Step 1 achieved — further optimisation not required |\n\n## Performance Budget (Pre-Release Gate)\n\nFor release-critical features, define performance budgets in `docs\u002Fperformance-budgets.md`:\n\n```yaml\napi_latency:\n  endpoint: POST \u002Fapi\u002Fsearch\n  p95_ms: 200\n  measured_with: k6\n  load: 100 concurrent users\n\nbundle_size:\n  entry: main.js\n  max_gzip_kb: 250\n  measured_with: webpack-bundle-analyzer\n\nmobile_fps:\n  screen: SearchScreen\n  min_fps: 60\n  tool: Android Profiler\n```\n\nCI fails if any budget is exceeded. Performance is a feature — it regresses like any other feature.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fperformance-audit",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill performance-audit",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill performance-audit",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill performance-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fperformance-audit\u002FSKILL.md",true,[],[70,80,88,96,104,112],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":79},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":79},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":79},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":79},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":79},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]