kapishdimakapishdima/soundcn/.agents/skills/fixing-metadata/SKILL.md

fixing-metadata

Skill864 starsChanged 9 months agoMITView on GitHub

Ship correct, complete metadata.

We split this skill into the rules it gives an agent

20 rules. 18 are common, 1 is distinctive, and 1 is very specific to this project.

18
Common
Most of the 8 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Do not introduce new frameworks or SEO libraries unless explicitly requested.
line 21
Common:
do not emit duplicate title, description, canonical, or robots tags
line 52
Common:
every page must have safe defaults for title and description
line 55
Common:
every page must have a title
line 59
Common:
use a consistent title format across the site
line 60
Common:
keep titles short and readable, avoid stuffing
line 61
Common:
use noindex only for private, duplicate, or non-public pages
line 68
Common:
prefer correct image dimensions and stable aspect ratios
line 77
Common:
use a sensible og:type, usually website or article
line 79
Common:
do not add JSON-LD unless it clearly maps to real page content
line 92
Common:
do not invent ratings, reviews, prices, or organization details
line 94
Common:
prefer one structured data block per page unless required
line 95
Common:
add hreflang alternates only when pages truly exist
line 101
Common:
prefer minimal changes, do not refactor unrelated code
line 106
Common:
do not migrate frameworks or SEO libraries unless requested
line 107
Very specific:
follow the project’s existing metadata pattern (Next.js metadata API, react-helmet, manual head, etc.)
line 108
Common:
ensure title, description, canonical, and og:url agree
line 113
Common:
verify social cards on a real URL, not localhost
line 114
Common:
prefer stable, boring metadata over clever or dynamic
line 115
Common:
keep diffs minimal and scoped to metadata only
line 116

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

fixing-metadata

Ship correct, complete metadata.

how to use

/fixing-metadata Apply these constraints to any metadata work in this conversation.
/fixing-metadata <file> Review the file against all rules below and report:
- violations (quote the exact line or snippet)
- why it matters (one short sentence)
- a concrete fix (code-level suggestion)

Do not introduce new frameworks or SEO libraries unless explicitly requested. Prefer minimal diffs.

when to apply

Reference these guidelines when:

adding or changing page titles, descriptions, canonical, robots
implementing Open Graph or Twitter card metadata
setting favicons, app icons, manifest, theme-color
building shared SEO components or layout metadata defaults
adding structured data (JSON-LD)
changing locale, alternate languages, or canonical routing
shipping new pages, marketing pages, or shareable links

rule categories by priority

priority	category	impact
1	correctness and duplication	critical
2	title and description	high
3	canonical and indexing	high
4	social cards	high
5	icons and manifest	medium
6	structured data	medium
7	locale and alternates	low-medium
8	tool boundaries	critical

quick reference

1. correctness and duplication (critical)

define metadata in one place per page, avoid competing systems
do not emit duplicate title, description, canonical, or robots tags
metadata must be deterministic, no random or unstable values
escape and sanitize any user-generated or dynamic strings
every page must have safe defaults for title and description

2. title and description (high)

every page must have a title
use a consistent title format across the site
keep titles short and readable, avoid stuffing
shareable or searchable pages should have a meta description
descriptions must be plain text, no markdown or quote spam

3. canonical and indexing (high)

canonical must point to the preferred URL for the page
use noindex only for private, duplicate, or non-public pages
robots meta must match actual access intent
previews or staging pages should be noindex by default when possible
paginated pages must have correct canonical behavior

4. social cards (high)

shareable pages must set Open Graph title, description, and image
Open Graph and Twitter images must use absolute URLs
prefer correct image dimensions and stable aspect ratios
og:url must match the canonical URL
use a sensible og:type, usually website or article
set twitter:card appropriately, summary_large_image by default

5. icons and manifest (medium)

include at least one favicon that works across browsers
include apple-touch-icon when relevant
manifest must be valid and referenced when used
set theme-color intentionally to avoid mismatched UI chrome
icon paths should be stable and cacheable

6. structured data (medium)

do not add JSON-LD unless it clearly maps to real page content
JSON-LD must be valid and reflect what is actually rendered
do not invent ratings, reviews, prices, or organization details
prefer one structured data block per page unless required

7. locale and alternates (low-medium)

set the html lang attribute correctly
set og:locale when localization exists
add hreflang alternates only when pages truly exist
localized pages must canonicalize correctly per locale

8. tool boundaries (critical)

prefer minimal changes, do not refactor unrelated code
do not migrate frameworks or SEO libraries unless requested
follow the project’s existing metadata pattern (Next.js metadata API, react-helmet, manual head, etc.)

review guidance

fix critical issues first (duplicates, canonical, indexing)
ensure title, description, canonical, and og:url agree
verify social cards on a real URL, not localhost
prefer stable, boring metadata over clever or dynamic
keep diffs minimal and scoped to metadata only

Download now (ZIP)

Other versions9 projects use a version of this.
Word for word · 1
agentset-ai/agentset★ 2.1k100% same
Edited · 7
ibelick/ui-skills★ 10k81% same
master5d/claude-design-skills★ 2681% same
julianromli/faiz-skills★ 1681% same
hsynozdamar-byte/claude-skills-edited★ 484% same
Discriminative-shoji607/ui-skills★ 381% same
ClaireAll/skills★ 286% same
sanmidable/skills★ 278% same
Wrote their own version · 1
jscraik/Agent-Skills★ 9same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use improve-ui, ui-skills-root and 9 more.
Other files people use alongside this one.
- Discriminative-shoji607Skill
  improve-ui
  Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.
  Also in 4 projects that use this
- Discriminative-shoji607Skill
  ui-skills-root
  Use before UI-related work to select the smallest useful UI Skills context through the ui-skills CLI.
  Also in 3 projects that use this
- ItamarZand88Skill
  create-design-md
  Create a new DESIGN.md file for any website, app, or custom design system. Use when the user wants to document a design system in DESIGN.md format, extract design tokens from a URL or existing CSS, create a custom design system from scratch, author a DESIGN.md for their own project, or contribute a new design to the awesome-design-md collection. Also trigger when user mentions "design system documentation", wants to formalize their app's visual language, or asks to create or generate a DESIGN.md file.
  Also in 4 projects that use this
- AnasX7Skill
  better-interface
  Combines all of the `better-*` skills into a single review across accessibility, layout, writing, typography, color and UI polish.
  Also in 3 projects that use this
- AnasX7Skill
  better-accessibility
  Helps your project comply with accessibility standards and best practices.
  Also in 3 projects that use this
- VercelSkill
  emil-design-eng
  This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
  Also in 4 projects that use this
- +5 more from AnasX7
In this repository11 other files it gives its agents.
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- baseline-uiSkill
- fixing-accessibilitySkill
- fixing-motion-performanceSkill
- frontend-designSkill
- generate-creative-ideasSkill
- nextjs-best-practicesSkill
- remotion-best-practicesSkill
- seo-auditSkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free

20 rules. 18 are common, 1 is distinctive, and 1 is very specific to this project.

fixing-metadata

how to use

when to apply

rule categories by priority

quick reference

1. correctness and duplication (critical)

2. title and description (high)

3. canonical and indexing (high)

4. social cards (high)

5. icons and manifest (medium)

6. structured data (medium)

7. locale and alternates (low-medium)

8. tool boundaries (critical)

review guidance

Word for word · 1

Edited · 7

Wrote their own version · 1

improve-ui

ui-skills-root

create-design-md

better-interface

better-accessibility

emil-design-eng

Does it work?

Your trail

Now do this for your own.