config-setup

Configures project dependencies, Biome linting, and TypeScript standards for frontend projects.

1|Updated Jul 18, 2025
One-click install
npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill config-setup-adelysalberto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: config-setup
Source: https://github.com/AdelysAlberto/md-configs-and-agents/tree/main/agents-hermes/skills/config-setup
Command: npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill config-setup-adelysalberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a new frontend project involves dozens of configuration decisions—dependency versions, linter rules, TypeScript settings, and pre-commit hooks—that are easy to get wrong or inconsistent across a team. This Skill enforces a single, opinionated standard for configuration files so every project starts with the same vetted setup. ## Core Features & Use Cases - Dynamic Dependency Resolution: Prohibits hardcoded or wildcard versions in package.json and requires fetching the latest published versions at runtime with bun pm view. - Biome Linter & Formatter Template: Ships a complete biome.json configuration with strict rules, JSON file exclusions, and import organization enabled. - TypeScript, Vite & Vitest Standards: Defines strict tsconfig settings, Vite build conventions, environment variable handling via env-config files, and test layout rules. - Use Case: When scaffolding a new React + TypeScript project, use this Skill to generate a compliant package.json, biome.json, and tsconfig.json, then verify everything passes pnpm typecheck and pnpm lint before the first commit. ## Quick Start Set up a new Vite React TypeScript project following the config-setup standards with pinned dependencies and the default Biome configuration.

Frequently Asked Questions about config-setup

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

FAQPage Schema
How do I configure Biome as a linter and formatter for a TypeScript project?▼

Create a biome.json that enables the formatter and linter, sets indent style and line width, and defines rule overrides for a11y, complexity, and correctness. Exclude package.json and tsconfig files from formatting using negated include patterns and a disabled JSON formatter override.

How to pin exact dependency versions in package.json?▼

Remove wildcard ranges like ^ and ~ and write exact version strings instead. Fetch the current published version at runtime with bun pm view <package> version or bun add <package>@latest rather than relying on memorized version numbers.

Should Biome format package.json and tsconfig.json files?▼

No, this setup explicitly disables Biome formatting and linting for package.json and tsconfig files. Use negated include patterns plus an overrides block with formatter and linter disabled to prevent reordering of configuration keys.

What TypeScript strict settings should a Vite project use?▼

Enable strict: true in tsconfig.json with target ES2022 and moduleResolution set to bundler. Verify the configuration by running tsc --noEmit against the source-specific tsconfig before every commit.

Why does the pre-commit hook fail on lint or typecheck errors?▼

Husky pre-commit hooks run Biome checks and TypeScript typechecking, so any unused imports, undeclared variables, or type errors block the commit. Fix violations with biome check --write and avoid bypassing hooks with --no-verify unless explicitly approved.