[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C1VAESCMF1PWZTMFX45DKA":3,"skill-same:01M7C1VAESCMF1PWZTMFX45DKA":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7C1VAESCMF1PWZTMFX45DKA","dt-obs-frontends",null,"Real User Monitoring (RUM) on Dynatrace — web and mobile frontends. Core Web Vitals, user sessions, page performance, mobile crashes, frontend errors, and frontend-backend linking. Query via `user.events`, `user.sessions`, and `dt.frontend.*` metrics. Does NOT cover synthetic monitoring (HTTP\u002Fbrowser\u002Fnetwork checks) — that's a separate domain.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fdynatrace-dynatrace-for-ai\u002Fdt-obs-frontends\u002Fskills\u002Fdt-obs-frontends\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dt-obs-frontends\ndescription: Real User Monitoring (RUM) on Dynatrace — web and mobile frontends. Core Web Vitals, user sessions, page performance, mobile crashes, frontend errors, and frontend-backend linking. Query via `user.events`, `user.sessions`, and `dt.frontend.*` metrics. Does NOT cover synthetic monitoring (HTTP\u002Fbrowser\u002Fnetwork checks) — that's a separate domain.\nlicense: Apache-2.0\n---\n\n# Frontend Observability (RUM)\n\nMonitor web and mobile frontends using Real User Monitoring with DQL.\nTargets the **New RUM Experience only** — do not use classic RUM data.\n\n**Concepts and data model:** https:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fobserve\u002Fdigital-experience\u002Fnew-rum-experience\u002Fconcepts\n\n## Data Model\n\nThree data sources, each for a different question:\n\n| Source | Use for | Granularity |\n|--------|---------|-------------|\n| `timeseries dt.frontend.*` | Trends, dashboards, alerting | Aggregated metric |\n| `fetch user.events` | Root cause, individual page views \u002F requests \u002F clicks \u002F errors | Per-event |\n| `fetch user.sessions` | Bounce rate, session duration, session-level aggregates | Per-session |\n\n**Rule of thumb**: start with metrics for the shape of the problem, drill into events for the why. Use sessions when the question is about user journeys, not individual interactions.\n\nFull event model: https:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fsemantic-dictionary\u002Fmodel\u002Frum\u002Fuser-events\n\n**DQL language reference (functions, syntax, operators):** https:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fplatform\u002Fgrail\u002Fdynatrace-query-language\n\n**Key `dt.frontend.*` metrics** (all support dimensions: `frontend.name`, `device.type`, `geo.country.iso_code`, `browser.name`, `os.name`, `dt.rum.user_type`, `dt.smartscape.frontend`):\n\n- `dt.frontend.web.page.largest_contentful_paint` \u002F `dt.frontend.web.page.interaction_to_next_paint` \u002F `dt.frontend.web.page.cumulative_layout_shift` \u002F `dt.frontend.web.page.first_input_delay` — Core Web Vitals\n- `dt.frontend.web.navigation.time_to_first_byte` \u002F `dt.frontend.web.navigation.dom_interactive` \u002F `dt.frontend.web.navigation.load_event_end` — Navigation timing\n- `dt.frontend.error.count` — Error counts\n- `dt.frontend.request.count` \u002F `dt.frontend.request.duration` — Request volume and latency\n- `dt.frontend.user_action.count` \u002F `dt.frontend.user_action.duration` — User action volume and duration\n- `dt.frontend.session.active.estimated_count` \u002F `dt.frontend.user.active.estimated_count` — Active sessions and users (cardinality metrics; use `countDistinct()` aggregation)\n\n## Common Filters\n\n**All sources (`user.events` + `user.sessions`):**\n- `frontend.name` — frontend identifier (preferred for all filtering); array on `user.sessions` (session can span multiple frontends). `dt.smartscape.frontend` is the Smartscape entity reference — use it to access entity attributes such as tags or linked services, not for name-based filtering. Avoid querying Smartscape to resolve a name to an entity ID and then joining with `user.events` — always filter on `frontend.name` directly.\n- `dt.rum.user_type` — `real_user`, `synthetic`, `robot`\n- `dt.rum.application.type` — `web` or `mobile`\n- `dt.rum.session.id`, `dt.rum.instance.id`\n- `os.name`, `geo.country.iso_code`, `client.isp`\n- `client.ip` — client IP address *(sensitive field — hidden by default; see Field Permissions below)*\n\n**`user.events` — web only:**\n- `browser.name`, `browser.version`, `device.type`\n\n**`user.events` — mobile only:**\n- `device.model.identifier`, `device.manufacturer`, `app.short_version`\n\n**Common characteristic filters** (scope `user.events` to a specific event type — use as `| filter characteristics.has_X`):\n- `characteristics.has_page_summary` — page loads (web)\n- `characteristics.has_view_summary` — views (SPA + mobile screens)\n- `characteristics.has_navigation` — navigation events\n- `characteristics.has_user_action` — user actions\n- `characteristics.has_error` — all errors\n\nFull characteristics reference: [references\u002Fcharacteristics.md](references\u002Fcharacteristics.md)\n\n## Field Permissions\n\nSome fields are **sensitive** and belong to the `builtin-sensitive-user-events-and-sessions` fieldset. They are **hidden by default** on both `user.events` and `user.sessions` — users without access see `null`, and queries that filter or group by these fields silently return no results.\n\nSensitive fields used in this skill:\n\n- `client.ip` — client IP address\n- `user.identifier` — real user identity\n\nGrant access with the following policy statement:\n\n```\nALLOW storage:fieldsets:read WHERE storage:fieldset-name=\"builtin-sensitive-user-events-and-sessions\"\n```\n\nReference: [Field permissions](https:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fshortlink\u002Frum-on-grail-permissions#field-permissions)\n\n## Drill-Down Pattern\n\nMost investigations follow this layered approach regardless of the specific problem domain (errors, performance, background activity, etc.):\n\n**1. Identify the frontend**\n\nStart by grouping `by: {frontend.name}` to find which application is affected. Filter by `dt.rum.application.type` (`web` or `mobile`) if you need to split web from mobile analysis upfront.\n\n**2. Find the affected page or view**\n\nBoth fields are available on all events (not scoped to a specific characteristic):\n\n- `page.name` — the page URL normalised to a Dynatrace entity name; **web only**\n- `view.name` — the SPA route or mobile screen name; available on **web and mobile**\n\nBoth can be present on the same event. For web SPAs, `page.name` reflects the top-level document while `view.name` reflects the current route — grouping by `view.name` gives finer granularity. For mobile, use `view.name` only.\n\n**Additional narrowing dimensions**\n\n| Dimension | Field | Platform | When to use |\n|-----------|-------|----------|-------------|\n| Specific request \u002F endpoint | `url.domain`, `url.path` | web + mobile | Performance or error pattern on a specific API call |\n| Individual user session | `dt.rum.session.id` | web + mobile | Reproduce a specific user's journey; connects to session replay |\n| Device form factor | `device.type` | web only | Desktop vs mobile browser vs tablet pattern |\n| Browser compatibility | `browser.name`, `browser.version` | web only | Issue only on certain browsers |\n| App version | `app.short_version` | mobile only | Regression introduced in a specific app release |\n| Geography | `geo.country.iso_code` | web + mobile | Regional infrastructure or CDN issue |\n| Synthetic vs real traffic | `dt.rum.user_type` | web + mobile | Exclude synthetic monitors before user-facing analysis |\n\n## Workflows\n\nEach workflow maps to one or more references. Load the reference when you start the workflow, not upfront.\n\n| Workflow | Reference |\n|----------|-----------|\n| Event characteristics — types, filters, event_type derivation | [references\u002Fcharacteristics.md](references\u002Fcharacteristics.md) |\n| Web Vitals (LCP, FCP, FID, INP, CLS) | [references\u002Fweb-vitals.md](references\u002Fweb-vitals.md) |\n| Session, bounce, engagement analysis | [references\u002Fuser-sessions.md](references\u002Fuser-sessions.md) |\n| User actions — interaction lifecycle, completion reasons, timeouts | [references\u002Fuser-actions.md](references\u002Fuser-actions.md) |\n| Errors, exceptions, frontend-backend linking | [references\u002Ferror-tracking.md](references\u002Ferror-tracking.md) |\n| CSP violations — security policy enforcement and blocked resources | [references\u002Fcsp-violations.md](references\u002Fcsp-violations.md) |\n| Mobile app starts, crashes, ANR, native signals | [references\u002Fmobile-monitoring.md](references\u002Fmobile-monitoring.md) |\n| Request latency, long tasks, JS profiling, geo performance | [references\u002Fweb-performance-analysis.md](references\u002Fweb-performance-analysis.md) |\n| Visibility changes — tab switching, background time, engagement quality | [references\u002Fvisibility-changes.md](references\u002Fvisibility-changes.md) |\n| Slow page load — backend vs render vs network vs JS triage | [references\u002Fslow-page-load-playbook.md](references\u002Fslow-page-load-playbook.md) |\n| Diagnosing zero results, anomalies, ambiguous data | [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md) |\n\n## Performance Thresholds (quick reference)\n\n- **LCP**: Good \u003C 2.5 s | Poor > 4.0 s\n- **INP**: Good \u003C 200 ms | Poor > 500 ms\n- **CLS**: Good \u003C 0.1 | Poor > 0.25\n- **FCP**: Good \u003C 1.8 s | Poor > 3.0 s\n- **TTFB**: Good \u003C 800 ms | Poor > 1800 ms\n- **Mobile cold start**: Good \u003C 3 s | Poor > 5 s\n- **Mobile warm start**: Good \u003C 1.5 s | Poor > 2 s\n- **Mobile hot start**: Good \u003C 500 ms | Poor > 1 s\n- **Long tasks**: > 50 ms problematic, > 250 ms severe\n\n*Web vitals thresholds (LCP, INP, CLS, FCP, TTFB): https:\u002F\u002Fweb.dev\u002Farticles\u002Fvitals*\n\n## When to Use\n\nUse this skill for real-user web and mobile frontend telemetry — Core Web Vitals, sessions, clicks, errors, crashes, request latency from the browser\u002Fapp, and frontend-backend linking.\n\nUse a different skill for:\n\n- Synthetic monitors \u002F availability checks → `dt-obs-synthetic`\n- Backend services, traces, spans → `dt-obs-services`, `dt-obs-tracing`\n- Infrastructure, hosts → `dt-obs-hosts`\n- Logs → `dt-obs-logs`\n- Problems and incidents → `dt-obs-problems`\n","# Frontend Observability (RUM)\n\nMonitor web and mobile frontends using Real User Monitoring with DQL.\nTargets the **New RUM Experience only** — do not use classic RUM data.\n\n**Concepts and data model:** https:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fobserve\u002Fdigital-experience\u002Fnew-rum-experience\u002Fconcepts\n\n## Data Model\n\nThree data sources, each for a different question:\n\n| Source | Use for | Granularity |\n|--------|---------|-------------|\n| `timeseries dt.frontend.*` | Trends, dashboards, alerting | Aggregated metric |\n| `fetch user.events` | Root cause, individual page views \u002F requests \u002F clicks \u002F errors | Per-event |\n| `fetch user.sessions` | Bounce rate, session duration, session-level aggregates | Per-session |\n\n**Rule of thumb**: start with metrics for the shape of the problem, drill into events for the why. Use sessions when the question is about user journeys, not individual interactions.\n\nFull event model: https:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fsemantic-dictionary\u002Fmodel\u002Frum\u002Fuser-events\n\n**DQL language reference (functions, syntax, operators):** https:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fplatform\u002Fgrail\u002Fdynatrace-query-language\n\n**Key `dt.frontend.*` metrics** (all support dimensions: `frontend.name`, `device.type`, `geo.country.iso_code`, `browser.name`, `os.name`, `dt.rum.user_type`, `dt.smartscape.frontend`):\n\n- `dt.frontend.web.page.largest_contentful_paint` \u002F `dt.frontend.web.page.interaction_to_next_paint` \u002F `dt.frontend.web.page.cumulative_layout_shift` \u002F `dt.frontend.web.page.first_input_delay` — Core Web Vitals\n- `dt.frontend.web.navigation.time_to_first_byte` \u002F `dt.frontend.web.navigation.dom_interactive` \u002F `dt.frontend.web.navigation.load_event_end` — Navigation timing\n- `dt.frontend.error.count` — Error counts\n- `dt.frontend.request.count` \u002F `dt.frontend.request.duration` — Request volume and latency\n- `dt.frontend.user_action.count` \u002F `dt.frontend.user_action.duration` — User action volume and duration\n- `dt.frontend.session.active.estimated_count` \u002F `dt.frontend.user.active.estimated_count` — Active sessions and users (cardinality metrics; use `countDistinct()` aggregation)\n\n## Common Filters\n\n**All sources (`user.events` + `user.sessions`):**\n- `frontend.name` — frontend identifier (preferred for all filtering); array on `user.sessions` (session can span multiple frontends). `dt.smartscape.frontend` is the Smartscape entity reference — use it to access entity attributes such as tags or linked services, not for name-based filtering. Avoid querying Smartscape to resolve a name to an entity ID and then joining with `user.events` — always filter on `frontend.name` directly.\n- `dt.rum.user_type` — `real_user`, `synthetic`, `robot`\n- `dt.rum.application.type` — `web` or `mobile`\n- `dt.rum.session.id`, `dt.rum.instance.id`\n- `os.name`, `geo.country.iso_code`, `client.isp`\n- `client.ip` — client IP address *(sensitive field — hidden by default; see Field Permissions below)*\n\n**`user.events` — web only:**\n- `browser.name`, `browser.version`, `device.type`\n\n**`user.events` — mobile only:**\n- `device.model.identifier`, `device.manufacturer`, `app.short_version`\n\n**Common characteristic filters** (scope `user.events` to a specific event type — use as `| filter characteristics.has_X`):\n- `characteristics.has_page_summary` — page loads (web)\n- `characteristics.has_view_summary` — views (SPA + mobile screens)\n- `characteristics.has_navigation` — navigation events\n- `characteristics.has_user_action` — user actions\n- `characteristics.has_error` — all errors\n\nFull characteristics reference: [references\u002Fcharacteristics.md](references\u002Fcharacteristics.md)\n\n## Field Permissions\n\nSome fields are **sensitive** and belong to the `builtin-sensitive-user-events-and-sessions` fieldset. They are **hidden by default** on both `user.events` and `user.sessions` — users without access see `null`, and queries that filter or group by these fields silently return no results.\n\nSensitive fields used in this skill:\n\n- `client.ip` — client IP address\n- `user.identifier` — real user identity\n\nGrant access with the following policy statement:\n\n```\nALLOW storage:fieldsets:read WHERE storage:fieldset-name=\"builtin-sensitive-user-events-and-sessions\"\n```\n\nReference: [Field permissions](https:\u002F\u002Fdocs.dynatrace.com\u002Fdocs\u002Fshortlink\u002Frum-on-grail-permissions#field-permissions)\n\n## Drill-Down Pattern\n\nMost investigations follow this layered approach regardless of the specific problem domain (errors, performance, background activity, etc.):\n\n**1. Identify the frontend**\n\nStart by grouping `by: {frontend.name}` to find which application is affected. Filter by `dt.rum.application.type` (`web` or `mobile`) if you need to split web from mobile analysis upfront.\n\n**2. Find the affected page or view**\n\nBoth fields are available on all events (not scoped to a specific characteristic):\n\n- `page.name` — the page URL normalised to a Dynatrace entity name; **web only**\n- `view.name` — the SPA route or mobile screen name; available on **web and mobile**\n\nBoth can be present on the same event. For web SPAs, `page.name` reflects the top-level document while `view.name` reflects the current route — grouping by `view.name` gives finer granularity. For mobile, use `view.name` only.\n\n**Additional narrowing dimensions**\n\n| Dimension | Field | Platform | When to use |\n|-----------|-------|----------|-------------|\n| Specific request \u002F endpoint | `url.domain`, `url.path` | web + mobile | Performance or error pattern on a specific API call |\n| Individual user session | `dt.rum.session.id` | web + mobile | Reproduce a specific user's journey; connects to session replay |\n| Device form factor | `device.type` | web only | Desktop vs mobile browser vs tablet pattern |\n| Browser compatibility | `browser.name`, `browser.version` | web only | Issue only on certain browsers |\n| App version | `app.short_version` | mobile only | Regression introduced in a specific app release |\n| Geography | `geo.country.iso_code` | web + mobile | Regional infrastructure or CDN issue |\n| Synthetic vs real traffic | `dt.rum.user_type` | web + mobile | Exclude synthetic monitors before user-facing analysis |\n\n## Workflows\n\nEach workflow maps to one or more references. Load the reference when you start the workflow, not upfront.\n\n| Workflow | Reference |\n|----------|-----------|\n| Event characteristics — types, filters, event_type derivation | [references\u002Fcharacteristics.md](references\u002Fcharacteristics.md) |\n| Web Vitals (LCP, FCP, FID, INP, CLS) | [references\u002Fweb-vitals.md](references\u002Fweb-vitals.md) |\n| Session, bounce, engagement analysis | [references\u002Fuser-sessions.md](references\u002Fuser-sessions.md) |\n| User actions — interaction lifecycle, completion reasons, timeouts | [references\u002Fuser-actions.md](references\u002Fuser-actions.md) |\n| Errors, exceptions, frontend-backend linking | [references\u002Ferror-tracking.md](references\u002Ferror-tracking.md) |\n| CSP violations — security policy enforcement and blocked resources | [references\u002Fcsp-violations.md](references\u002Fcsp-violations.md) |\n| Mobile app starts, crashes, ANR, native signals | [references\u002Fmobile-monitoring.md](references\u002Fmobile-monitoring.md) |\n| Request latency, long tasks, JS profiling, geo performance | [references\u002Fweb-performance-analysis.md](references\u002Fweb-performance-analysis.md) |\n| Visibility changes — tab switching, background time, engagement quality | [references\u002Fvisibility-changes.md](references\u002Fvisibility-changes.md) |\n| Slow page load — backend vs render vs network vs JS triage | [references\u002Fslow-page-load-playbook.md](references\u002Fslow-page-load-playbook.md) |\n| Diagnosing zero results, anomalies, ambiguous data | [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md) |\n\n## Performance Thresholds (quick reference)\n\n- **LCP**: Good \u003C 2.5 s | Poor > 4.0 s\n- **INP**: Good \u003C 200 ms | Poor > 500 ms\n- **CLS**: Good \u003C 0.1 | Poor > 0.25\n- **FCP**: Good \u003C 1.8 s | Poor > 3.0 s\n- **TTFB**: Good \u003C 800 ms | Poor > 1800 ms\n- **Mobile cold start**: Good \u003C 3 s | Poor > 5 s\n- **Mobile warm start**: Good \u003C 1.5 s | Poor > 2 s\n- **Mobile hot start**: Good \u003C 500 ms | Poor > 1 s\n- **Long tasks**: > 50 ms problematic, > 250 ms severe\n\n*Web vitals thresholds (LCP, INP, CLS, FCP, TTFB): https:\u002F\u002Fweb.dev\u002Farticles\u002Fvitals*\n\n## When to Use\n\nUse this skill for real-user web and mobile frontend telemetry — Core Web Vitals, sessions, clicks, errors, crashes, request latency from the browser\u002Fapp, and frontend-backend linking.\n\nUse a different skill for:\n\n- Synthetic monitors \u002F availability checks → `dt-obs-synthetic`\n- Backend services, traces, spans → `dt-obs-services`, `dt-obs-tracing`\n- Infrastructure, hosts → `dt-obs-hosts`\n- Logs → `dt-obs-logs`\n- Problems and incidents → `dt-obs-problems`\n",{"name":5,"license":15,"description":7},"main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fdynatrace-dynatrace-for-ai\u002Fdt-obs-frontends\u002Fskills\u002Fdt-obs-frontends",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill dt-obs-frontends",{"tool":38,"command":39},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill dt-obs-frontends",{"tool":41,"command":42},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill dt-obs-frontends","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fdynatrace-dynatrace-for-ai\u002Fdt-obs-frontends\u002Fskills\u002Fdt-obs-frontends\u002FSKILL.md",true,[],[47,55,60,67,72,79],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":56,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":68,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":80,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":51,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]