andrewm.codes

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

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.

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.