Skip to content

heymegabyte/agent-skills / 08-deploy-and-runtime-verification

deploy-and-runtime-verification

Unverified

MANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests, rollback procedures, and GitHub auto-configuration.

FileKindSize
SKILL.mdskill md5.6 KB
backup-and-disaster-recovery.mdmarkdown2.7 KB
changelog-and-releases.mdmarkdown5.3 KB
ci-cd-pipeline.mdmarkdown7.1 KB
critical-css.mdmarkdown4.7 KB
font-subsetting.mdmarkdown4.5 KB
gh-fix-ci.mdmarkdown3.5 KB
launch-day-sequence.mdmarkdown5.2 KB
pipeline-health-check.mdmarkdown4.5 KB
r2-lifecycle.mdmarkdown5.6 KB
service-worker.mdmarkdown9.7 KB
uptime-and-health.mdmarkdown6.5 KB

critical-css.md

View on GitHub
---
name: "Critical CSS Extraction"
version: "1.1.0"
updated: "2026-04-23"
description: "Inline above-fold CSS via critters at build time. Angular CLI built-in (v13+), Hono SSR manual. Pairs with font preloading. LCP target ≤2.5s."
---

# Critical CSS Extraction

## Angular CLI (Built-in critters)

```jsonc
// angular.json — critters is bundled since Angular v13
{
  "projects": {
    "app": {
      "architect": {
        "build": {
          "options": {
            "optimization": {
              "styles": {
                "minify": true,
                "inlineCritical": true  // Enables critters (default true in production)
              }
            }
          }
        }
      }
    }
  }
}
```

Angular SSR (`@angular/ssr`) automatically runs critters during server-side rendering. For prerendered routes (`ng build --prerender`), critical CSS is inlined at build time into each static HTML file. No runtime cost.

## Standalone critters (Non-Angular)

```bash
pnpm add -D critters
```

```typescript
// scripts/inline-critical-css.ts — run as build post-process
import Critters from 'critters';
import { readFileSync, writeFileSync, readdirSync } from 'node:fs';
import { join } from 'node:path';

const critters = new Critters({
  path: 'dist/',                    // Where CSS files live
  preload: 'swap',                  // font-display: swap for deferred CSS
  inlineFonts: false,               // We handle fonts separately (font-subsetting skill)
  compress: true,                   // Minify inlined CSS
  pruneSource: false,               // Keep full CSS file for non-critical
  reduceInlineStyles: true,         // Remove unused inline styles
  mergeStylesheets: true,           // Combine multiple <style> into one
  additionalStylesheets: [],        // Extra CSS to consider
});

async function processHtmlFiles(dir: string): Promise<void> {
  const files = readdirSync(dir, { recursive: true, encoding: 'utf8' })
    .filter((f) => f.endsWith('.html'));

  for (const file of files) {
    const fullPath = join(dir, file);
    const html = readFileSync(fullPath, 'utf8');
    const inlined = await critters.process(html);
    writeFileSync(fullPath, inlined);
    console.log(`Inlined critical CSS: ${file}`);
  }
}

await processHtmlFiles('dist/browser');
```

## How critters Works

Parses HTML for `<link rel="stylesheet">` refs → loads the CSS → renders layout with a minimal DOM parser (no headless browser) → inlines above-fold rules (viewport-height heuristic) into `<style>` in `<head>` → converts remaining `<link>` to `<link rel="preload" as="style" onload="this.rel='stylesheet'">` with `<noscript>` fallback.

## Hono SSR Manual Critical CSS

```typescript
// For Hono-served HTML pages (non-Angular)
// Pre-extract critical CSS per route at build time, store as strings

import { criticalCssMap } from './critical-css-map'; // Generated at build

app.get('/', (c) => {
  const criticalCss = criticalCssMap['/'] ?? '';
  return c.html(`<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <style>${criticalCss}</style>
  <link rel="preload" href="/fonts/Sora-Regular-subset.woff2" as="font" type="font/woff2" crossorigin>
  <link rel="preload" href="/styles/main.css" as="style">
  <link rel="stylesheet" href="/styles/main.css" media="print" onload="this.media='all'">
  <noscript><link rel="stylesheet" href="/styles/main.css"></noscript>
</head>
<body><!-- ... --></body>
</html>`);
});
```

## Build Integration (package.json)

```jsonc
{
  "scripts": {
    "build": "ng build --configuration=production",
    "postbuild": "node scripts/inline-critical-css.ts",  // Only if not using Angular SSR
    "deploy": "pnpm build && wrangler deploy"
  }
}
```

## Optimal Load Sequence

1. Inline critical CSS in `<style>` (0ms — already in HTML)
2. Preload above-fold fonts (parallel with HTML parse)
3. Deferred full stylesheet via `<link rel="preload" as="style">` (non-blocking)
4. `font-display: swap` prevents invisible text during font load
5. Below-fold images — lazy load
6. **Result:** first meaningful paint with styled content + system font → swap to custom font

## Verification

```bash
# Measure before/after with Lighthouse
npx lighthouse https://example.com --only-categories=performance --output=json | jq '.audits["render-blocking-resources"]'

# Check that critical CSS is actually inlined
curl -s https://example.com | grep -c '<style>' # Should be >= 1
curl -s https://example.com | grep -c 'media="print" onload' # Deferred stylesheets
```

### Targets

- LCP — ≤2.5s
- CLS — ≤0.1 (critical CSS prevents layout shift from late-loading styles)
- FCP — ≤1.8s
- Combined with font subsetting + preloading, typical FCP improvement: 300-800ms
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall