[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74AGQN1DF6D67RE682BVW5Z":3,"skill-same:01M74AGQN1DF6D67RE682BVW5Z":56},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M74AGQN1DF6D67RE682BVW5Z","cache-bust-deploy-validation",null,"After a production deploy of a CDN-fronted site, force cache-bust on every validation request and inspect Age\u002Fcache-status headers — the CDN can serve a stale 200 with old content for hours, hiding a broken deploy. Use whenever validating a freshly-deployed web app, debugging \"deploy completed but the live site shows the old version\", or building a post-deploy smoke test.","CarlosCaPe\u002Foctorato","CarlosCaPe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F39838249?v=4","01M72WXX4ZRR8MBH1EP1QND2FQ","dataqbs","01M72WXX5NA7YCKRSJ54GW1GQ8",18,"MIT","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fcache-bust-deploy-validation\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: cache-bust-deploy-validation\ndescription: After a production deploy of a CDN-fronted site, force cache-bust on every validation request and inspect Age\u002Fcache-status headers — the CDN can serve a stale 200 with old content for hours, hiding a broken deploy. Use whenever validating a freshly-deployed web app, debugging \"deploy completed but the live site shows the old version\", or building a post-deploy smoke test.\nmetadata:\n  type: skill\n---\n\n# Cache-Bust Deploy Validation\n\n## When to use\n\nTrigger this skill any time you are validating that a fresh deploy went live on a CDN-fronted host (Cloudflare Pages, Vercel, Netlify, Fastly, CloudFront, AWS S3+CF).\n\nConcrete triggers:\n- \"Deploy completed but the live site shows the old version\"\n- \"Validating a deploy \u002F verifying a feature shipped\"\n- \"Why is the new \u003Cfeature> not visible?\"\n- Writing a post-deploy smoke test\n\n## The anti-pattern\n\n```bash\n# WRONG — the CDN happily returns 200 with cached old content\ncurl https:\u002F\u002Fprod.example.com\u002Fpage   # looks fine, but is stale\n```\n\nA deploy can be **broken at the worker but green at the edge** for hours because the edge cache holds the last successful response. Validation that doesn't bypass the cache will report \"all good\" while real users are about to hit 404 \u002F wrong content as soon as the cache expires.\n\n## The correct validation loop\n\n```bash\n# 1. Cache-bust on EVERY validation request\ncurl -sS \"https:\u002F\u002Fprod.example.com\u002Fpage?_=$(date +%s)\" -o \u002Ftmp\u002Ffresh.html\ngrep -c \"\u003Cfeature-marker>\" \u002Ftmp\u002Ffresh.html   # must be > 0\n\n# 2. Inspect cache headers — Age > 60s on a path you just redeployed = stale\ncurl -sS -I \"https:\u002F\u002Fprod.example.com\u002Fpage\" | grep -iE 'cache|age|x-vercel|cf-'\n\n# 3. Test the deploy preview URL too (each platform exposes one) — it\n#    skips the production CDN cache layer entirely.\n#    CF Pages:  https:\u002F\u002F\u003Cdeploy-hash>.\u003Cproject>.pages.dev\u002F\u003Cpath>\n#    Vercel:    URL from `vercel ls` \u002F deployment dashboard\n#    Netlify:   permalink under each deploy in the dashboard\n```\n\n## Headers that signal cache masking\n\n| Header | Meaning |\n|---|---|\n| `Age: \u003CN>` (N > 60) | Response is N seconds old — served from cache |\n| `cf-cache-status: HIT` | Cloudflare served from edge cache |\n| `cf-cache-status: DYNAMIC` | NOT cached at edge (the SSR case you usually want) |\n| `cf-cache-status: BYPASS` | CF skipped cache by config (also OK) |\n| `x-vercel-cache: HIT` | Vercel edge cache hit |\n| `x-cache: Hit from cloudfront` | CloudFront hit |\n| `cache-control: no-cache, max-age=0` combined with `Age: \u003Clarge>` | Origin says don't cache, but something cached it anyway — investigate |\n\n## Why it matters\n\nCDN edge caches routinely outlive deploys:\n- HTML responses get cached despite `Cache-Control: no-cache` (some CDNs respect only `private` or `no-store`)\n- Workers\u002FPages keep the old version until purge propagates (~30 sec to several min)\n- Tiered caches mean different POPs may serve different versions for hours\n- A redirect that points to a now-404 URL can be served from cache long after the breaking commit shipped\n\nSo **\"the site loads correctly\"** is not proof **\"the deploy worked\"** — it might just be proof that the cache hasn't expired.\n\n## How to purge\n\nUse when you need users to see the new version immediately, not whenever the TTL expires.\n\n| Platform | How |\n|---|---|\n| Cloudflare | Dashboard → Caching → Configuration → Purge by URL. API: `POST \u002Fzones\u002F\u003Czone-id>\u002Fpurge_cache` with `{\"files\":[\"https:\u002F\u002Fprod\u002Fpath\"]}` |\n| Vercel | `vercel rollback \u003Cprev>` then redeploy, or trigger a force-redeploy commit. Vercel auto-invalidates on deploy but a stuck edge sometimes needs this. |\n| Netlify | Site → Deploys → \"Clear cache and deploy site\" |\n| Fastly | `curl -X POST -H \"Fastly-Key:$KEY\" https:\u002F\u002Fapi.fastly.com\u002Fservice\u002F\u003Cservice-id>\u002Fpurge_all` |\n| CloudFront | `aws cloudfront create-invalidation --distribution-id $ID --paths '\u002Fpath'` |\n\n## Validation script template (drop into CI smoke tests)\n\n```bash\nURL=\"$1\"\nMARKER=\"$2\"   # e.g. unique string only present in the new version\nfresh=$(curl -sS \"${URL}?_=$(date +%s)\")\nhits=$(echo \"$fresh\" | grep -c \"$MARKER\")\nif [ \"$hits\" -lt 1 ]; then\n  echo \"::error::Marker '$MARKER' not present in $URL — deploy may be stale or broken\"\n  curl -sS -I \"$URL\" | grep -iE 'cache|age' >&2\n  exit 1\nfi\necho \"✓ Marker present, deploy live\"\n```\n\n## Anti-pattern to flag in code review\n\nA `_redirects` \u002F route rule that redirects path A → path B without first verifying that the receiving framework's worker actually has a handler at path B. Common on Astro \u002F Next.js \u002F Remix hybrid SSR: the framework registers routes WITHOUT a trailing slash by default; a CDN-level redirect forcing the trailing slash sends users to a path the worker doesn't serve, producing 404. The edge cache can mask this for hours before users complain.\n\n## Lessons Learned\n\n- An add-only `_redirects` line meant to fix a perceived SEO conflict broke a section of a hybrid-SSR site for ~5h before being caught. The 5h delay was entirely due to edge cache: the production URL kept returning `200` with `Age: ~18000s` (cached pre-regression), so manual checks said \"looks fine\" while the actual worker was 404-ing. Lesson: every deploy validation MUST cache-bust, and a 200 with a large `Age` is a red flag, not a green one.\n","# Cache-Bust Deploy Validation\n\n## When to use\n\nTrigger this skill any time you are validating that a fresh deploy went live on a CDN-fronted host (Cloudflare Pages, Vercel, Netlify, Fastly, CloudFront, AWS S3+CF).\n\nConcrete triggers:\n- \"Deploy completed but the live site shows the old version\"\n- \"Validating a deploy \u002F verifying a feature shipped\"\n- \"Why is the new \u003Cfeature> not visible?\"\n- Writing a post-deploy smoke test\n\n## The anti-pattern\n\n```bash\n# WRONG — the CDN happily returns 200 with cached old content\ncurl https:\u002F\u002Fprod.example.com\u002Fpage   # looks fine, but is stale\n```\n\nA deploy can be **broken at the worker but green at the edge** for hours because the edge cache holds the last successful response. Validation that doesn't bypass the cache will report \"all good\" while real users are about to hit 404 \u002F wrong content as soon as the cache expires.\n\n## The correct validation loop\n\n```bash\n# 1. Cache-bust on EVERY validation request\ncurl -sS \"https:\u002F\u002Fprod.example.com\u002Fpage?_=$(date +%s)\" -o \u002Ftmp\u002Ffresh.html\ngrep -c \"\u003Cfeature-marker>\" \u002Ftmp\u002Ffresh.html   # must be > 0\n\n# 2. Inspect cache headers — Age > 60s on a path you just redeployed = stale\ncurl -sS -I \"https:\u002F\u002Fprod.example.com\u002Fpage\" | grep -iE 'cache|age|x-vercel|cf-'\n\n# 3. Test the deploy preview URL too (each platform exposes one) — it\n#    skips the production CDN cache layer entirely.\n#    CF Pages:  https:\u002F\u002F\u003Cdeploy-hash>.\u003Cproject>.pages.dev\u002F\u003Cpath>\n#    Vercel:    URL from `vercel ls` \u002F deployment dashboard\n#    Netlify:   permalink under each deploy in the dashboard\n```\n\n## Headers that signal cache masking\n\n| Header | Meaning |\n|---|---|\n| `Age: \u003CN>` (N > 60) | Response is N seconds old — served from cache |\n| `cf-cache-status: HIT` | Cloudflare served from edge cache |\n| `cf-cache-status: DYNAMIC` | NOT cached at edge (the SSR case you usually want) |\n| `cf-cache-status: BYPASS` | CF skipped cache by config (also OK) |\n| `x-vercel-cache: HIT` | Vercel edge cache hit |\n| `x-cache: Hit from cloudfront` | CloudFront hit |\n| `cache-control: no-cache, max-age=0` combined with `Age: \u003Clarge>` | Origin says don't cache, but something cached it anyway — investigate |\n\n## Why it matters\n\nCDN edge caches routinely outlive deploys:\n- HTML responses get cached despite `Cache-Control: no-cache` (some CDNs respect only `private` or `no-store`)\n- Workers\u002FPages keep the old version until purge propagates (~30 sec to several min)\n- Tiered caches mean different POPs may serve different versions for hours\n- A redirect that points to a now-404 URL can be served from cache long after the breaking commit shipped\n\nSo **\"the site loads correctly\"** is not proof **\"the deploy worked\"** — it might just be proof that the cache hasn't expired.\n\n## How to purge\n\nUse when you need users to see the new version immediately, not whenever the TTL expires.\n\n| Platform | How |\n|---|---|\n| Cloudflare | Dashboard → Caching → Configuration → Purge by URL. API: `POST \u002Fzones\u002F\u003Czone-id>\u002Fpurge_cache` with `{\"files\":[\"https:\u002F\u002Fprod\u002Fpath\"]}` |\n| Vercel | `vercel rollback \u003Cprev>` then redeploy, or trigger a force-redeploy commit. Vercel auto-invalidates on deploy but a stuck edge sometimes needs this. |\n| Netlify | Site → Deploys → \"Clear cache and deploy site\" |\n| Fastly | `curl -X POST -H \"Fastly-Key:$KEY\" https:\u002F\u002Fapi.fastly.com\u002Fservice\u002F\u003Cservice-id>\u002Fpurge_all` |\n| CloudFront | `aws cloudfront create-invalidation --distribution-id $ID --paths '\u002Fpath'` |\n\n## Validation script template (drop into CI smoke tests)\n\n```bash\nURL=\"$1\"\nMARKER=\"$2\"   # e.g. unique string only present in the new version\nfresh=$(curl -sS \"${URL}?_=$(date +%s)\")\nhits=$(echo \"$fresh\" | grep -c \"$MARKER\")\nif [ \"$hits\" -lt 1 ]; then\n  echo \"::error::Marker '$MARKER' not present in $URL — deploy may be stale or broken\"\n  curl -sS -I \"$URL\" | grep -iE 'cache|age' >&2\n  exit 1\nfi\necho \"✓ Marker present, deploy live\"\n```\n\n## Anti-pattern to flag in code review\n\nA `_redirects` \u002F route rule that redirects path A → path B without first verifying that the receiving framework's worker actually has a handler at path B. Common on Astro \u002F Next.js \u002F Remix hybrid SSR: the framework registers routes WITHOUT a trailing slash by default; a CDN-level redirect forcing the trailing slash sends users to a path the worker doesn't serve, producing 404. The edge cache can mask this for hours before users complain.\n\n## Lessons Learned\n\n- An add-only `_redirects` line meant to fix a perceived SEO conflict broke a section of a hybrid-SSR site for ~5h before being caught. The 5h delay was entirely due to edge cache: the production URL kept returning `200` with `Age: ~18000s` (cached pre-regression), so manual checks said \"looks fine\" while the actual worker was 404-ing. Lesson: every deploy validation MUST cache-bust, and a 200 with a large `Age` is a red flag, not a green one.\n",{"name":5,"metadata":24,"description":7},{"type":25},"skill","master","b4414608cd5a3f87d1525b518f1c6add8363540d","skills\u002Fcache-bust-deploy-validation",6,"https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato","https:\u002F\u002Fwww.dataqbs.com\u002Foctorato","https:\u002F\u002Fgithub.com\u002FCarlosCaPe","www.dataqbs.com"," AI-powered data engineering\r\n& consulting\r\n\r\nWe build data platforms that turn complexity into clarity — from cloud architecture and ETL pipelines to AI-driven","2026-11-14 00:21:00",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add CarlosCaPe\u002Foctorato --skill cache-bust-deploy-validation",{"tool":42,"command":43},"bunx","bunx skills add CarlosCaPe\u002Foctorato --skill cache-bust-deploy-validation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add CarlosCaPe\u002Foctorato --skill cache-bust-deploy-validation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fcache-bust-deploy-validation\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"skill.json","REFERENCE","参考文档",505,"https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fcache-bust-deploy-validation\u002Fskill.json",[57,66,74,81,89,97],{"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":61,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74EVAA4A4B4AKR5TT732GP4","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M74EV4WMRDKP2NQS4YWR8PXH","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M74EV05MHTXKEXD4B2QJEYTF","workspace-skill-discovery","Discover and include ALL skills across the workspace — not just global ones. Use at the start of every session or when the user asks about available skills. Ensures project-level skills (under .claude\u002Fskills\u002F or skills\u002F in any repo) are never missed.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkspace-skill-discovery\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M74ETV78525B4VP2F28Z6NRD","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M74ETR75NF67WGVEN7288ACV","winui-app","Create, build and design WinUI 3 desktop apps with C# and the Windows App SDK following Microsoft's official guidance and CommunityToolkit. Covers XAML, navigation, theming, accessibility and deployment.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M74ETJFRNPPNSQZ36C6HD6CW","windows-brain-script-portability","Scripts in ~\u002F.claude\u002Fscripts\u002F that run on a Windows brain: use the python3.cmd shim and not bare python3, and reconfigure stdout to UTF-8 if you print symbols. Use it when writing a brain script or triaging a Windows-only crash.","https:\u002F\u002Fgithub.com\u002FCarlosCaPe\u002Foctorato\u002Fblob\u002Fmaster\u002Fskills\u002Fwindows-brain-script-portability\u002FSKILL.md",[],[]]