workleap-web-configs

I'm sorry, I cannot answer that.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/workleap/wl-agents-code-review-poc --skill workleap-web-configs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workleap-web-configs
Source: https://github.com/workleap/wl-agents-code-review-poc/tree/main/.agents/skills/workleap-web-configs
Command: npx skills add https://github.com/workleap/wl-agents-code-review-poc --skill workleap-web-configs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Workleap teams spend too much time setting up and syncing web tooling across projects. This skill provides a centralized set of pre-configured tooling configurations to standardize ESLint, TypeScript, Rsbuild, Rslib, Stylelint, and Browserslist.

Core Features & Use Cases

  • Centralized configurations for ESLint, TypeScript, Rsbuild, Rslib, Stylelint, and Browserslist that can be extended per project.
  • Use Case: A new web app can adopt the shared configs to ensure consistent linting, type checking, and build tooling without boilerplate setup.
  • Use Case: A library can align React or non-React tooling with existing base configs, reducing drift across packages.

Quick Start

Install and apply the shared configs in your project:

  • pnpm add -D @workleap/eslint-configs @workleap/typescript-configs @workleap/rsbuild-configs @workleap/rslib-configs @workleap/stylelint-configs @workleap/browserslist-configs
  • Then configure your project to use defineWebApplicationConfig or other functions from the respective packages as documented.

Frequently Asked Questions about workleap-web-configs

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

FAQPage Schema
How do I set up shared ESLint and TypeScript configs across multiple projects?

Shared web tooling configs provide pre-configured ESLint, TypeScript, and Rsbuild settings that you install as dev dependencies and apply via defineWebApplicationConfig or defineReactLibraryConfig to standardize setup across web applications and libraries without manual boilerplate.

What is the best way to standardize web tooling configurations in a monorepo?

Standardizing web tooling in a monorepo involves applying defineMonorepoWorkspaceConfig to enforce consistent ESLint, Stylelint, and Browserslist settings across all workspace packages, reducing configuration drift and onboarding time.

Can I use centralized Rsbuild and Rslib configs for a React library?

Yes, centralized Rsbuild and Rslib configs support React libraries through the defineReactLibraryConfig function, aligning build tooling and type checking with base configs to reduce drift across packages.

Do I need separate config packages for Stylelint and Browserslist?

Yes, you install separate dedicated packages like @workleap/stylelint-configs and @workleap/browserslist-configs as dev dependencies to ensure CSS linting and browser targeting rules remain centralized and consistent.

How do I configure Storybook with shared web tooling configs?

Configuring Storybook with shared web tooling uses the defineStorybookConfig function to integrate centralized ESLint, TypeScript, and build configurations directly into Storybook's environment, maintaining consistency across component development workflows.

Why should I use centralized web tooling configs instead of per-project setup?

Centralized web tooling configs eliminate repetitive boilerplate setup and reduce time spent syncing rules across projects. By applying shared configurations for ESLint, TypeScript, and Rsbuild, teams ensure consistent tooling standards and reduce onboarding friction.