agentleFS
passion4it-gmbhpassion4it-gmbh/passionfruit-site/.claude/skills/passionfruit-content/SKILL.md

passionfruit-content

Skill0 starsChanged 12 days agoMITView on GitHub

Use when the user wants to add, edit, translate, or remove content (blog posts, team members, pages, navigation, translation strings, or anything inside src/content/, src/i18n/, or src/components/). Loads the bilingual rules, frontmatter shapes, page-registry conventions, and component sidecar rules so edits don't silently break the build.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never invent facts about a real business: No made-up people, quotes, clients, numbers or awards, and no placeholder text in anything that …

    line 16
  2. Very specific:

    No hex literals in components — use Tailwind tokens that map to @theme values in src/styles/global.css.

    line 78
  3. Very specific:

    Every .astro component under src/components/ has a sidecar .md file next to it (same basename).

    line 82

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

passionfruit content rules

Project content is bilingual (DE + EN) by default. The build refuses to ship monolingual entries. Read this skill before editing anything under src/content/ or src/i18n/.

Hard rules

  1. Every collection entry exists in both de/ and en/. Pair them with the same translationKey frontmatter value.
  2. Every i18n string lives in both src/i18n/de.json and src/i18n/en.json. Same nested key path, different language.
  3. Never commit a single-locale change. scripts/check-bilingual.mjs runs as prebuild and exits 1 if pairs are missing.
  4. translationKey is ASCII, kebab-case, derived from the English version of the title — same across both locale files. It is the identifier; the slug (filename) can differ.
  5. Never invent facts about a real business. No made-up people, quotes, clients, numbers or awards, and no placeholder text in anything that ships. Ask the user, or leave it out.
  6. Only reference images that exist. A frontmatter image path to a missing file fails the whole build. heroImage and photo are optional, so omit them if there's no file.

Collections at a glance

TypePathRequired frontmatterHelper command
Blogsrc/content/blog/{de,en}/*.mdtranslationKey, title, description, publishedAt, author, tags. Optional: featured, heroImage/new-post
Teamsrc/content/team/{de,en}/*.mdtranslationKey, name, role, displayOrder. Optional: specializations, photo, socials/new-team-member
Pagessrc/content/pages/{de,en}/*.mdtranslationKey, title, description. Optional: heroImage(manual)
Careerssrc/content/careers/{de,en}/*.mdtranslationKey, title, location, employmentType, applyUrl, summary, postedAt. Optional: department, seniority, closesAt, salaryMin/salaryMax/salaryCurrency, tags(manual)
Eventssrc/content/events/{de,en}/*.mdtranslationKey, title, summary, startsAt, category, location. Optional: endsAt, tags, registrationUrl, heroImage, speakers(manual)
Case Studiessrc/content/caseStudies/{de,en}/*.mdtranslationKey, personName, personRole, clientName, category, quote, portraitImage. Optional: tags, portraitFit, videoId, publishedAt(manual)

Image paths in frontmatter are relative to the markdown file, not to the project root — e.g. ../../../assets/blog/<slug>.png from a blog post, or ./_images/hero.jpg if collocated.

Adding a new page

A new page is not just a markdown file. Four things must change in lockstep:

  1. Markdown entries at src/content/pages/de/<slug>.md and src/content/pages/en/<slug>.md (with matching translationKey).
  2. A page component in src/components/pages/ (Astro). Reuse hero/section helpers — don't re-roll layout.
  3. A new entry in the PAGES array in src/lib/page-registry.ts mapping PageKey to { de: '<de-slug>', en: '<en-slug>' }. The catch-all route src/pages/[...path].astro reads from this registry.
  4. Navigation: add items in Header.astro and Footer.astro if the page should be linked.

heroImage on about, services, contact auto-renders the split-layout hero. imprint and privacy intentionally ignore it — legal pages stay sober.

Translation strings (src/i18n/{de,en}.json)

  • Nested object shape: { "section": { "key": "value" } }.
  • Access from components via useTranslations(locale) then t('section.key').
  • German is the primary market — DE strings must read like a native wrote them, not like a machine translated from English.

Tag and role conventions

Tag and role labels are per-locale. Use these pairs when possible (custom values must be translated naturally for the other locale):

DEEN
KIAI
WebentwicklungWeb Development
DesignDesign
BusinessBusiness
TutorialTutorial
UnternehmenCompany
DEEN
GeschäftsführerinCEO
Lead EntwicklerLead Developer
DesignerinDesigner
Digitale TransformationDigital Transformation

Routing recap

URL scheme is apex-locale: DE lives at the root (/), EN under /en/. Localized slugs are paired in src/lib/page-registry.ts (/leistungen ↔ /en/services). If you rename a slug in only one locale, the registry breaks language switching — change both at once.

Before committing

  • Both DE and EN files exist for any new collection entry.
  • Both de.json and en.json updated for any new i18n key.
  • pnpm build runs locally (it triggers the bilingual check, lint, typecheck, and astro build).
  • No hex literals in components — use Tailwind tokens that map to @theme values in src/styles/global.css.

Components

Every .astro component under src/components/ has a sidecar .md file next to it (same basename). The sidecar is the component's living doc: purpose, props, usage examples, and design rationale.

  • Before editing or composing with a component, read its sidecar first.
  • When creating a new component, create the sidecar in the same commit. The prebuild check (scripts/check-component-docs.mjs) exits 1 if any .astro file is missing its pair.
  • The canonical sidecar contract and template live in docs/superpowers/specs/2026-05-28-component-sidecar-docs-design.md § "Sidecar contract".
  • See src/components/CollectionFilter.md for a representative sidecar to understand the expected shape.
  • src/components/CLAUDE.md is partially auto-generated. The block between <!-- CATALOG:START --> and <!-- CATALOG:END --> is regenerated on every build and by pnpm sync:component-catalog. Never edit inside those markers — changes go in the individual sidecars.

When you're stuck

  • /new-post scaffolds a bilingual blog post correctly.
  • /new-team-member scaffolds a bilingual team entry correctly.
  • For pages or i18n changes, do them by hand and re-read this skill before committing.
  • See CONTRIBUTING.md for the long-form reference; this skill is the short version.

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.