Jakość

SEO and metadata

Gets pages found and shared correctly - titles, meta descriptions, canonical URLs, robots and noindex, status codes, sitemaps, hreflang, Open Graph and JSON-LD structured data, with the metadata API of Next.js, Nuxt, Astro, SvelteKit and Angular. Use when adding a page or route, a layout head, social previews, structured data, i18n URLs, or when asked "fix SEO" or "why is this not indexed".

fe-seo-metadatakażdego projektu webowego10 regułładowane zawsze: 93 tokeny; przy użyciu: 951 tokenów; w referencjach na żądanie: 1689 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-seo-metadata dla: Claude Code

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

---
paths:
  - "**/*.html"
  - "**/*.jsx"
  - "**/*.tsx"
  - "**/*.vue"
  - "**/*.svelte"
  - "**/*.astro"
  - "**/robots.txt"
  - "**/sitemap*.xml"
---

# SEO and metadata (frontend-skills)

Gets pages found and shared correctly - titles, meta descriptions, canonical URLs, robots and noindex, status codes, sitemaps, hreflang, Open Graph and JSON-LD structured data, with the metadata API of Next.js, Nuxt, Astro, SvelteKit and Angular. Use when adding a page or route, a layout head, social previews, structured data, i18n URLs, or when asked "fix SEO" or "why is this not indexed".

- Every page has its own title, topic first and site name last (seo/title-unique).
- Every indexable page has its own meta description (seo/meta-description).
- One absolute `rel="canonical"` per page, without a fragment (seo/canonical-valid).
- No `noindex` on pages that should rank; set robots per environment from configuration (seo/indexable).
- Missing pages return 404, moved pages 301 or 308; no soft 404s (seo/http-status).
- hreflang uses valid codes (`en-GB`, not `en_UK`), absolute URLs, every version listed, plus `x-default` (seo/hreflang-valid).
- JSON-LD is valid JSON with the schema.org context, describes only visible content, and uses supported types (seo/jsonld-valid, seo/jsonld-type-supported).
- Social tags use absolute https URLs for images and URLs (seo/og-absolute-url).
- Links are `<a href>` with real URLs and descriptive text; never script-only links (a11y/link-is-link).
- Metadata, canonical and robots are in the server HTML, not added by client script.
- Never claim a ranking result; say what was fixed and how to verify it in Search Console.

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

Prawdziwy plik

Gdzie trafia fe-seo-metadata dla: OpenAI Codex

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

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

---
description: Gets pages found and shared correctly - titles, meta descriptions, canonical URLs, robots and noindex, status codes, sitemaps, hreflang, Open Graph and JSON-LD structured data, with the metadata API of Next.js, Nuxt, Astro, SvelteKit and Angular. Use when adding a page or route, a layout head, social previews, structured data, i18n URLs, or when asked "fix SEO" or "why is this not indexed".
globs: **/*.html, **/*.jsx, **/*.tsx, **/*.vue, **/*.svelte, **/*.astro, **/robots.txt, **/sitemap*.xml
alwaysApply: false
---

# SEO and metadata (frontend-skills)

- Every page has its own title, topic first and site name last (seo/title-unique).
- Every indexable page has its own meta description (seo/meta-description).
- One absolute `rel="canonical"` per page, without a fragment (seo/canonical-valid).
- No `noindex` on pages that should rank; set robots per environment from configuration (seo/indexable).
- Missing pages return 404, moved pages 301 or 308; no soft 404s (seo/http-status).
- hreflang uses valid codes (`en-GB`, not `en_UK`), absolute URLs, every version listed, plus `x-default` (seo/hreflang-valid).
- JSON-LD is valid JSON with the schema.org context, describes only visible content, and uses supported types (seo/jsonld-valid, seo/jsonld-type-supported).
- Social tags use absolute https URLs for images and URLs (seo/og-absolute-url).
- Links are `<a href>` with real URLs and descriptive text; never script-only links (a11y/link-is-link).
- Metadata, canonical and robots are in the server HTML, not added by client script.
- Never claim a ranking result; say what was fixed and how to verify it in Search Console.

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

Prawdziwy plik

Gdzie trafia fe-seo-metadata dla: GitHub Copilot

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

---
applyTo: "**/*.html,**/*.jsx,**/*.tsx,**/*.vue,**/*.svelte,**/*.astro,**/robots.txt,**/sitemap*.xml"
description: "Gets pages found and shared correctly - titles, meta descriptions, canonical URLs, robots and noindex, status codes, sitemaps, hreflang, Open Graph and JSON-LD structured data, with the metadata API of Next.js, Nuxt, Astro, SvelteKit and Angular. Use when adding a page or route, a layout head, social previews, structured data, i18n URLs, or when asked \"fix SEO\" or \"why is this not indexed\"."
---

# SEO and metadata (frontend-skills)

- Every page has its own title, topic first and site name last (seo/title-unique).
- Every indexable page has its own meta description (seo/meta-description).
- One absolute `rel="canonical"` per page, without a fragment (seo/canonical-valid).
- No `noindex` on pages that should rank; set robots per environment from configuration (seo/indexable).
- Missing pages return 404, moved pages 301 or 308; no soft 404s (seo/http-status).
- hreflang uses valid codes (`en-GB`, not `en_UK`), absolute URLs, every version listed, plus `x-default` (seo/hreflang-valid).
- JSON-LD is valid JSON with the schema.org context, describes only visible content, and uses supported types (seo/jsonld-valid, seo/jsonld-type-supported).
- Social tags use absolute https URLs for images and URLs (seo/og-absolute-url).
- Links are `<a href>` with real URLs and descriptive text; never script-only links (a11y/link-is-link).
- Metadata, canonical and robots are in the server HTML, not added by client script.
- Never claim a ranking result; say what was fixed and how to verify it in Search Console.

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

Prawdziwy plik

Gdzie trafia fe-seo-metadata dla: Gemini CLI

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

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

---
trigger: glob
globs: "**/*.html, **/*.jsx, **/*.tsx, **/*.vue, **/*.svelte, **/*.astro, **/robots.txt, **/sitemap*.xml"
description: "Gets pages found and shared correctly - titles, meta descriptions, canonical URLs, robots and noindex, status codes, sitemaps, hreflang, Open Graph and JSON-LD structured data, with the metadata API of Next.js, Nuxt, Astro, SvelteKit and Angular. Use when adding a page or route, a layout head, social previews, structured data, i18n URLs, or when asked \"fix SEO\" or \"why is this not indexed\"."
---

# SEO and metadata (frontend-skills)

- Every page has its own title, topic first and site name last (seo/title-unique).
- Every indexable page has its own meta description (seo/meta-description).
- One absolute `rel="canonical"` per page, without a fragment (seo/canonical-valid).
- No `noindex` on pages that should rank; set robots per environment from configuration (seo/indexable).
- Missing pages return 404, moved pages 301 or 308; no soft 404s (seo/http-status).
- hreflang uses valid codes (`en-GB`, not `en_UK`), absolute URLs, every version listed, plus `x-default` (seo/hreflang-valid).
- JSON-LD is valid JSON with the schema.org context, describes only visible content, and uses supported types (seo/jsonld-valid, seo/jsonld-type-supported).
- Social tags use absolute https URLs for images and URLs (seo/og-absolute-url).
- Links are `<a href>` with real URLs and descriptive text; never script-only links (a11y/link-is-link).
- Metadata, canonical and robots are in the server HTML, not added by client script.
- Never claim a ranking result; say what was fixed and how to verify it in Search Console.

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

Prawdziwy plik

Gdzie trafia fe-seo-metadata dla: Devin / Windsurf

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

---
trigger: glob
globs: "**/*.html,**/*.jsx,**/*.tsx,**/*.vue,**/*.svelte,**/*.astro,**/robots.txt,**/sitemap*.xml"
---

# SEO and metadata (frontend-skills)

Gets pages found and shared correctly - titles, meta descriptions, canonical URLs, robots and noindex, status codes, sitemaps, hreflang, Open Graph and JSON-LD structured data, with the metadata API of Next.js, Nuxt, Astro, SvelteKit and Angular. Use when adding a page or route, a layout head, social previews, structured data, i18n URLs, or when asked "fix SEO" or "why is this not indexed".

- Every page has its own title, topic first and site name last (seo/title-unique).
- Every indexable page has its own meta description (seo/meta-description).
- One absolute `rel="canonical"` per page, without a fragment (seo/canonical-valid).
- No `noindex` on pages that should rank; set robots per environment from configuration (seo/indexable).
- Missing pages return 404, moved pages 301 or 308; no soft 404s (seo/http-status).
- hreflang uses valid codes (`en-GB`, not `en_UK`), absolute URLs, every version listed, plus `x-default` (seo/hreflang-valid).
- JSON-LD is valid JSON with the schema.org context, describes only visible content, and uses supported types (seo/jsonld-valid, seo/jsonld-type-supported).
- Social tags use absolute https URLs for images and URLs (seo/og-absolute-url).
- Links are `<a href>` with real URLs and descriptive text; never script-only links (a11y/link-is-link).
- Metadata, canonical and robots are in the server HTML, not added by client script.
- Never claim a ranking result; say what was fixed and how to verify it in Search Console.

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

Prawdziwy plik

Gdzie trafia fe-seo-metadata dla: OpenCode

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

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

---
paths:
  - "**/*.html"
  - "**/*.jsx"
  - "**/*.tsx"
  - "**/*.vue"
  - "**/*.svelte"
  - "**/*.astro"
  - "**/robots.txt"
  - "**/sitemap*.xml"
---

# SEO and metadata (frontend-skills)

Gets pages found and shared correctly - titles, meta descriptions, canonical URLs, robots and noindex, status codes, sitemaps, hreflang, Open Graph and JSON-LD structured data, with the metadata API of Next.js, Nuxt, Astro, SvelteKit and Angular. Use when adding a page or route, a layout head, social previews, structured data, i18n URLs, or when asked "fix SEO" or "why is this not indexed".

- Every page has its own title, topic first and site name last (seo/title-unique).
- Every indexable page has its own meta description (seo/meta-description).
- One absolute `rel="canonical"` per page, without a fragment (seo/canonical-valid).
- No `noindex` on pages that should rank; set robots per environment from configuration (seo/indexable).
- Missing pages return 404, moved pages 301 or 308; no soft 404s (seo/http-status).
- hreflang uses valid codes (`en-GB`, not `en_UK`), absolute URLs, every version listed, plus `x-default` (seo/hreflang-valid).
- JSON-LD is valid JSON with the schema.org context, describes only visible content, and uses supported types (seo/jsonld-valid, seo/jsonld-type-supported).
- Social tags use absolute https URLs for images and URLs (seo/og-absolute-url).
- Links are `<a href>` with real URLs and descriptive text; never script-only links (a11y/link-is-link).
- Metadata, canonical and robots are in the server HTML, not added by client script.
- Never claim a ranking result; say what was fixed and how to verify it in Search Console.

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

Prawdziwy plik

Gdzie trafia fe-seo-metadata dla: Zed

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

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

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

---
inclusion: fileMatch
fileMatchPattern: ["**/*.html", "**/*.jsx", "**/*.tsx", "**/*.vue", "**/*.svelte", "**/*.astro", "**/robots.txt", "**/sitemap*.xml"]
---

# SEO and metadata (frontend-skills)

Gets pages found and shared correctly - titles, meta descriptions, canonical URLs, robots and noindex, status codes, sitemaps, hreflang, Open Graph and JSON-LD structured data, with the metadata API of Next.js, Nuxt, Astro, SvelteKit and Angular. Use when adding a page or route, a layout head, social previews, structured data, i18n URLs, or when asked "fix SEO" or "why is this not indexed".

- Every page has its own title, topic first and site name last (seo/title-unique).
- Every indexable page has its own meta description (seo/meta-description).
- One absolute `rel="canonical"` per page, without a fragment (seo/canonical-valid).
- No `noindex` on pages that should rank; set robots per environment from configuration (seo/indexable).
- Missing pages return 404, moved pages 301 or 308; no soft 404s (seo/http-status).
- hreflang uses valid codes (`en-GB`, not `en_UK`), absolute URLs, every version listed, plus `x-default` (seo/hreflang-valid).
- JSON-LD is valid JSON with the schema.org context, describes only visible content, and uses supported types (seo/jsonld-valid, seo/jsonld-type-supported).
- Social tags use absolute https URLs for images and URLs (seo/og-absolute-url).
- Links are `<a href>` with real URLs and descriptive text; never script-only links (a11y/link-is-link).
- Metadata, canonical and robots are in the server HTML, not added by client script.
- Never claim a ranking result; say what was fixed and how to verify it in Search Console.

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

Prawdziwy plik

Gdzie trafia fe-seo-metadata dla: Augment

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

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

---
description: "Gets pages found and shared correctly - titles, meta descriptions, canonical URLs, robots and noindex, status codes, sitemaps, hreflang, Open Graph and JSON-LD structured data, with the metadata API of Next.js, Nuxt, Astro, SvelteKit and Angular. Use when adding a page or route, a layout head, social previews, structured data, i18n URLs, or when asked \"fix SEO\" or \"why is this not indexed\"."
globs: **/*.html,**/*.jsx,**/*.tsx,**/*.vue,**/*.svelte,**/*.astro,**/robots.txt,**/sitemap*.xml
alwaysApply: false
---

# SEO and metadata (frontend-skills)

- Every page has its own title, topic first and site name last (seo/title-unique).
- Every indexable page has its own meta description (seo/meta-description).
- One absolute `rel="canonical"` per page, without a fragment (seo/canonical-valid).
- No `noindex` on pages that should rank; set robots per environment from configuration (seo/indexable).
- Missing pages return 404, moved pages 301 or 308; no soft 404s (seo/http-status).
- hreflang uses valid codes (`en-GB`, not `en_UK`), absolute URLs, every version listed, plus `x-default` (seo/hreflang-valid).
- JSON-LD is valid JSON with the schema.org context, describes only visible content, and uses supported types (seo/jsonld-valid, seo/jsonld-type-supported).
- Social tags use absolute https URLs for images and URLs (seo/og-absolute-url).
- Links are `<a href>` with real URLs and descriptive text; never script-only links (a11y/link-is-link).
- Metadata, canonical and robots are in the server HTML, not added by client script.
- Never claim a ranking result; say what was fixed and how to verify it in Search Console.

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

Prawdziwy plik

Gdzie trafia fe-seo-metadata dla: Continue

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

---
name: "SEO and metadata"
description: "Gets pages found and shared correctly - titles, meta descriptions, canonical URLs, robots and noindex, status codes, sitemaps, hreflang, Open Graph and JSON-LD structured data, with the metadata API of Next.js, Nuxt, Astro, SvelteKit and Angular. Use when adding a page or route, a layout head, social previews, structured data, i18n URLs, or when asked \"fix SEO\" or \"why is this not indexed\"."
globs: ["**/*.html", "**/*.jsx", "**/*.tsx", "**/*.vue", "**/*.svelte", "**/*.astro", "**/robots.txt", "**/sitemap*.xml"]
alwaysApply: false
---

# SEO and metadata (frontend-skills)

- Every page has its own title, topic first and site name last (seo/title-unique).
- Every indexable page has its own meta description (seo/meta-description).
- One absolute `rel="canonical"` per page, without a fragment (seo/canonical-valid).
- No `noindex` on pages that should rank; set robots per environment from configuration (seo/indexable).
- Missing pages return 404, moved pages 301 or 308; no soft 404s (seo/http-status).
- hreflang uses valid codes (`en-GB`, not `en_UK`), absolute URLs, every version listed, plus `x-default` (seo/hreflang-valid).
- JSON-LD is valid JSON with the schema.org context, describes only visible content, and uses supported types (seo/jsonld-valid, seo/jsonld-type-supported).
- Social tags use absolute https URLs for images and URLs (seo/og-absolute-url).
- Links are `<a href>` with real URLs and descriptive text; never script-only links (a11y/link-is-link).
- Metadata, canonical and robots are in the server HTML, not added by client script.
- Never claim a ranking result; say what was fixed and how to verify it in Search Console.

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

Prawdziwy plik

Gdzie trafia fe-seo-metadata dla: Amazon Q Developer

.frontend-skills/skills/fe-seo-metadata/SKILL.mdskill
.frontend-skills/skills/fe-seo-metadata/references/seo.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-seo-metadata` (SEO and metadata): when editing `**/*.html`, `**/*.jsx`, `**/*.tsx`, `**/*.vue`, `**/*.svelte`, `**/*.astro`, `**/robots.txt`, `**/sitemap*.xml`, first read `.frontend-skills/skills/fe-seo-metadata/SKILL.md`.

Prawdziwy plik

Gdzie trafia fe-seo-metadata dla: Aider

.frontend-skills/skills/fe-seo-metadata/SKILL.mdskill
.frontend-skills/skills/fe-seo-metadata/references/seo.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-seo-metadata` (SEO and metadata): when editing `**/*.html`, `**/*.jsx`, `**/*.tsx`, `**/*.vue`, `**/*.svelte`, `**/*.astro`, `**/robots.txt`, `**/sitemap*.xml`, first read `.frontend-skills/skills/fe-seo-metadata/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):

fix SEO
why is this not indexed

A żeby sprawdzić i poprawić pracę:

Użyj skilla fe-seo-metadata na tym pliku.
Uruchom audyt front-endu na moich zmianach i popraw wszystko, co poważne.
Wyjaśnij seo/title-unique i popraw to tutaj.

Reguły, których uczy

seo/title-unique
Each page has its own descriptive title, page topic first and site name last, in the page's language.
drobnaręczne
seo/meta-description
Each indexable page has its own meta description that summarises that page.
umiarkowanastatyczne
seo/canonical-valid
A page has at most one rel="canonical", in the head, with an absolute URL of an indexable page and no fragment.
umiarkowanastatyczne
seo/indexable
Pages meant to rank are crawlable and carry no noindex (meta robots or X-Robots-Tag) in production.
poważnaw przeglądarce
seo/http-status
Missing pages return 404 or 410, moved pages 301 or 308, and a client-rendered error view is not served with 200.
umiarkowanaw przeglądarce
seo/hreflang-valid
hreflang values are ISO 639-1 language codes with an optional script and ISO 3166-1 region (or x-default), linking absolute URLs.
umiarkowanastatyczne
seo/jsonld-valid
Every JSON-LD block is valid JSON with "@context" "https://schema.org" and a schema.org @type.
umiarkowanastatyczne
seo/jsonld-type-supported
Structured data for rich results uses types in Google's current search gallery, not retired ones such as FAQPage or HowTo.
drobnastatyczne
seo/og-absolute-url
Open Graph and social image and URL tags (og:image, og:url, twitter:image) use absolute https URLs.
drobnastatyczne
a11y/link-is-link
An <a> is a real link with an href; an action is a <button>, never <a> without href, href="#" or javascript:.
poważnastatyczneWCAG 2.1.1, 4.1.2

Skrót reguł

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

Every page has its own title, topic first and site name last (seo/title-unique).
Every indexable page has its own meta description (seo/meta-description).
One absolute rel="canonical" per page, without a fragment (seo/canonical-valid).
No noindex on pages that should rank; set robots per environment from configuration (seo/indexable).
Missing pages return 404, moved pages 301 or 308; no soft 404s (seo/http-status).
hreflang uses valid codes (en-GB, not en_UK), absolute URLs, every version listed, plus x-default (seo/hreflang-valid).
JSON-LD is valid JSON with the schema.org context, describes only visible content, and uses supported types (seo/jsonld-valid, seo/jsonld-type-supported).
Social tags use absolute https URLs for images and URLs (seo/og-absolute-url).
Links are <a href> with real URLs and descriptive text; never script-only links (a11y/link-is-link).
Metadata, canonical and robots are in the server HTML, not added by client script.
Never claim a ranking result; say what was fixed and how to verify it in Search Console.

Kroki, które wykonuje agent

Find where the head is built: root layout plus per-route metadata (Next.js metadata/generateMetadata, Nuxt useSeoMeta, Astro layout props, SvelteKit <svelte:head>, Angular Title/Meta and route title).
Set defaults once in the root layout (site name template, Open Graph defaults, canonical origin from config); override per route.
Generate sitemap.xml and robots.txt from the routes (Next.js app/sitemap.ts and app/robots.ts, @astrojs/sitemap, @nuxtjs/sitemap), with canonical URLs only.
For multilingual sites, generate hreflang from the i18n configuration, and keep <html lang> equal to the page language.
Add structured data as an object serialised with JSON.stringify (escape <), only for types in Google's current gallery.

Jak agent sprawdza swoją pracę

npx github:dawidolko/frontend-skills audit --changed finds missing descriptions in documents, bad canonicals, invalid hreflang, broken JSON-LD, retired rich-result types, relative social URLs and script-only links.
audit --url <page> runs Lighthouse SEO (crawlable, status code, title, description, link text, hreflang, canonical).
By hand: view the page source (not the DOM) for title, description, canonical and robots; test structured data with the Rich Results Test; inspect a URL in Search Console.

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/seo.md1689 tokenów

SKILL.md na GitHubie