[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMAGY6SFSA5PX67QJ73J9V":3,"skill-same:01M7EMAGY6SFSA5PX67QJ73J9V":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMAGY6SFSA5PX67QJ73J9V","app-performance-monitoring",null,"Application performance monitoring — transactions, profiling, and finding slow code — works with any APM platform.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-app-performance-monitoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: app-performance-monitoring\ndescription: Application performance monitoring — transactions, profiling, and finding slow code — works with any APM platform.\ncategory: sentry\n---\n\n## Overview\n\nAPM answers \"why is this slow?\" with data: which transactions are slow,\nwhich spans dominate, which database queries drag, and how performance\ntrends across releases. This skill covers instrumenting applications for\nperformance visibility and using that data to find and fix real bottlenecks —\nindependent of any specific APM vendor.\n\n## When to use\n\n- Finding why an endpoint or page load is slow\n- Setting up transaction tracing and span instrumentation\n- Identifying N+1 queries, slow serialization, or chatty service calls\n- Tracking performance across releases (did v2.1 get slower?)\n- Deciding what to instrument with custom spans vs automatic\n\n## Core concepts\n\n**Transactions and spans.** A transaction = one unit of work (an HTTP\nrequest, a background job, a page load). Spans = its decomposed steps\n(DB query, cache call, external API, template render). Automatic\ninstrumentation covers frameworks and drivers; custom spans mark your\nbusiness logic (\"compute recommendations\"). The trace waterfall shows\nexactly where time goes — optimize the longest bars first.\n\n**Measure percentiles, not averages.** Averages hide the pain: p50 tells\nyou the typical experience, p95\u002Fp99 the bad one users actually complain\nabout. Track latency as a distribution; alert on p99, optimize the spans\nthat dominate p99 traces.\n\n**Apdex \u002F satisfaction framing.** Translate latency into user experience:\nwhat fraction of requests are \"satisfying\" (\u003C T), \"tolerable\", \"frustrating\"?\nIt focuses optimization on what users feel and gives non-engineers an\nintuitive number.\n\n**Sampling strategy.** Tracing every request at high traffic is expensive\n(overhead + ingest cost). Sample: 100% of errors and slow outliers,\na percentage of normal traffic (enough for representative p99s), and\ndynamic sampling that keeps interesting traces. Head-based sampling is\nsimple; tail-based keeps the important ones — know which you have.\n\n**Correlate with releases.** Every deploy should mark the timeline; a p99\njump starting exactly at release X is a diagnosis, not a mystery. Tag\ntransactions with release version and compare distributions across\nreleases, not just point values.\n\n## Practical workflow\n\n1. **Instrument:** install the APM SDK\u002Ftracer, enable auto-instrumentation\n   for your framework\u002FDB\u002Fcache\u002FHTTP clients, and add custom spans around\n   key business operations.\n2. **Establish baselines:** per-endpoint p50\u002Fp95\u002Fp99, throughput, and error\n   rate over a representative week — you can't detect regressions without\n   \"normal\".\n3. **Find the bottleneck:** sort transactions by total time impact\n   (latency × volume — a slightly slow hot endpoint beats a very slow rare\n   one), open representative slow traces, and read the waterfall.\n4. **Fix the usual suspects:** N+1 queries (batch\u002Feager-load), missing\n   indexes, over-fetching (select only needed fields), synchronous calls\n   that could parallelize, uncached repeated computation, slow\n   serialization of huge payloads.\n5. **Verify with data:** compare p99 before\u002Fafter the fix on comparable\n   traffic; watch for regressions in the release comparison view.\n6. **Guard with alerts\u002FSLOs:** latency SLOs per critical endpoint with\n   burn-rate alerting; performance budgets in CI for key pages\u002Fendpoints\n   to catch regressions before deploy.\n\n## Common pitfalls\n\n- **Optimizing the average** — p50 looks fine while p99 users suffer;\n  always work from the tail.\n- **No custom spans** — auto-instrumentation shows \"DB: 800ms\" but not\n  which business operation caused 40 queries; span your domain logic.\n- **Tracing 100% of traffic** — overhead and cost explode; sample\n  deliberately.\n- **One slow trace = the truth** — outliers mislead; aggregate across\n  many traces before concluding.\n- **Ignoring the frontend** — backend p99 is great but users wait on\n  4MB of JavaScript; measure real user experience (RUM) alongside.\n- **Performance work without baselines** — \"we made it faster\" with no\n  before\u002Fafter numbers; measure first, then optimize, then verify.\n","## Overview\n\nAPM answers \"why is this slow?\" with data: which transactions are slow,\nwhich spans dominate, which database queries drag, and how performance\ntrends across releases. This skill covers instrumenting applications for\nperformance visibility and using that data to find and fix real bottlenecks —\nindependent of any specific APM vendor.\n\n## When to use\n\n- Finding why an endpoint or page load is slow\n- Setting up transaction tracing and span instrumentation\n- Identifying N+1 queries, slow serialization, or chatty service calls\n- Tracking performance across releases (did v2.1 get slower?)\n- Deciding what to instrument with custom spans vs automatic\n\n## Core concepts\n\n**Transactions and spans.** A transaction = one unit of work (an HTTP\nrequest, a background job, a page load). Spans = its decomposed steps\n(DB query, cache call, external API, template render). Automatic\ninstrumentation covers frameworks and drivers; custom spans mark your\nbusiness logic (\"compute recommendations\"). The trace waterfall shows\nexactly where time goes — optimize the longest bars first.\n\n**Measure percentiles, not averages.** Averages hide the pain: p50 tells\nyou the typical experience, p95\u002Fp99 the bad one users actually complain\nabout. Track latency as a distribution; alert on p99, optimize the spans\nthat dominate p99 traces.\n\n**Apdex \u002F satisfaction framing.** Translate latency into user experience:\nwhat fraction of requests are \"satisfying\" (\u003C T), \"tolerable\", \"frustrating\"?\nIt focuses optimization on what users feel and gives non-engineers an\nintuitive number.\n\n**Sampling strategy.** Tracing every request at high traffic is expensive\n(overhead + ingest cost). Sample: 100% of errors and slow outliers,\na percentage of normal traffic (enough for representative p99s), and\ndynamic sampling that keeps interesting traces. Head-based sampling is\nsimple; tail-based keeps the important ones — know which you have.\n\n**Correlate with releases.** Every deploy should mark the timeline; a p99\njump starting exactly at release X is a diagnosis, not a mystery. Tag\ntransactions with release version and compare distributions across\nreleases, not just point values.\n\n## Practical workflow\n\n1. **Instrument:** install the APM SDK\u002Ftracer, enable auto-instrumentation\n   for your framework\u002FDB\u002Fcache\u002FHTTP clients, and add custom spans around\n   key business operations.\n2. **Establish baselines:** per-endpoint p50\u002Fp95\u002Fp99, throughput, and error\n   rate over a representative week — you can't detect regressions without\n   \"normal\".\n3. **Find the bottleneck:** sort transactions by total time impact\n   (latency × volume — a slightly slow hot endpoint beats a very slow rare\n   one), open representative slow traces, and read the waterfall.\n4. **Fix the usual suspects:** N+1 queries (batch\u002Feager-load), missing\n   indexes, over-fetching (select only needed fields), synchronous calls\n   that could parallelize, uncached repeated computation, slow\n   serialization of huge payloads.\n5. **Verify with data:** compare p99 before\u002Fafter the fix on comparable\n   traffic; watch for regressions in the release comparison view.\n6. **Guard with alerts\u002FSLOs:** latency SLOs per critical endpoint with\n   burn-rate alerting; performance budgets in CI for key pages\u002Fendpoints\n   to catch regressions before deploy.\n\n## Common pitfalls\n\n- **Optimizing the average** — p50 looks fine while p99 users suffer;\n  always work from the tail.\n- **No custom spans** — auto-instrumentation shows \"DB: 800ms\" but not\n  which business operation caused 40 queries; span your domain logic.\n- **Tracing 100% of traffic** — overhead and cost explode; sample\n  deliberately.\n- **One slow trace = the truth** — outliers mislead; aggregate across\n  many traces before concluding.\n- **Ignoring the frontend** — backend p99 is great but users wait on\n  4MB of JavaScript; measure real user experience (RUM) alongside.\n- **Performance work without baselines** — \"we made it faster\" with no\n  before\u002Fafter numbers; measure first, then optimize, then verify.\n",{"name":5,"category":24,"description":7},"sentry","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-app-performance-monitoring",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill app-performance-monitoring",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill app-performance-monitoring",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill app-performance-monitoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-app-performance-monitoring\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]