skills.rest
ccediland
ccedilandCOMMUNITY
Explore all skills by this author →
GitHub

stack-integration-playbook

Composes web-stack skills into one site with canonical ordering, seams, and recipes.

Updated Jun 17, 2026
Search Tags:#cloudflare workers#composition#csp#astro#lead capture#lighthouse ci#web stack
One-click install
npx skills add https://github.com/ccediland/web-stack-skills --skill stack-integration-playbook-ccediland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stack-integration-playbook
Source: https://github.com/ccediland/web-stack-skills/tree/main/plugin/skills/stack-integration-playbook
Command: npx skills add https://github.com/ccediland/web-stack-skills --skill stack-integration-playbook-ccediland

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Combining multiple Astro/Cloudflare web skills into one site fails at the seams — vacuous CI gates, CSP conflicts, deploy-shape surprises — and no single skill explains those failures. This playbook defines the canonical composition order, the cross-skill seams, and the recipes for forms, analytics, prefetching, and legal notices. ## Core Features & Use Cases - Canonical composition order: An 8-step dependency chain (brand ingest → tokens → CSP → CI gates → SEO → motion → one visual → CMS) with explicit omit conditions per step. - Cross-cutting seam catalog: Field-proven failure modes like LHCI asserting nothing, _headers concatenation, and software-WebGL CPU blowups, each with its fix. - Capability recipes: Ready architectures for lead-capture forms (Astro Action + Turnstile + Supabase), cookieless analytics (Umami + server-side conversion events), Speculation Rules prefetching, and the Mexican aviso de privacidad template. - Use Case: When a brief asks for a lead-gen landing, use the playbook to pick the skill subset, sequence the build, wire the contact form and analytics, and verify the composed CI gates actually assert. ## Quick Start Ask the AI to compose the catalog skills into a full site build plan for your brief, in the canonical order with the right recipe.

Frequently Asked Questions about stack-integration-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I combine multiple Astro skills into one website build?▼

Follow the canonical composition order: brand ingest, CSS tokens, security headers, perf CI gates, SEO schema, motion, at most one visual skill, then CMS. Each step consumes artifacts from the previous one, so reordering breaks the dependency chain.

How do I add a contact form to an Astro site on Cloudflare Workers?▼

Use the forms recipe: an Astro Action on the site's own Worker with server-side Turnstile verification, a zod-validated insert into a Supabase leads table with insert-only RLS, and email notification via Cloudflare Email Service. Pages stay prerendered; only the /_actions/* route renders on demand.

What analytics tool works with a strict CSP on a static site?▼

The recipe recommends Umami: a 2.3 KB cookieless script needing only two CSP origin allowances, with the conversion event fired server-side from the Astro Action. GA4 is excluded at 143 KB with a hostile multi-domain CSP surface.

Why does my Lighthouse CI job pass but assert nothing?▼

LHCI refuses assert.assertions combined with assert.budgetsFile, and the action wrapper swallows the crash, reporting green. Express budgets as resource-summary assertions inside one assertions block, and verify the job log shows assertions actually ran.

Does Cloudflare Speed Brain work with Workers Static Assets?▼

No. Speed Brain's documentation states it will not prefetch on routes that run Workers, and every Workers Static Assets route is served through a Worker. Use Astro's stable prefetch by default and manual Speculation Rules prerender as a Chromium-only escalation.

When should I not use this composition playbook?▼

Do not use it for single capabilities — CSP setup belongs to web-security-headers, CI gates to perf-ci-gates, and external data to data-layer. Customer portals with per-user data are also out of scope, as they require app-style SSR under auth rather than prerendered pages.

Related Skills

Explore More Software Engineering Skills→
hardness1020hardness1020
8

clarify-demand

Clarify demand and feasibility before work-item registration with an Intake Brief.

Community
Advanced
GenEducationGenEducation

land-and-deploy

Merge a pull request, wait for CI and deployment, and verify production health with canary checks.

Official
Advanced
ChegginCheggin
1

performance-benchmark

Measure and enforce web performance budgets with Lighthouse CI.

Community
Advanced
foomakersfoomakers
6

assess-stack

Assess and define a project's technology stack with version tracking.

Official
Advanced