What problem does it solve? Web projects drift into inconsistent tooling setups: relaxed TypeScript strictness, linters that pass on warnings, package managers resolving unpinned binaries, and CI gates that disagree with local git hooks. This Skill encodes one enforced set of conventions so every web component builds, lints, tests, and documents the same way. ## Core Features & Use Cases - Strict TypeScript configuration: Extend a synced tsconfig.base.json with framework-specific options without relaxing strict flags, and use @ts-expect-error instead of @ts-ignore. - Biome linting and formatting: Run the local binary via ./node_modules/.bin/biome with --error-on-warnings so warning-severity rules actually gate CI, and keep tools as real devDependencies rather than relying on npx fallbacks. - Testing, docs, and CI alignment: Set up Vitest coverage thresholds, TSDoc plus TypeDoc validation, required package.json scripts, lefthook git hooks, and Turborepo task graphs that match what web-ci.yml invokes. - Use Case: When migrating a project from npm to pnpm, follow the guidance to run pnpm import, move settings into pnpm-workspace.yaml, declare onlyBuiltDependencies, and check vercel.json for a pinned npm installCommand that would break deploys. ## Quick Start Use the web-development-guide skill to review my Next.js project's package.json scripts, tsconfig, and Biome setup against the required conventions.
