Run any Skill in Manus with one click

eslint-config-change

Stars1

Forks0

UpdatedMay 7, 2026 at 10:27

Scope is the entire monorepo (root + all workspaces under apps/* and packages/*). Update the monorepo ESLint configuration in vnext-forge-studio. Use when changing shared lint rules, workspace-specific ESLint behavior, runtime globals, or logger/no-console overrides. Trigger this skill for any ESLint config work in `eslint.config.mjs` at the repo root or in any workspace.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

burgan-tech

burgan-tech/vnext-forge

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	eslint-config-change
description	Scope is the entire monorepo (root + all workspaces under apps/* and packages/*). Update the monorepo ESLint configuration in vnext-forge-studio. Use when changing shared lint rules, workspace-specific ESLint behavior, runtime globals, or logger/no-console overrides. Trigger this skill for any ESLint config work in `eslint.config.mjs` at the repo root or in any workspace.

ESLint Config Change

Scope: Repo-wide (root eslint.config.mjs plus per-workspace ESLint files under apps/* and packages/*).

Use this skill when editing the ESLint setup in this repository.

Architecture

Keep the root eslint.config.mjs as the shared monorepo factory only.
Do not turn the root config into a real lint target. The default export should stay minimal and ignore the root by default.
Use createWorkspaceConfig(...) from the root config in each workspace-level ESLint file.
Put workspace-specific plugins, overrides, and file globs in the workspace config, not in the root shared factory, unless the rule truly applies everywhere.

Runtime Model

Set runtime: 'browser' for frontend apps.
Set runtime: 'node' for backend/server apps.
Set runtime: 'library' for packages that should not receive implicit browser or node globals.
Do not force globals.browser or globals.node onto library packages unless there is an explicit runtime requirement.

Console And Logger Policy

Keep no-console enabled as error in the shared rule set.
Do not disable no-console globally or per workspace.
Allow console.* only in the single central logger implementation file for that workspace.
When a logger file is added, update only that workspace's loggerConsoleFiles list with the exact relative path.
Preserve the TODO(logger) comments in the shared config and workspace configs. Do not delete or weaken them before a real central logger exists.

Monorepo Guardrails

Avoid root-level file globs such as src/**/* inside the shared config. Those patterns are wrong for a monorepo root.
Keep workspace globs relative to the workspace config file that owns them.
Prefer shared rules in the root factory and package/app-specific behavior in workspace configs under apps/* and packages/*.

Validation

After changing ESLint config, validate the affected workspace with pnpm exec eslint --print-config <file>.
Validate from inside the target workspace so tsconfigRootDir and runtime globals resolve correctly.
If a logger override was added, confirm that no-console is still error outside the logger file and off only for the listed logger path.

More from this repository

same repository

dependency-policy

burgan-tech/vnext-forge

Scope is repo-wide. Enforces the cross-package import direction policy (apps depend on packages; packages depend only on packages of equal or lower role; apps never depend on each other). Trigger this skill when adding a new import that crosses workspace boundaries, modifying `package.json` `dependencies`, adding/changing barrel files, or editing ESLint `no-restricted-imports`. See `docs/architecture/dependency-policy.md`.

2026-05-071

error-taxonomy

burgan-tech/vnext-forge

Scope is repo-wide. Authoritative guide for the error contract built around `ERROR_CODES`, `VnextForgeError`, `ApiResponse<T>`, and `error-presentation`. Trigger this skill whenever throwing, catching, mapping, displaying, or testing errors anywhere in the monorepo (apps/*, packages/*). See ADR 005.

2026-05-071

notification-feedback

burgan-tech/vnext-forge

Scope is the host-agnostic notification port in packages/designer-ui plus its shell adapters in apps/web (sonner toast) and apps/extension/webview-ui (VS Code native). Guidelines for emitting and routing transient user feedback (toast / native notification / status-bar pill). Use when calling showNotification(...), wiring a new shell sink, deciding between transient feedback and inline screen state, or working on status-bar notification chrome.

2026-05-071

theme-color-system-web

burgan-tech/vnext-forge

Scope is apps/web (web frontend). Optional guidance for theming and color tokens in the web app. Use only when the task is explicitly about visual system work; do not treat theme token migration as a required part of the architecture refactor. Trigger this skill for any theming or color token work under `apps/web`.

2026-04-221

trace-headers

burgan-tech/vnext-forge

Scope is repo-wide. Implements the `trace-v1` contract for `X-Trace-Id` and `traceparent` correlation. Trigger this skill whenever editing HTTP middleware, transports, RPC clients, runtime-proxy, or anything that reads/writes trace headers anywhere in the monorepo. See ADR 002.

2026-04-201

vnext-features

burgan-tech/vnext-forge

Scope is repo-wide domain knowledge (not bound to a single workspace). vNext Runtime platform referansı. Workflow, state, transition, task, schema, view, function ve extension kavramlarını, JSON tanım yapılarını ve C# mapping/rule pattern'lerini kapsar. vNext bileşenleri oluşturulurken veya düzenlenirken bu skill'i kullanın. Trigger this skill whenever vNext workflow/task/schema/view/function/extension JSON or `.csx` mapping/rule files are being created or edited anywhere in the monorepo (or in target vnext domain repositories).

2026-04-191

name	eslint-config-change
description	Scope is the entire monorepo (root + all workspaces under apps/* and packages/*). Update the monorepo ESLint configuration in vnext-forge-studio. Use when changing shared lint rules, workspace-specific ESLint behavior, runtime globals, or logger/no-console overrides. Trigger this skill for any ESLint config work in `eslint.config.mjs` at the repo root or in any workspace.

ESLint Config Change

Scope: Repo-wide (root eslint.config.mjs plus per-workspace ESLint files under apps/* and packages/*).

Use this skill when editing the ESLint setup in this repository.

Architecture

Keep the root eslint.config.mjs as the shared monorepo factory only.
Do not turn the root config into a real lint target. The default export should stay minimal and ignore the root by default.
Use createWorkspaceConfig(...) from the root config in each workspace-level ESLint file.
Put workspace-specific plugins, overrides, and file globs in the workspace config, not in the root shared factory, unless the rule truly applies everywhere.

Runtime Model

Set runtime: 'browser' for frontend apps.
Set runtime: 'node' for backend/server apps.
Set runtime: 'library' for packages that should not receive implicit browser or node globals.
Do not force globals.browser or globals.node onto library packages unless there is an explicit runtime requirement.

Console And Logger Policy

Keep no-console enabled as error in the shared rule set.
Do not disable no-console globally or per workspace.
Allow console.* only in the single central logger implementation file for that workspace.
When a logger file is added, update only that workspace's loggerConsoleFiles list with the exact relative path.
Preserve the TODO(logger) comments in the shared config and workspace configs. Do not delete or weaken them before a real central logger exists.

Monorepo Guardrails

Avoid root-level file globs such as src/**/* inside the shared config. Those patterns are wrong for a monorepo root.
Keep workspace globs relative to the workspace config file that owns them.
Prefer shared rules in the root factory and package/app-specific behavior in workspace configs under apps/* and packages/*.

Validation

After changing ESLint config, validate the affected workspace with pnpm exec eslint --print-config <file>.
Validate from inside the target workspace so tsconfigRootDir and runtime globals resolve correctly.
If a logger override was added, confirm that no-console is still error outside the logger file and off only for the listed logger path.