菜单
Cloudflare skill scoped to how andrewm.codes actually uses the platform — a static Bridgetown build served by Workers Static Assets, deployed with Wrangler, with Workers observability enabled. Covers Static Assets, Workers, Wrangler, and Observability. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use whenever the user is building, modifying, debugging, or asking about a Bridgetown site or any of its features — ERB layouts, ViewComponent, collections, resources, front matter, pagination, prototype pages, plugins/builders, hooks, helpers, inspectors (`inspect_html`), wikilinks, external content sources, SSR routes via Roda, Islands architecture, Declarative Shadow DOM, esbuild bundling, Tailwind setup, or deploying to Vercel/Netlify/Render/Fly. Also trigger when the user says things like "create a new Bridgetown site", "add a Bridgetown plugin", "convert this to Bridgetown", "rebuild andrewm.codes / andrewmcodes-v7", or mentions Bridgetown-specific idioms — `bin/bridgetown`, `site.collections`, `collections.posts.resources`, `Bridgetown::Component`, `SiteBuilder`, `Bridgetown.configure`, `bridgetown.config.yml`, `config/initializers.rb`, `init :wikilinks`, `paginator.resources`, `helper :name`, `define_resource_method`, `inspect_html`, `render_with`, `<is-land>`, or `template_engine "erb"`. Even when "B
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
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.
| name | cloudflare |
| description | Cloudflare skill scoped to how andrewm.codes actually uses the platform — a static Bridgetown build served by Workers Static Assets, deployed with Wrangler, with Workers observability enabled. Covers Static Assets, Workers, Wrangler, and Observability. Biases towards retrieval from Cloudflare docs over pre-trained knowledge. |
| references | ["static-assets","workers","wrangler","observability"] |
Scoped to how this project uses Cloudflare. andrewm.codes is a fully static Bridgetown build (output/) served by Workers Static Assets and deployed with Wrangler. There is no SSR, no database, and no bindings — production is static files plus Workers observability. See wrangler.jsonc for the deploy config and the project CLAUDE.md for the deploy/CI details.
Your knowledge of Cloudflare APIs, types, limits, and pricing may be outdated. Prefer retrieval over pre-training — the references in this skill are starting points, not source of truth.
Fetch the latest information before citing specific numbers, API signatures, or configuration options. Do not rely on baked-in knowledge or these reference files alone.
| Source | How to retrieve | Use for |
|---|---|---|
| Cloudflare docs | cloudflare-docs search tool or https://developers.cloudflare.com/ | Limits, pricing, API reference, compatibility dates/flags |
| Workers types | npm pack @cloudflare/workers-types or check node_modules | Type signatures, binding shapes, handler types |
| Wrangler config schema | node_modules/wrangler/config-schema.json | Config fields, binding shapes, allowed values |
| Product changelogs | https://developers.cloudflare.com/changelog/ | Recent changes to limits, features, deprecations |
When a reference file and the docs disagree, trust the docs. This is especially important for: numeric limits, pricing tiers, type signatures, and configuration options.
output/ is uploaded as Workers Static Assets (assets.directory in wrangler.jsonc). not_found_handling: "404-page" serves /404.html on misses; a Cloudflare-format _redirects file (written by plugins/builders/redirects.rb) handles legacy and per-post redirects. There is intentionally no /* catch-all.cloudflare/wrangler-action@v4. Push to main → wrangler deploy; same-repo PR → wrangler versions upload --preview-alias <slug>. Fork PRs skip deploy.wrangler.jsonc (observability.logs), so Workers Logs are available for the static-asset Worker.| Topic | Reference | Use for |
|---|---|---|
| Static Assets | references/static-assets/ | assets config, not_found_handling, _redirects, routing precedence |
| Workers | references/workers/ | Worker runtime model, request handling, compatibility dates/flags |
| Wrangler | references/wrangler/ | deploy, versions upload, config schema, preview aliases |
| Observability | references/observability/ | Workers Logs, sampling, trace/log config, real-time debugging |
If a task genuinely needs a Cloudflare product not listed here (a database, queue, AI, etc.), that would be a new capability for this site — retrieve from the Cloudflare docs rather than assuming it's already wired up, and consider whether it belongs in this static-site architecture at all.