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.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- brandSkill
- deploySkill
- new-postSkill
- new-team-memberSkill
- onboardSkill
- passionfruit-a11ySkill
- passionfruit-designSkill
- passionfruit-perfSkill
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
- Distinctive: line 16
Never invent facts about a real business: No made-up people, quotes, clients, numbers or awards, and no placeholder text in anything that …
- Very specific: line 78
No hex literals in components — use Tailwind tokens that map to @theme values in src/styles/global.css.
- Very specific: line 82
Every .astro component under src/components/ has a sidecar .md file next to it (same basename).
≈ “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.
Files
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
- Every collection entry exists in both
de/anden/. Pair them with the sametranslationKeyfrontmatter value. - Every i18n string lives in both
src/i18n/de.jsonandsrc/i18n/en.json. Same nested key path, different language. - Never commit a single-locale change.
scripts/check-bilingual.mjsruns asprebuildand exits 1 if pairs are missing. translationKeyis 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.- 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.
- Only reference images that exist. A frontmatter image path to a missing file fails the whole build.
heroImageandphotoare optional, so omit them if there's no file.
Collections at a glance
| Type | Path | Required frontmatter | Helper command |
| Blog | src/content/blog/{de,en}/*.md | translationKey, title, description, publishedAt, author, tags. Optional: featured, heroImage | /new-post |
| Team | src/content/team/{de,en}/*.md | translationKey, name, role, displayOrder. Optional: specializations, photo, socials | /new-team-member |
| Pages | src/content/pages/{de,en}/*.md | translationKey, title, description. Optional: heroImage | (manual) |
| Careers | src/content/careers/{de,en}/*.md | translationKey, title, location, employmentType, applyUrl, summary, postedAt. Optional: department, seniority, closesAt, salaryMin/salaryMax/salaryCurrency, tags | (manual) |
| Events | src/content/events/{de,en}/*.md | translationKey, title, summary, startsAt, category, location. Optional: endsAt, tags, registrationUrl, heroImage, speakers | (manual) |
| Case Studies | src/content/caseStudies/{de,en}/*.md | translationKey, 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:
- Markdown entries at
src/content/pages/de/<slug>.mdandsrc/content/pages/en/<slug>.md(with matchingtranslationKey). - A page component in
src/components/pages/(Astro). Reuse hero/section helpers — don't re-roll layout. - A new entry in the
PAGESarray insrc/lib/page-registry.tsmappingPageKeyto{ de: '<de-slug>', en: '<en-slug>' }. The catch-all routesrc/pages/[...path].astroreads from this registry. - Navigation: add items in
Header.astroandFooter.astroif 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)thent('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):
| DE | EN |
| KI | AI |
| Webentwicklung | Web Development |
| Design | Design |
| Business | Business |
| Tutorial | Tutorial |
| Unternehmen | Company |
| DE | EN |
| Geschäftsführerin | CEO |
| Lead Entwickler | Lead Developer |
| Designerin | Designer |
| Digitale Transformation | Digital 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.jsonanden.jsonupdated for any new i18n key. pnpm buildruns locally (it triggers the bilingual check, lint, typecheck, and astro build).- No hex literals in components — use Tailwind tokens that map to
@themevalues insrc/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.astrofile 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.mdfor a representative sidecar to understand the expected shape. src/components/CLAUDE.mdis partially auto-generated. The block between<!-- CATALOG:START -->and<!-- CATALOG:END -->is regenerated on every build and bypnpm sync:component-catalog. Never edit inside those markers — changes go in the individual sidecars.
When you're stuck
/new-postscaffolds a bilingual blog post correctly./new-team-memberscaffolds a bilingual team entry correctly.- For pages or i18n changes, do them by hand and re-read this skill before committing.
- See
CONTRIBUTING.mdfor the long-form reference; this skill is the short version.
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
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.

