skills.rest
GoogleChrome
GoogleChromeOFFICIAL
Explore all skills by this author →
GitHub

project-coding-standards

Enforces coding conventions, architectural principles, and PR review standards for the modern-web-guidance-src repository.

1.0k|75|Updated Jan 27, 2026
Search Tags:#linting#CLI#Coding Standards#typeScript#repository conventions#Code review#Pull request
One-click install
npx skills add https://github.com/GoogleChrome/modern-web-guidance-src --skill project-coding-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-coding-standards
Source: https://github.com/GoogleChrome/modern-web-guidance-src/tree/main/.agents/skills/project-coding-standards
Command: npx skills add https://github.com/GoogleChrome/modern-web-guidance-src --skill project-coding-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contributors to the modern-web-guidance-src repository risk producing inconsistent code, monolithic PRs, and bypassed verification gates without a shared set of architectural and review standards.

Core Features & Use Cases

  • Architectural Conventions: Enforces reuse of shared CLI runners, centralized enums (Agents, Serving), canonical metadata from evals.json, and separation of prompts from execution logic.
  • PR Scope & Review Standards: Guides splitting multi-component features into small, sequential PRs across data layer, CLI workflows, and UI components.
  • Verification Gates: Defines tiered preflight checks including pnpm typecheck, lint, preflight, and Playwright E2E tests for eval-view dashboard changes.
  • Use Case: When authoring a new CLI command or dashboard endpoint, apply these standards to keep the PR focused, reuse existing abstractions, and pass all preflight gates before submission.

Quick Start

Review my changes to the harness CLI against the project coding standards and tell me what to fix before opening a PR.

Frequently Asked Questions about project-coding-standards

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

FAQPage Schema
How do I structure PRs for the modern-web-guidance repository?▼

Keep each PR focused on a single component and split multi-component features into sequential PRs: data layer first, then CLI workflows, then UI components. Smaller PRs are easier to review, test, and revert.

What checks must pass before submitting a PR?▼

Run pnpm run preflight, which bundles build, typecheck, lint, and parallel unit tests across workspaces. For eval-view dashboard or server changes, also run pnpm --filter eval-view run test:e2e with Playwright.

Should I use raw strings or enums for agent and serving modes?▼

Use the centralized enums from harness/config.ts, such as Agents.JETSKI and Serving.MCP, instead of hardcoded string constants. This keeps a single source of truth across the codebase.

Can I modify tsconfig.json to fix typecheck errors?▼

No. Shared root configurations like tsconfig.json, package.json, and .oxlintignore must not be weakened to bypass failures. Fix types properly with TypeScript interfaces or targeted JSDoc annotations.

How should the dashboard handle static hosting versus local server mode?▼

Features requiring a local Node server must detect static mode and gracefully hide or disable themselves. Pass explicit data source context like ?source=local so the server distinguishes local file operations from remote streaming.

Related Skills

Explore More Software Engineering Skills→
EanLeeEanLee

monorepo-management

Configure monorepos with Turborepo, Nx, and pnpm workspaces.

Community
Advanced
cookeyholdercookeyholder

squash-pr

Squash and merge a GitHub pull request into main after validating review feedback.

Community
Advanced
LimaTechnologiesLimaTechnologies

quality-gate

Run typecheck, lint, tests, and build for TypeScript projects.

Community
Advanced
PostalocityPostalocity
1

auto-format

Format code and fix lint errors across a codebase.

Official
Basic