Praca z narzędziem

Fix findings

Fixes front-end audit findings by rule id - smallest correct change first, shared components before pages, the rule's own fix and source, re-running audit --changed after each fix, and never suppressing a finding without the rule id and a reason. Use when asked to fix audit findings, a rule id such as a11y/input-label, the problems in frontend-report.md, or "make the audit pass".

fe-fixkażdego projektu webowego2 regułyładowane zawsze: 90 tokenów; przy użyciu: 670 tokenów; w referencjach na żądanie: 814 tokenów.

Instalacja

init instaluje ten skill, gdy projekt używa: każdego projektu webowego. 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-fix dla: Claude Code

.claude/skills/fe-fix/SKILL.mdskill
.claude/skills/fe-fix/references/fixing.mdskill
.claude/rules/fe-fix.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-fix.md

---
paths:
  - "**/frontend-report.md"
  - "**/.frontend-skills/**"
---

# Fix findings (frontend-skills)

Fixes front-end audit findings by rule id - smallest correct change first, shared components before pages, the rule's own fix and source, re-running audit --changed after each fix, and never suppressing a finding without the rule id and a reason. Use when asked to fix audit findings, a rule id such as a11y/input-label, the problems in frontend-report.md, or "make the audit pass".

- Work from the audit, by rule id: `npx github:dawidolko/frontend-skills audit --json`, then `explain <id>` for the fix and source.
- Fix the cause in the shared component, layout or token, not each page that uses it.
- Make the smallest change that fixes the rule; do not refactor or restyle around it.
- Use the project's helpers and components (`profile.helpers`, lessons) in the fix.
- After each fix, run `audit --changed` and the project's lint and tests (tooling/use-project-scripts).
- Never suppress to pass: an `fs-ignore` names the rule id and a reason, or the finding stays (tooling/ignore-with-reason).
- Never weaken `audit.failOn`, budgets or a rule to make the audit pass.
- A static fix that needs judgement (alt text wording, error message text, labels) gets a short note for the person to confirm.
- Fixing one finding must not create another: check the rule ids of the skill for that area.

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

Prawdziwy plik

Gdzie trafia fe-fix dla: OpenAI Codex

.agents/skills/fe-fix/SKILL.mdskill
.agents/skills/fe-fix/references/fixing.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-fix dla: Cursor

.agents/skills/fe-fix/SKILL.mdskill
.agents/skills/fe-fix/references/fixing.mdskill
.cursor/rules/fe-fix.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-fix.mdc

---
description: Fixes front-end audit findings by rule id - smallest correct change first, shared components before pages, the rule's own fix and source, re-running audit --changed after each fix, and never suppressing a finding without the rule id and a reason. Use when asked to fix audit findings, a rule id such as a11y/input-label, the problems in frontend-report.md, or "make the audit pass".
globs: **/frontend-report.md, **/.frontend-skills/**
alwaysApply: false
---

# Fix findings (frontend-skills)

- Work from the audit, by rule id: `npx github:dawidolko/frontend-skills audit --json`, then `explain <id>` for the fix and source.
- Fix the cause in the shared component, layout or token, not each page that uses it.
- Make the smallest change that fixes the rule; do not refactor or restyle around it.
- Use the project's helpers and components (`profile.helpers`, lessons) in the fix.
- After each fix, run `audit --changed` and the project's lint and tests (tooling/use-project-scripts).
- Never suppress to pass: an `fs-ignore` names the rule id and a reason, or the finding stays (tooling/ignore-with-reason).
- Never weaken `audit.failOn`, budgets or a rule to make the audit pass.
- A static fix that needs judgement (alt text wording, error message text, labels) gets a short note for the person to confirm.
- Fixing one finding must not create another: check the rule ids of the skill for that area.

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

Prawdziwy plik

Gdzie trafia fe-fix dla: GitHub Copilot

.agents/skills/fe-fix/SKILL.mdskill
.agents/skills/fe-fix/references/fixing.mdskill
.github/instructions/fe-fix.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-fix.instructions.md

---
applyTo: "**/frontend-report.md,**/.frontend-skills/**"
description: "Fixes front-end audit findings by rule id - smallest correct change first, shared components before pages, the rule's own fix and source, re-running audit --changed after each fix, and never suppressing a finding without the rule id and a reason. Use when asked to fix audit findings, a rule id such as a11y/input-label, the problems in frontend-report.md, or \"make the audit pass\"."
---

# Fix findings (frontend-skills)

- Work from the audit, by rule id: `npx github:dawidolko/frontend-skills audit --json`, then `explain <id>` for the fix and source.
- Fix the cause in the shared component, layout or token, not each page that uses it.
- Make the smallest change that fixes the rule; do not refactor or restyle around it.
- Use the project's helpers and components (`profile.helpers`, lessons) in the fix.
- After each fix, run `audit --changed` and the project's lint and tests (tooling/use-project-scripts).
- Never suppress to pass: an `fs-ignore` names the rule id and a reason, or the finding stays (tooling/ignore-with-reason).
- Never weaken `audit.failOn`, budgets or a rule to make the audit pass.
- A static fix that needs judgement (alt text wording, error message text, labels) gets a short note for the person to confirm.
- Fixing one finding must not create another: check the rule ids of the skill for that area.

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

Prawdziwy plik

Gdzie trafia fe-fix dla: Gemini CLI

.agents/skills/fe-fix/SKILL.mdskill
.agents/skills/fe-fix/references/fixing.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-fix dla: Antigravity CLI

.agents/skills/fe-fix/SKILL.mdskill
.agents/skills/fe-fix/references/fixing.mdskill
.agents/rules/fe-fix.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-fix.md

---
trigger: glob
globs: "**/frontend-report.md, **/.frontend-skills/**"
description: "Fixes front-end audit findings by rule id - smallest correct change first, shared components before pages, the rule's own fix and source, re-running audit --changed after each fix, and never suppressing a finding without the rule id and a reason. Use when asked to fix audit findings, a rule id such as a11y/input-label, the problems in frontend-report.md, or \"make the audit pass\"."
---

# Fix findings (frontend-skills)

- Work from the audit, by rule id: `npx github:dawidolko/frontend-skills audit --json`, then `explain <id>` for the fix and source.
- Fix the cause in the shared component, layout or token, not each page that uses it.
- Make the smallest change that fixes the rule; do not refactor or restyle around it.
- Use the project's helpers and components (`profile.helpers`, lessons) in the fix.
- After each fix, run `audit --changed` and the project's lint and tests (tooling/use-project-scripts).
- Never suppress to pass: an `fs-ignore` names the rule id and a reason, or the finding stays (tooling/ignore-with-reason).
- Never weaken `audit.failOn`, budgets or a rule to make the audit pass.
- A static fix that needs judgement (alt text wording, error message text, labels) gets a short note for the person to confirm.
- Fixing one finding must not create another: check the rule ids of the skill for that area.

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

Prawdziwy plik

Gdzie trafia fe-fix dla: Devin / Windsurf

.agents/skills/fe-fix/SKILL.mdskill
.agents/skills/fe-fix/references/fixing.mdskill
.devin/rules/fe-fix.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-fix.md

---
trigger: glob
globs: "**/frontend-report.md,**/.frontend-skills/**"
---

# Fix findings (frontend-skills)

Fixes front-end audit findings by rule id - smallest correct change first, shared components before pages, the rule's own fix and source, re-running audit --changed after each fix, and never suppressing a finding without the rule id and a reason. Use when asked to fix audit findings, a rule id such as a11y/input-label, the problems in frontend-report.md, or "make the audit pass".

- Work from the audit, by rule id: `npx github:dawidolko/frontend-skills audit --json`, then `explain <id>` for the fix and source.
- Fix the cause in the shared component, layout or token, not each page that uses it.
- Make the smallest change that fixes the rule; do not refactor or restyle around it.
- Use the project's helpers and components (`profile.helpers`, lessons) in the fix.
- After each fix, run `audit --changed` and the project's lint and tests (tooling/use-project-scripts).
- Never suppress to pass: an `fs-ignore` names the rule id and a reason, or the finding stays (tooling/ignore-with-reason).
- Never weaken `audit.failOn`, budgets or a rule to make the audit pass.
- A static fix that needs judgement (alt text wording, error message text, labels) gets a short note for the person to confirm.
- Fixing one finding must not create another: check the rule ids of the skill for that area.

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

Prawdziwy plik

Gdzie trafia fe-fix dla: OpenCode

.agents/skills/fe-fix/SKILL.mdskill
.agents/skills/fe-fix/references/fixing.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-fix dla: Cline

.claude/skills/fe-fix/SKILL.mdskill
.claude/skills/fe-fix/references/fixing.mdskill
.clinerules/fe-fix.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-fix.md

---
paths:
  - "**/frontend-report.md"
  - "**/.frontend-skills/**"
---

# Fix findings (frontend-skills)

Fixes front-end audit findings by rule id - smallest correct change first, shared components before pages, the rule's own fix and source, re-running audit --changed after each fix, and never suppressing a finding without the rule id and a reason. Use when asked to fix audit findings, a rule id such as a11y/input-label, the problems in frontend-report.md, or "make the audit pass".

- Work from the audit, by rule id: `npx github:dawidolko/frontend-skills audit --json`, then `explain <id>` for the fix and source.
- Fix the cause in the shared component, layout or token, not each page that uses it.
- Make the smallest change that fixes the rule; do not refactor or restyle around it.
- Use the project's helpers and components (`profile.helpers`, lessons) in the fix.
- After each fix, run `audit --changed` and the project's lint and tests (tooling/use-project-scripts).
- Never suppress to pass: an `fs-ignore` names the rule id and a reason, or the finding stays (tooling/ignore-with-reason).
- Never weaken `audit.failOn`, budgets or a rule to make the audit pass.
- A static fix that needs judgement (alt text wording, error message text, labels) gets a short note for the person to confirm.
- Fixing one finding must not create another: check the rule ids of the skill for that area.

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

Prawdziwy plik

Gdzie trafia fe-fix dla: Zed

.agents/skills/fe-fix/SKILL.mdskill
.agents/skills/fe-fix/references/fixing.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-fix dla: JetBrains Junie

.agents/skills/fe-fix/SKILL.mdskill
.agents/skills/fe-fix/references/fixing.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-fix dla: Kiro

.kiro/skills/fe-fix/SKILL.mdskill
.kiro/skills/fe-fix/references/fixing.mdskill
.kiro/steering/fe-fix.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-fix.md

---
inclusion: fileMatch
fileMatchPattern: ["**/frontend-report.md", "**/.frontend-skills/**"]
---

# Fix findings (frontend-skills)

Fixes front-end audit findings by rule id - smallest correct change first, shared components before pages, the rule's own fix and source, re-running audit --changed after each fix, and never suppressing a finding without the rule id and a reason. Use when asked to fix audit findings, a rule id such as a11y/input-label, the problems in frontend-report.md, or "make the audit pass".

- Work from the audit, by rule id: `npx github:dawidolko/frontend-skills audit --json`, then `explain <id>` for the fix and source.
- Fix the cause in the shared component, layout or token, not each page that uses it.
- Make the smallest change that fixes the rule; do not refactor or restyle around it.
- Use the project's helpers and components (`profile.helpers`, lessons) in the fix.
- After each fix, run `audit --changed` and the project's lint and tests (tooling/use-project-scripts).
- Never suppress to pass: an `fs-ignore` names the rule id and a reason, or the finding stays (tooling/ignore-with-reason).
- Never weaken `audit.failOn`, budgets or a rule to make the audit pass.
- A static fix that needs judgement (alt text wording, error message text, labels) gets a short note for the person to confirm.
- Fixing one finding must not create another: check the rule ids of the skill for that area.

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

Prawdziwy plik

Gdzie trafia fe-fix dla: Augment

.agents/skills/fe-fix/SKILL.mdskill
.agents/skills/fe-fix/references/fixing.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-fix dla: Trae

.trae/skills/fe-fix/SKILL.mdskill
.trae/skills/fe-fix/references/fixing.mdskill
.trae/rules/fe-fix.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-fix.md

---
description: "Fixes front-end audit findings by rule id - smallest correct change first, shared components before pages, the rule's own fix and source, re-running audit --changed after each fix, and never suppressing a finding without the rule id and a reason. Use when asked to fix audit findings, a rule id such as a11y/input-label, the problems in frontend-report.md, or \"make the audit pass\"."
globs: **/frontend-report.md,**/.frontend-skills/**
alwaysApply: false
---

# Fix findings (frontend-skills)

- Work from the audit, by rule id: `npx github:dawidolko/frontend-skills audit --json`, then `explain <id>` for the fix and source.
- Fix the cause in the shared component, layout or token, not each page that uses it.
- Make the smallest change that fixes the rule; do not refactor or restyle around it.
- Use the project's helpers and components (`profile.helpers`, lessons) in the fix.
- After each fix, run `audit --changed` and the project's lint and tests (tooling/use-project-scripts).
- Never suppress to pass: an `fs-ignore` names the rule id and a reason, or the finding stays (tooling/ignore-with-reason).
- Never weaken `audit.failOn`, budgets or a rule to make the audit pass.
- A static fix that needs judgement (alt text wording, error message text, labels) gets a short note for the person to confirm.
- Fixing one finding must not create another: check the rule ids of the skill for that area.

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

Prawdziwy plik

Gdzie trafia fe-fix dla: Continue

.frontend-skills/skills/fe-fix/SKILL.mdskill
.frontend-skills/skills/fe-fix/references/fixing.mdskill
.continue/rules/fe-fix.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-fix.md

---
name: "Fix findings"
description: "Fixes front-end audit findings by rule id - smallest correct change first, shared components before pages, the rule's own fix and source, re-running audit --changed after each fix, and never suppressing a finding without the rule id and a reason. Use when asked to fix audit findings, a rule id such as a11y/input-label, the problems in frontend-report.md, or \"make the audit pass\"."
globs: ["**/frontend-report.md", "**/.frontend-skills/**"]
alwaysApply: false
---

# Fix findings (frontend-skills)

- Work from the audit, by rule id: `npx github:dawidolko/frontend-skills audit --json`, then `explain <id>` for the fix and source.
- Fix the cause in the shared component, layout or token, not each page that uses it.
- Make the smallest change that fixes the rule; do not refactor or restyle around it.
- Use the project's helpers and components (`profile.helpers`, lessons) in the fix.
- After each fix, run `audit --changed` and the project's lint and tests (tooling/use-project-scripts).
- Never suppress to pass: an `fs-ignore` names the rule id and a reason, or the finding stays (tooling/ignore-with-reason).
- Never weaken `audit.failOn`, budgets or a rule to make the audit pass.
- A static fix that needs judgement (alt text wording, error message text, labels) gets a short note for the person to confirm.
- Fixing one finding must not create another: check the rule ids of the skill for that area.

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

Prawdziwy plik

Gdzie trafia fe-fix dla: Amazon Q Developer

.frontend-skills/skills/fe-fix/SKILL.mdskill
.frontend-skills/skills/fe-fix/references/fixing.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-fix` (Fix findings): when editing `**/frontend-report.md`, `**/.frontend-skills/**`, first read `.frontend-skills/skills/fe-fix/SKILL.md`.

Prawdziwy plik

Gdzie trafia fe-fix dla: Aider

.frontend-skills/skills/fe-fix/SKILL.mdskill
.frontend-skills/skills/fe-fix/references/fixing.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-fix` (Fix findings): when editing `**/frontend-report.md`, `**/.frontend-skills/**`, first read `.frontend-skills/skills/fe-fix/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):

make the audit pass

A żeby sprawdzić i poprawić pracę:

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

Reguły, których uczy

tooling/ignore-with-reason
Every fs-ignore comment names the rule id it silences and says why; a bare fs-ignore silences every rule on the line.
umiarkowanaręczne
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

Skrót reguł

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

Work from the audit, by rule id: npx github:dawidolko/frontend-skills audit --json, then explain <id> for the fix and source.
Fix the cause in the shared component, layout or token, not each page that uses it.
Make the smallest change that fixes the rule; do not refactor or restyle around it.
Use the project's helpers and components (profile.helpers, lessons) in the fix.
After each fix, run audit --changed and the project's lint and tests (tooling/use-project-scripts).
Never suppress to pass: an fs-ignore names the rule id and a reason, or the finding stays (tooling/ignore-with-reason).
Never weaken audit.failOn, budgets or a rule to make the audit pass.
A static fix that needs judgement (alt text wording, error message text, labels) gets a short note for the person to confirm.
Fixing one finding must not create another: check the rule ids of the skill for that area.

Kroki, które wykonuje agent

Run the audit and take findings in the order critical, serious, moderate, minor; within a level, the rule with the most locations first.
For each rule: explain <id>, open the first location, find whether it comes from a shared component, and fix it there.
Load the skill that owns the rule (its skill: in explain) for the patterns of this stack.
Run npx github:dawidolko/frontend-skills audit --changed --json and the project's lint and tests; repeat until the rule is gone.
Report: rule ids fixed, files changed, findings left with the reason, and anything a person must check (browser and manual rules).

Jak agent sprawdza swoją pracę

audit --changed shows no finding of the fixed rule ids in the changed files.
git diff shows only changes that serve the fixed rules.
Every new fs-ignore has a rule id and a reason.

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/fixing.md814 tokenów

SKILL.md na GitHubie