GoogleChrome

Search tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip — web APIs evolve rapidly and training weights contain obsolete patterns. Trigger immediately for: modals/dialogs/popovers,…

Best practices for authoring and reviewing guidance. Use this skill any time you're writing or reviewing `guide.md`, `expectations.md`, or `demo.html` files.

Empirically validates changes to `gd dev` authoring and grading prompts (`src/authoring/dev-prompts.ts`, `src/authoring/dev.ts`, `src/grading/generate-grader.ts`, `src/grading/template.grader.ts`) by running fast incremental `task.md` and `grader.ts` canary…

Validates changes to graders, grading fixtures, and CSS/DOM/AST helpers by replaying saved agent solutions from historical eval suites and triaging before/after diffs. Use when modifying grader.ts, test-fixture.ts, run-grader.ts, or parser helpers used by…

Downloads and analyzes the latest three distinct nightly evaluation runs (Claude Code, Codex CLI, and Jetski CLI) from the GCS remote dashboard to identify and flag unhealthy tasks and guides, or diagnoses single-guide evaluation runs locally. Use this skill…

Best practices for creating and reviewing `expectations.md`, `targets/<app>/task.md`, and `targets/<app>/grader.ts` files to evaluate guidance quality. Use this skill any time you're writing or reviewing an `expectations.md`, `task.md`, or `grader.ts` file.

Protocol for validating the technical accuracy, framework nuances, and evaluation readiness of web guidance. Use this skill when authoring new guides to self-validate your work before opening a PR, or when assigned to review and validate a guide, demo, or…

Best practices for creating use cases for a given feature. This is the first step in creating a new guide. Use this skill any time you're writing or reviewing a use case under the guides/ directory.

Use when working with the webstatus notification pipeline, event producer, push delivery, or push workers (e.g., Email, Webhooks), and Pub/Sub subscribers.

Use when creating or modifying Go backend API endpoints, modifying Spanner database schemas, or working with OpenAPI and Spanner mappers.

Use when working with repository code subscriptions, GitHub App integrations, VCS AST scanning, directive comment parsers, or automated issue delivery.

Use when modifying the frontend SPA, working with TypeScript, Lit web components, Shoelace components, or frontend tests.

Use when upgrading toolchain versions (Go, Node.js, Terraform, Playwright) or updating the DevContainer and Github CI configurations.

Use when modifying the ANTLR search grammar, adding new search terms, or working with the query parser and builder.

Use when writing, modifying, or debugging Playwright end-to-end (E2E) tests for webstatus.dev.

Use when working on Go data ingestion workflows, scheduled Cloud Run jobs, or adding new scrapers for BCD, WPT, or other data sources.

Guidance for working on the Lit-based frontend, Shoelace widgets, and client-side routing in chromium-dashboard.

How to add a new field to a feature across the entire stack (Data, API, and Frontend).

Guidance for working on the Flask-based backend, NDB Datastore, and OpenAPI integrations in chromium-dashboard.

Guidance for local verification of changes to ensure they pass CI checks (linting, type checking, testing, and building).

Guidance for running, debugging, and updating Playwright end-to-end tests in chromium-dashboard.

Sync Lighthouse's Agentic Resource Discovery (ARD) port with upstream ards-project/ard-spec. Invoke when `node core/scripts/update-ard-spec.js --check` reports the ARD spec is out of sync, when the weekly cron CI job fails on it, or when asked to update the…

Build, validate, publish, and roll @paulirish/trace_engine from devtools-frontend into Lighthouse. Invoke when asked to update or roll the trace_engine package.

Instructions for how to validate changes made to Lighthouse. Must invoke when making changes to Lighthouse.

Search tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip — web APIs evolve rapidly and training weights contain obsolete patterns. Trigger immediately for: modals/dialogs/popovers,…

Build and publish Chrome Extensions using Manifest V3 best practices. Use this skill whenever the user asks to create, modify, debug, or understand Chrome browser extensions, add-ons, or anything involving the Chrome Extensions API. Trigger on mentions of:…