Jakość

Build, lint and format tooling

Sets up front-end tooling the way the project already does - package manager and lockfile, Vite 8, ESLint 10 flat config with accessibility plugins, Prettier 3 or Biome 2, Stylelint, TypeScript type checks, browserslist with Baseline targets, Node LTS. Use when adding or upgrading a linter, formatter, bundler or TypeScript, fixing a broken config or CI step, or when asked "set up linting".

fe-toolingvite, eslint, prettier, biome6 regułładowane zawsze: 88 tokenów; przy użyciu: 857 tokenów; w referencjach na żądanie: 1519 tokenów.

Instalacja

init instaluje ten skill, gdy projekt używa: vite, eslint, prettier, biome. Wybierz agenta, aby zobaczyć, gdzie trafią jego pliki.

npx github:dawidolko/frontend-skills init

Ten sposób nie był jeszcze testowany. npx i pnpm dlx są przetestowane; jeśli ten zawiedzie, użyj jednego z nich.

Bez --agents polecenie init rozpoznaje agentów po tym, co projekt już ma, a gdy nie znajdzie żadnego, pyta:

Po czym init rozpoznaje każdego z agentów (17)

Agent	Rozpoznawany po
Claude Code	`CLAUDE.md` `.claude` `CLAUDE.local.md`
OpenAI Codex	`.codex` `AGENTS.override.md`
Cursor	`.cursor` `.cursorrules`
GitHub Copilot	`.github/copilot-instructions.md` `.github/instructions` `.github/skills` `.github/prompts`
Gemini CLI	`GEMINI.md` `.gemini`
Antigravity CLI	`.agents/rules` `.agent/rules`
Devin / Windsurf	`.devin` `.windsurf` `.windsurfrules`
OpenCode	`opencode.json` `opencode.jsonc` `.opencode`
Cline	`.clinerules` `.cline`
Zed	`.rules` `.zed`
JetBrains Junie	`.junie`
Kiro	`.kiro`
Augment	`.augment` `.augment-guidelines`
Trae	`.trae`
Continue	`.continue`
Amazon Q Developer	`.amazonq`
Aider	`.aider.conf.yml` `CONVENTIONS.md`

Gdzie trafia fe-tooling dla: Claude Code

.claude/skills/fe-tooling/SKILL.mdskill
.claude/skills/fe-tooling/references/tooling.mdskill
.claude/rules/fe-tooling.mdplik reguł
CLAUDE.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.claude/rules/fe-tooling.md

---
paths:
  - "**/package.json"
  - "**/eslint.config.*"
  - "**/vite.config.*"
  - "**/tsconfig*.json"
  - "**/biome.json"
  - "**/.prettierrc*"
  - "**/stylelint.config.*"
  - "**/.browserslistrc"
---

# Build, lint and format tooling (frontend-skills)

Sets up front-end tooling the way the project already does - package manager and lockfile, Vite 8, ESLint 10 flat config with accessibility plugins, Prettier 3 or Biome 2, Stylelint, TypeScript type checks, browserslist with Baseline targets, Node LTS. Use when adding or upgrading a linter, formatter, bundler or TypeScript, fixing a broken config or CI step, or when asked "set up linting".

- Run the project's scripts with its package manager; never install tools globally (tooling/use-project-scripts).
- Keep one committed lockfile; CI installs with the frozen command (tooling/one-lockfile).
- ESLint 10 reads only `eslint.config.*`; migrate `.eslintrc*` and `.eslintignore` (tooling/eslint-flat-config).
- TypeScript projects run a separate type check in CI; bundlers only strip types (tooling/typecheck-separately).
- Lint with the framework's accessibility plugin or compiler warnings (tooling/a11y-lint).
- Declare browser targets once, as a Baseline query; no blanket polyfills (perf/no-legacy-javascript).
- One formatter per file type; with ESLint and Prettier together, turn off ESLint's style rules (`eslint-config-prettier`).
- Pin the Node version to a supported LTS line (22, 24 or 26 in November 2026) in `.nvmrc` and `engines`.
- Never weaken a lint rule or a type to make a check pass; fix the code or explain the exception inline.
- Do not switch tools in passing (ESLint to Oxlint, Prettier to Biome); propose it separately.

Before larger changes, read the full skill: `.claude/skills/fe-tooling/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-tooling dla: OpenAI Codex

.agents/skills/fe-tooling/SKILL.mdskill
.agents/skills/fe-tooling/references/tooling.mdskill
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

OpenAI Codex nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

AGENTS.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Cursor

.agents/skills/fe-tooling/SKILL.mdskill
.agents/skills/fe-tooling/references/tooling.mdskill
.cursor/rules/fe-tooling.mdcplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.cursor/rules/fe-tooling.mdc

---
description: Sets up front-end tooling the way the project already does - package manager and lockfile, Vite 8, ESLint 10 flat config with accessibility plugins, Prettier 3 or Biome 2, Stylelint, TypeScript type checks, browserslist with Baseline targets, Node LTS. Use when adding or upgrading a linter, formatter, bundler or TypeScript, fixing a broken config or CI step, or when asked "set up linting".
globs: **/package.json, **/eslint.config.*, **/vite.config.*, **/tsconfig*.json, **/biome.json, **/.prettierrc*, **/stylelint.config.*, **/.browserslistrc
alwaysApply: false
---

# Build, lint and format tooling (frontend-skills)

- Run the project's scripts with its package manager; never install tools globally (tooling/use-project-scripts).
- Keep one committed lockfile; CI installs with the frozen command (tooling/one-lockfile).
- ESLint 10 reads only `eslint.config.*`; migrate `.eslintrc*` and `.eslintignore` (tooling/eslint-flat-config).
- TypeScript projects run a separate type check in CI; bundlers only strip types (tooling/typecheck-separately).
- Lint with the framework's accessibility plugin or compiler warnings (tooling/a11y-lint).
- Declare browser targets once, as a Baseline query; no blanket polyfills (perf/no-legacy-javascript).
- One formatter per file type; with ESLint and Prettier together, turn off ESLint's style rules (`eslint-config-prettier`).
- Pin the Node version to a supported LTS line (22, 24 or 26 in November 2026) in `.nvmrc` and `engines`.
- Never weaken a lint rule or a type to make a check pass; fix the code or explain the exception inline.
- Do not switch tools in passing (ESLint to Oxlint, Prettier to Biome); propose it separately.

Before larger changes, read the full skill: `.agents/skills/fe-tooling/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-tooling dla: GitHub Copilot

.agents/skills/fe-tooling/SKILL.mdskill
.agents/skills/fe-tooling/references/tooling.mdskill
.github/instructions/fe-tooling.instructions.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.github/instructions/fe-tooling.instructions.md

---
applyTo: "**/package.json,**/eslint.config.*,**/vite.config.*,**/tsconfig*.json,**/biome.json,**/.prettierrc*,**/stylelint.config.*,**/.browserslistrc"
description: "Sets up front-end tooling the way the project already does - package manager and lockfile, Vite 8, ESLint 10 flat config with accessibility plugins, Prettier 3 or Biome 2, Stylelint, TypeScript type checks, browserslist with Baseline targets, Node LTS. Use when adding or upgrading a linter, formatter, bundler or TypeScript, fixing a broken config or CI step, or when asked \"set up linting\"."
---

# Build, lint and format tooling (frontend-skills)

- Run the project's scripts with its package manager; never install tools globally (tooling/use-project-scripts).
- Keep one committed lockfile; CI installs with the frozen command (tooling/one-lockfile).
- ESLint 10 reads only `eslint.config.*`; migrate `.eslintrc*` and `.eslintignore` (tooling/eslint-flat-config).
- TypeScript projects run a separate type check in CI; bundlers only strip types (tooling/typecheck-separately).
- Lint with the framework's accessibility plugin or compiler warnings (tooling/a11y-lint).
- Declare browser targets once, as a Baseline query; no blanket polyfills (perf/no-legacy-javascript).
- One formatter per file type; with ESLint and Prettier together, turn off ESLint's style rules (`eslint-config-prettier`).
- Pin the Node version to a supported LTS line (22, 24 or 26 in November 2026) in `.nvmrc` and `engines`.
- Never weaken a lint rule or a type to make a check pass; fix the code or explain the exception inline.
- Do not switch tools in passing (ESLint to Oxlint, Prettier to Biome); propose it separately.

Before larger changes, read the full skill: `.agents/skills/fe-tooling/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Gemini CLI

.agents/skills/fe-tooling/SKILL.mdskill
.agents/skills/fe-tooling/references/tooling.mdskill
GEMINI.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Gemini CLI: Gemini CLI was replaced by Antigravity CLI for unpaid tiers on 2026-06-18; choose "antigravity" too if you use it.

Gemini CLI nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

GEMINI.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Antigravity CLI

.agents/skills/fe-tooling/SKILL.mdskill
.agents/skills/fe-tooling/references/tooling.mdskill
.agents/rules/fe-tooling.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.agents/rules/fe-tooling.md

---
trigger: glob
globs: "**/package.json, **/eslint.config.*, **/vite.config.*, **/tsconfig*.json, **/biome.json, **/.prettierrc*, **/stylelint.config.*, **/.browserslistrc"
description: "Sets up front-end tooling the way the project already does - package manager and lockfile, Vite 8, ESLint 10 flat config with accessibility plugins, Prettier 3 or Biome 2, Stylelint, TypeScript type checks, browserslist with Baseline targets, Node LTS. Use when adding or upgrading a linter, formatter, bundler or TypeScript, fixing a broken config or CI step, or when asked \"set up linting\"."
---

# Build, lint and format tooling (frontend-skills)

- Run the project's scripts with its package manager; never install tools globally (tooling/use-project-scripts).
- Keep one committed lockfile; CI installs with the frozen command (tooling/one-lockfile).
- ESLint 10 reads only `eslint.config.*`; migrate `.eslintrc*` and `.eslintignore` (tooling/eslint-flat-config).
- TypeScript projects run a separate type check in CI; bundlers only strip types (tooling/typecheck-separately).
- Lint with the framework's accessibility plugin or compiler warnings (tooling/a11y-lint).
- Declare browser targets once, as a Baseline query; no blanket polyfills (perf/no-legacy-javascript).
- One formatter per file type; with ESLint and Prettier together, turn off ESLint's style rules (`eslint-config-prettier`).
- Pin the Node version to a supported LTS line (22, 24 or 26 in November 2026) in `.nvmrc` and `engines`.
- Never weaken a lint rule or a type to make a check pass; fix the code or explain the exception inline.
- Do not switch tools in passing (ESLint to Oxlint, Prettier to Biome); propose it separately.

Before larger changes, read the full skill: `.agents/skills/fe-tooling/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Devin / Windsurf

.agents/skills/fe-tooling/SKILL.mdskill
.agents/skills/fe-tooling/references/tooling.mdskill
.devin/rules/fe-tooling.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Devin / Windsurf: Devin CLI also reads .cursor/rules; with Cursor chosen too, the CLI sees both rule files of a skill.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.devin/rules/fe-tooling.md

---
trigger: glob
globs: "**/package.json,**/eslint.config.*,**/vite.config.*,**/tsconfig*.json,**/biome.json,**/.prettierrc*,**/stylelint.config.*,**/.browserslistrc"
---

# Build, lint and format tooling (frontend-skills)

Sets up front-end tooling the way the project already does - package manager and lockfile, Vite 8, ESLint 10 flat config with accessibility plugins, Prettier 3 or Biome 2, Stylelint, TypeScript type checks, browserslist with Baseline targets, Node LTS. Use when adding or upgrading a linter, formatter, bundler or TypeScript, fixing a broken config or CI step, or when asked "set up linting".

- Run the project's scripts with its package manager; never install tools globally (tooling/use-project-scripts).
- Keep one committed lockfile; CI installs with the frozen command (tooling/one-lockfile).
- ESLint 10 reads only `eslint.config.*`; migrate `.eslintrc*` and `.eslintignore` (tooling/eslint-flat-config).
- TypeScript projects run a separate type check in CI; bundlers only strip types (tooling/typecheck-separately).
- Lint with the framework's accessibility plugin or compiler warnings (tooling/a11y-lint).
- Declare browser targets once, as a Baseline query; no blanket polyfills (perf/no-legacy-javascript).
- One formatter per file type; with ESLint and Prettier together, turn off ESLint's style rules (`eslint-config-prettier`).
- Pin the Node version to a supported LTS line (22, 24 or 26 in November 2026) in `.nvmrc` and `engines`.
- Never weaken a lint rule or a type to make a check pass; fix the code or explain the exception inline.
- Do not switch tools in passing (ESLint to Oxlint, Prettier to Biome); propose it separately.

Before larger changes, read the full skill: `.agents/skills/fe-tooling/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-tooling dla: OpenCode

.agents/skills/fe-tooling/SKILL.mdskill
.agents/skills/fe-tooling/references/tooling.mdskill
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

OpenCode nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

AGENTS.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Cline

.claude/skills/fe-tooling/SKILL.mdskill
.claude/skills/fe-tooling/references/tooling.mdskill
.clinerules/fe-tooling.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Cline: If .clinerules is a single file rather than a folder, Cline rule files are not written; skills still are.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.clinerules/fe-tooling.md

---
paths:
  - "**/package.json"
  - "**/eslint.config.*"
  - "**/vite.config.*"
  - "**/tsconfig*.json"
  - "**/biome.json"
  - "**/.prettierrc*"
  - "**/stylelint.config.*"
  - "**/.browserslistrc"
---

# Build, lint and format tooling (frontend-skills)

Sets up front-end tooling the way the project already does - package manager and lockfile, Vite 8, ESLint 10 flat config with accessibility plugins, Prettier 3 or Biome 2, Stylelint, TypeScript type checks, browserslist with Baseline targets, Node LTS. Use when adding or upgrading a linter, formatter, bundler or TypeScript, fixing a broken config or CI step, or when asked "set up linting".

- Run the project's scripts with its package manager; never install tools globally (tooling/use-project-scripts).
- Keep one committed lockfile; CI installs with the frozen command (tooling/one-lockfile).
- ESLint 10 reads only `eslint.config.*`; migrate `.eslintrc*` and `.eslintignore` (tooling/eslint-flat-config).
- TypeScript projects run a separate type check in CI; bundlers only strip types (tooling/typecheck-separately).
- Lint with the framework's accessibility plugin or compiler warnings (tooling/a11y-lint).
- Declare browser targets once, as a Baseline query; no blanket polyfills (perf/no-legacy-javascript).
- One formatter per file type; with ESLint and Prettier together, turn off ESLint's style rules (`eslint-config-prettier`).
- Pin the Node version to a supported LTS line (22, 24 or 26 in November 2026) in `.nvmrc` and `engines`.
- Never weaken a lint rule or a type to make a check pass; fix the code or explain the exception inline.
- Do not switch tools in passing (ESLint to Oxlint, Prettier to Biome); propose it separately.

Before larger changes, read the full skill: `.claude/skills/fe-tooling/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Zed

.agents/skills/fe-tooling/SKILL.mdskill
.agents/skills/fe-tooling/references/tooling.mdskill
CLAUDE.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zed: Zed reads only the first instruction file of its list; the block is placed in that file.

Zed nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

CLAUDE.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-tooling dla: JetBrains Junie

.agents/skills/fe-tooling/SKILL.mdskill
.agents/skills/fe-tooling/references/tooling.mdskill
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

JetBrains Junie: Junie reads .agents/skills only in a trusted project.

JetBrains Junie nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

AGENTS.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Kiro

.kiro/skills/fe-tooling/SKILL.mdskill
.kiro/skills/fe-tooling/references/tooling.mdskill
.kiro/steering/fe-tooling.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.kiro/steering/fe-tooling.md

---
inclusion: fileMatch
fileMatchPattern: ["**/package.json", "**/eslint.config.*", "**/vite.config.*", "**/tsconfig*.json", "**/biome.json", "**/.prettierrc*", "**/stylelint.config.*", "**/.browserslistrc"]
---

# Build, lint and format tooling (frontend-skills)

Sets up front-end tooling the way the project already does - package manager and lockfile, Vite 8, ESLint 10 flat config with accessibility plugins, Prettier 3 or Biome 2, Stylelint, TypeScript type checks, browserslist with Baseline targets, Node LTS. Use when adding or upgrading a linter, formatter, bundler or TypeScript, fixing a broken config or CI step, or when asked "set up linting".

- Run the project's scripts with its package manager; never install tools globally (tooling/use-project-scripts).
- Keep one committed lockfile; CI installs with the frozen command (tooling/one-lockfile).
- ESLint 10 reads only `eslint.config.*`; migrate `.eslintrc*` and `.eslintignore` (tooling/eslint-flat-config).
- TypeScript projects run a separate type check in CI; bundlers only strip types (tooling/typecheck-separately).
- Lint with the framework's accessibility plugin or compiler warnings (tooling/a11y-lint).
- Declare browser targets once, as a Baseline query; no blanket polyfills (perf/no-legacy-javascript).
- One formatter per file type; with ESLint and Prettier together, turn off ESLint's style rules (`eslint-config-prettier`).
- Pin the Node version to a supported LTS line (22, 24 or 26 in November 2026) in `.nvmrc` and `engines`.
- Never weaken a lint rule or a type to make a check pass; fix the code or explain the exception inline.
- Do not switch tools in passing (ESLint to Oxlint, Prettier to Biome); propose it separately.

Before larger changes, read the full skill: `.kiro/skills/fe-tooling/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Augment

.agents/skills/fe-tooling/SKILL.mdskill
.agents/skills/fe-tooling/references/tooling.mdskill
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Augment nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

AGENTS.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Trae

.trae/skills/fe-tooling/SKILL.mdskill
.trae/skills/fe-tooling/references/tooling.mdskill
.trae/rules/fe-tooling.mdplik reguł
AGENTS.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Trae: Trae reads AGENTS.md only after it is enabled in its settings.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.trae/rules/fe-tooling.md

---
description: "Sets up front-end tooling the way the project already does - package manager and lockfile, Vite 8, ESLint 10 flat config with accessibility plugins, Prettier 3 or Biome 2, Stylelint, TypeScript type checks, browserslist with Baseline targets, Node LTS. Use when adding or upgrading a linter, formatter, bundler or TypeScript, fixing a broken config or CI step, or when asked \"set up linting\"."
globs: **/package.json,**/eslint.config.*,**/vite.config.*,**/tsconfig*.json,**/biome.json,**/.prettierrc*,**/stylelint.config.*,**/.browserslistrc
alwaysApply: false
---

# Build, lint and format tooling (frontend-skills)

- Run the project's scripts with its package manager; never install tools globally (tooling/use-project-scripts).
- Keep one committed lockfile; CI installs with the frozen command (tooling/one-lockfile).
- ESLint 10 reads only `eslint.config.*`; migrate `.eslintrc*` and `.eslintignore` (tooling/eslint-flat-config).
- TypeScript projects run a separate type check in CI; bundlers only strip types (tooling/typecheck-separately).
- Lint with the framework's accessibility plugin or compiler warnings (tooling/a11y-lint).
- Declare browser targets once, as a Baseline query; no blanket polyfills (perf/no-legacy-javascript).
- One formatter per file type; with ESLint and Prettier together, turn off ESLint's style rules (`eslint-config-prettier`).
- Pin the Node version to a supported LTS line (22, 24 or 26 in November 2026) in `.nvmrc` and `engines`.
- Never weaken a lint rule or a type to make a check pass; fix the code or explain the exception inline.
- Do not switch tools in passing (ESLint to Oxlint, Prettier to Biome); propose it separately.

Before larger changes, read the full skill: `.trae/skills/fe-tooling/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Continue

.frontend-skills/skills/fe-tooling/SKILL.mdskill
.frontend-skills/skills/fe-tooling/references/tooling.mdskill
.continue/rules/fe-tooling.mdplik reguł

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.continue/rules/fe-tooling.md

---
name: "Build, lint and format tooling"
description: "Sets up front-end tooling the way the project already does - package manager and lockfile, Vite 8, ESLint 10 flat config with accessibility plugins, Prettier 3 or Biome 2, Stylelint, TypeScript type checks, browserslist with Baseline targets, Node LTS. Use when adding or upgrading a linter, formatter, bundler or TypeScript, fixing a broken config or CI step, or when asked \"set up linting\"."
globs: ["**/package.json", "**/eslint.config.*", "**/vite.config.*", "**/tsconfig*.json", "**/biome.json", "**/.prettierrc*", "**/stylelint.config.*", "**/.browserslistrc"]
alwaysApply: false
---

# Build, lint and format tooling (frontend-skills)

- Run the project's scripts with its package manager; never install tools globally (tooling/use-project-scripts).
- Keep one committed lockfile; CI installs with the frozen command (tooling/one-lockfile).
- ESLint 10 reads only `eslint.config.*`; migrate `.eslintrc*` and `.eslintignore` (tooling/eslint-flat-config).
- TypeScript projects run a separate type check in CI; bundlers only strip types (tooling/typecheck-separately).
- Lint with the framework's accessibility plugin or compiler warnings (tooling/a11y-lint).
- Declare browser targets once, as a Baseline query; no blanket polyfills (perf/no-legacy-javascript).
- One formatter per file type; with ESLint and Prettier together, turn off ESLint's style rules (`eslint-config-prettier`).
- Pin the Node version to a supported LTS line (22, 24 or 26 in November 2026) in `.nvmrc` and `engines`.
- Never weaken a lint rule or a type to make a check pass; fix the code or explain the exception inline.
- Do not switch tools in passing (ESLint to Oxlint, Prettier to Biome); propose it separately.

Before larger changes, read the full skill: `.frontend-skills/skills/fe-tooling/SKILL.md`. Explain any rule id with `npx github:dawidolko/frontend-skills explain <id>`.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Amazon Q Developer

.frontend-skills/skills/fe-tooling/SKILL.mdskill
.frontend-skills/skills/fe-tooling/references/tooling.mdskill
.amazonq/rules/frontend-skills.mdblok instrukcji

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Amazon Q Developer: Amazon Q Developer IDE plugins reach end of support on 2027-04-30; AWS points to Kiro.

Amazon Q Developer nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

.amazonq/rules/frontend-skills.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

### Skills

- `fe-tooling` (Build, lint and format tooling): when editing `**/package.json`, `**/eslint.config.*`, `**/vite.config.*`, `**/tsconfig*.json`, `**/biome.json`, `**/.prettierrc*`, `**/stylelint.config.*`, `**/.browserslistrc`, first read `.frontend-skills/skills/fe-tooling/SKILL.md`.

Prawdziwy plik

Gdzie trafia fe-tooling dla: Aider

.frontend-skills/skills/fe-tooling/SKILL.mdskill
.frontend-skills/skills/fe-tooling/references/tooling.mdskill
CONVENTIONS.mdblok instrukcji
.aider.conf.ymlkonfiguracja

Dla każdego agenta także: .frontend-skills/profile.json, .frontend-skills/lessons.md i .frontend-skills/install.json.

Aider nie ma plików reguł zawężonych do typów plików; czyta skille i blok instrukcji.

Zaplanowane przez sam instalator dla przykładowego projektu React z repozytorium.

CONVENTIONS.md

## Front-end work (frontend-skills)

- Before front-end work, read `.frontend-skills/profile.json` (the stack) and `.frontend-skills/lessons.md` (confirmed conventions of this project; they win over any skill).
- Use the installed `fe-*` skill that matches the files you edit.
- After changing UI code, run `npx github:dawidolko/frontend-skills audit --changed --json` and fix findings at `serious` and above; `explain <rule id>` gives the reason, the source and the fix.
- Name rule ids (such as `a11y/img-alt`) in reviews and commit messages.

### Skills

- `fe-tooling` (Build, lint and format tooling): when editing `**/package.json`, `**/eslint.config.*`, `**/vite.config.*`, `**/tsconfig*.json`, `**/biome.json`, `**/.prettierrc*`, `**/stylelint.config.*`, `**/.browserslistrc`, first read `.frontend-skills/skills/fe-tooling/SKILL.md`.

Prawdziwy plik

Jak go używać

Po instalacji agent sam ładuje skill, gdy zadanie pasuje do jego opisu. Możesz też poprosić o niego własnymi słowami, na przykład:

Frazy z opisu skilla, po których agent go wybiera (po angielsku, jak w skillu):

set up linting

A żeby sprawdzić i poprawić pracę:

Użyj skilla fe-tooling na tym pliku.
Uruchom audyt front-endu na moich zmianach i popraw wszystko, co poważne.
Wyjaśnij tooling/use-project-scripts i popraw to tutaj.

Reguły, których uczy

tooling/use-project-scripts
Run checks through the project's own scripts and package manager; never install tools globally or switch package managers.
drobnaręczne
tooling/one-lockfile
A project has exactly one committed lockfile, and CI installs from it with the frozen command (npm ci, pnpm install --frozen-lockfile).
umiarkowanaręczne
tooling/eslint-flat-config
ESLint is configured in eslint.config.* (flat config); .eslintrc files and .eslintignore are migrated, not kept beside it.
umiarkowanaręczne
tooling/typecheck-separately
A TypeScript project runs a separate type check (tsc --noEmit, vue-tsc, svelte-check, astro check) in CI; the bundler does not.
umiarkowanaręczne
tooling/a11y-lint
The linter runs the framework's accessibility rules (jsx-a11y, vuejs-accessibility, angular-eslint template, Svelte a11y warnings).
drobnaręczne
perf/no-legacy-javascript
Do not ship polyfills and down-level transforms for features your target browsers already support; declare targets once.
drobnaw przeglądarce

Skrót reguł

Ta część jest kopiowana do zawężonego pliku reguł każdego agenta, więc musi być zrozumiała sama w sobie:

Run the project's scripts with its package manager; never install tools globally (tooling/use-project-scripts).
Keep one committed lockfile; CI installs with the frozen command (tooling/one-lockfile).
ESLint 10 reads only eslint.config.*; migrate .eslintrc* and .eslintignore (tooling/eslint-flat-config).
TypeScript projects run a separate type check in CI; bundlers only strip types (tooling/typecheck-separately).
Lint with the framework's accessibility plugin or compiler warnings (tooling/a11y-lint).
Declare browser targets once, as a Baseline query; no blanket polyfills (perf/no-legacy-javascript).
One formatter per file type; with ESLint and Prettier together, turn off ESLint's style rules (eslint-config-prettier).
Pin the Node version to a supported LTS line (22, 24 or 26 in November 2026) in .nvmrc and engines.
Never weaken a lint rule or a type to make a check pass; fix the code or explain the exception inline.
Do not switch tools in passing (ESLint to Oxlint, Prettier to Biome); propose it separately.

Kroki, które wykonuje agent

Read package.json scripts, the lockfile and config files first; the profile lists what was detected.
Fix configs in place: migrate ESLint to flat config with @eslint/migrate-config, move ignores into the config, keep one formatter config.
Add the missing CI steps in this order: install (frozen), lint, typecheck, test, build, frontend-skills audit.
For Vite 8 (Rolldown inside): remove the rolldown-vite alias, check plugins for Vite 8 support, set build.target or browserslist once.
Keep tool output short for agents: eslint --format compact, vitest run --reporter=dot, tsc --pretty false.

Jak agent sprawdza swoją pracę

npx github:dawidolko/frontend-skills audit runs the static rules; this skill's own rules are checked by reading the config files, as listed in ## Rules.
Run <pm> run lint, <pm> run typecheck, <pm> run build and read the first error, not the last.
npx github:dawidolko/frontend-skills doctor shows which agent files are installed and current.

Sprawdzane audytem

Testy statyczne tych reguł działają w audit; to prawdziwa sesja na przykładowym projekcie:

Nagranie terminala: audit wypisuje znaleziska według wagi z identyfikatorami reguł i miejscem plik:linia i kończy się błędem od progu serious. — `audit`: liczby według wagi, każda reguła z pierwszym miejscem, kod wyjścia.

Pliki referencyjne

references/tooling.md1519 tokenów

SKILL.md na GitHubie