agentleFS
passion4it-gmbhpassion4it-gmbh/passionfruit-site/CLAUDE.md

passionfruit-site

CLAUDE.md0 starsChanged 12 days agoMITView on GitHub

This is the public marketing site for the passionfruit website template — meta on purpose. The site is itself a passionfruit project, so anything we ship here is also a live demo of what users get out of the box. **Claude must keep CLAUDE.md, STYLE_GUIDE.md, and CONTRIBUTING.md in sync with reality.** Update these files when: This is not optional. These files are the project's memory. If they drift from reality, future sessions will produce wrong code. If the site still…

  • Reads credentials
  • Commits and pushes

The file

Show its rules and text

We split this CLAUDE.md into the rules it gives an agent

15 rules. About 0 are common, 8 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Hard rule: if you ever feel the urge to add a custom component, ship it upstream to the passionfruit framework first, then pull it in here.

    line 12
  2. Very specific:

    If the site still shows "passionfruit", run /onboard to personalize it for your business.

    line 29
  3. Distinctive:

    Never commit a single-locale entry.

    line 55
  4. Very specific:

    Translations: Always update both src/i18n/de.json and src/i18n/en.json in lockstep.

    line 67
  5. Distinctive:

    Prefer Astro components over React.

    line 71
  6. Distinctive:

    Always update both i18n JSON files when adding strings.

    line 76
  7. Very specific:

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

    line 90
  8. Distinctive:

    Always end with "No text, no logos" unless text is wanted

    line 185
  9. Very specific:

    Use --size 1536x1024 for hero/banner images, 1024x1024 for square thumbnails

    line 186
  10. Very specific:

    Site URL: Update site in astro.config.mjs after deployment.

    line 212
  11. Distinctive:

    Never push directly to main: Every change goes through a pull request, even if it's just you.

    line 220
  12. Very specific:

    Create a branch: git checkout -b feat/<short-name>

    line 224
  13. Distinctive:

    Wait for CI to pass and Cloudflare to deploy a preview — the preview URL appears on the PR

    line 228
  14. Distinctive:

    Squash merge: when approved — this keeps main history linear and readable

    line 230
  15. Very specific:

    Preview deployments: Every PR gets a unique preview URL like https://<branch-name>.<project>.pages.dev, updated on every push to the branch.

    line 247

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 CLAUDE.md 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
CLAUDE.md

passionfruit-site

1. Project

This is the public marketing site for the passionfruit website template — meta on purpose. The site is itself a passionfruit project, so anything we ship here is also a live demo of what users get out of the box.

  • Audience: non-technical site owners (primary), curious developers (secondary).
  • Primary CTA: pnpm create passionfruit my-site.
  • Languages: German at root, English at /en/ (bilingual is the framework's USP — we eat the dog food).
  • Hosting: Cloudflare Pages at passionfruit.passion4it.de.
  • Pages: Home, Features (/funktionen/, /en/features/), Blog, Contact, Imprint, Privacy. No About, no Team — the agency portfolio at passion4it.de fills that slot.
  • Hard rule: if you ever feel the urge to add a custom component, ship it upstream to the passionfruit framework first, then pull it in here. Customizing this site directly defeats the dogfood signal.

2. Self-improvement rule

Claude must keep CLAUDE.md, STYLE_GUIDE.md, and CONTRIBUTING.md in sync with reality. Update these files when:

  • The user establishes a preference ("always use rounded buttons" → add to STYLE_GUIDE.md button section)
  • A new content collection is added → document its schema, paths, and workflow in CONTRIBUTING.md
  • A recurring issue is fixed → add to the quality checklist so it doesn't happen again
  • A new component pattern emerges → document it in STYLE_GUIDE.md
  • Routing changes → update the routing section below
  • New commands are added → update the commands table

This is not optional. These files are the project's memory. If they drift from reality, future sessions will produce wrong code.

3. First-time setup

If the site still shows "passionfruit", run /onboard to personalize it for your business. After onboarding, run /brand to replace the placeholder favicon and social sharing image with your own logo.

If a user says /onboard "doesn't work": they are likely in the Claude Desktop chat app, where repo skills and slash commands don't exist. Point them to a Claude Code surface — claude.ai/code (no install), the Code tab of the desktop app, the CLI, or an IDE extension. In any of those, plain language works too: "set this site up for my business" triggers onboarding without the slash command.

4. Tech stack

ToolVersion / notes
Node26 LTS in .nvmrc; engines floor stays 22.23.4 because cloud sessions ship Node 22
Astro7, static output
MarkdownSätteri (Astro 7's engine); external links via a hast plugin in astro.config.mjs
Tailwindv4 via @tailwindcss/vite (theme in src/styles/global.css @theme block)
TypeScriptstrict — no any, ever
Package managerpnpm
Icons@lucide/astro (no emojis)
Consentvanilla-cookieconsent
AnalyticsPostHog (EU instance, env-var-gated)
FontInter Variable (self-hosted via @fontsource-variable/inter)
ReactDependency present; only use when interactivity genuinely demands it

5. Bilingual rule

Hard rule: every page and every collection entry must exist in both DE and EN.

  • Pairing is via translationKey frontmatter field — same value across both locale files.
  • scripts/check-bilingual.mjs runs as prebuild and exits 1 if any entry is monolingual.
  • Never commit a single-locale entry. Always update both DE and EN in the same commit.

6. Content workflows

See CONTRIBUTING.md for full details. Summary:

Blog post: src/content/blog/{de,en}/<slug>.md — needs translationKey, title, description, publishedAt, author, tags.

Team member: src/content/team/{de,en}/<slug>.md — needs translationKey, name, role, displayOrder.

Page: src/content/pages/{de,en}/<slug>.md — needs translationKey, title, description. Also update src/lib/page-registry.ts.

Translations: Always update both src/i18n/de.json and src/i18n/en.json in lockstep. Nested key structure, accessed via t('section.key').

7. Component conventions

  • Prefer Astro components over React.
  • Brand tokens via Tailwind utility classes only — no hex literals in components.
  • Icons via @lucide/astro. No emojis.
  • Translation strings via useTranslations(locale) from ~/i18n.
  • Images via <Image> component from astro:assets.
  • Always update both i18n JSON files when adding strings.
  • Layout primitives: <Section tone="..." padding="..." container="..."> for every section frame; <Prose> for long-form Markdown rendering. Never compose ad-hoc <section> or <div> wrappers when a primitive exists.
  • Motion primitives: <Motion effect="fade-up" duration="base"> or its sugars <FadeUp> / <FadeIn> for entrance animations. Reduced-motion is handled for you — don't author per-element keyframes. The old anim-* scroll classes are gone — never add per-page IntersectionObserver scripts.
  • Section archetypes (src/components/sections/): AsymmetricHero, MagazineGrid, StickyStory, EditorialQuote, SplitFeature, Trust, Comparison, FAQ, FeatureList, CtaBand. Pick the right archetype before reaching for a custom layout.
  • State surfaces (src/components/state/): <Skeleton variant="..."> for loading states, <EmptyState> (CTA required — no dead-end empties), <ErrorState tone="warning|error|info">. Don't roll custom gray boxes or ad-hoc error text.
  • Sidecar docs: every *.astro in src/components/ has a sibling *.md sidecar (purpose, props, slots, owned i18n keys, gotchas) plus a generated index in src/components/CLAUDE.md. Props describe the local component, never upstream. Update the sidecar in the same commit as the component — a build-time check (scripts/check-component-docs.mjs, run in prebuild) fails on missing/malformed sidecars; pnpm sync:component-catalog regenerates the catalog. See src/components/CLAUDE.md for the schema.
  • The passionfruit-design, passionfruit-a11y, and passionfruit-perf skills auto-load on design, accessibility, and performance work respectively — read them for the full decision-shortcut cheat sheets.

8. Styling

Read STYLE_GUIDE.md before touching any UI. It is the single source of truth for colors, typography, buttons, cards, layout, accessibility, social proof, and state surfaces. The Decision Shortcuts cheat sheet at the bottom of STYLE_GUIDE.md is the fastest path to the right answer.

Key rules:

  • No hex literals in components — use Tailwind tokens that map to global.css @theme values
  • Buttons use variant (primary / secondary / ghost) x tone (on-light / on-dark)
  • One card component per content type (BlogCard is the only card in this repo)
  • 44px minimum touch targets
  • focus-visible ring on all interactive elements

9. Analytics and consent

vanilla-cookieconsent dispatches passionfruit:consent-changed events. Both analytics providers listen for that event and load on demand once window.hasAnalyticsConsent() returns true. Both are env-var-gated and no-op when their key is absent.

PostHog (EU) — PUBLIC_POSTHOG_API_KEY, PUBLIC_POSTHOG_HOST (defaults to https://eu.i.posthog.com — ingest endpoint), PUBLIC_POSTHOG_UI_HOST (defaults to https://eu.posthog.com — dashboard for toolbar/heatmap links).

Google Analytics 4 — PUBLIC_GA_MEASUREMENT_ID (format G-XXXXXXXXXX). Uses Consent Mode v2 with analytics_storage: granted only after the user accepts; ad cookies stay denied. IP anonymization on.

You can run either, both, or neither. Most users want GA4 (familiar dashboard); PostHog is for those who want session replay, funnels, and feature flags.

10. Contact form

The contact form (src/components/pages/contact.astro) submits a JSON body {name, email, message, honeypot, turnstileToken, lang} via POST to /api/contact. The honeypot is a hidden field rendered with the DOM name company; its value is sent on the wire as honeypot. Any non-empty value causes the request to be silently dropped (200 returned to the visitor, no email sent).

Delivery: functions/api/contact.ts (Cloudflare Pages Function) calls the Brevo transactional email API. Nothing is hardcoded — the To, From, and From display name all come from env vars (see below); Reply-To is the visitor's address, and the subject/body are localized by the lang field. Spam protection: honeypot + optional Cloudflare Turnstile (gated by TURNSTILE_SECRET_KEY) + Cloudflare edge limits — no app-level rate limiting by design.

The address shown on the page and the mailto: fallback are a separate thing: they come from the contact.info.email i18n string (currently info@passion4it.de in both locales), independent of the Function's CONTACT_RECIPIENT.

Env vars:

  • PUBLIC_FORM_ENDPOINT=/api/contact — build-time flag; enables real delivery via the Function. Leave EMPTY (default in .env.example) to fall back to a mailto: link — no Function is called.
  • CONTACT_RECIPIENT — secret; the address form submissions are delivered to (the To:).
  • CONTACT_SENDER — secret; a Brevo-verified sender address (the From:).
  • CONTACT_SENDER_NAME — optional secret; From: display name (default: Website contact form).
  • BREVO_API_KEY — secret; Brevo transactional API key.
  • PUBLIC_TURNSTILE_SITE_KEY (public, build-time) / TURNSTILE_SECRET_KEY (secret) — set together to enable Turnstile verification; leave both empty to rely on the honeypot alone. If CONTACT_RECIPIENT, CONTACT_SENDER, or BREVO_API_KEY is missing the Function returns a config error.

Set the secrets in the Cloudflare Pages dashboard (Settings → Environment Variables) for production. For local testing with wrangler pages dev, add them to a git-ignored .dev.vars file (never commit it).

DNS on passion4it.de: To authenticate the sending domain in Brevo, add the Brevo code TXT record, the DKIM TXT record, and a DMARC record if none already exists. SPF and MX records are NOT changed — Microsoft 365 keeps the mailboxes. Brevo sends via its own return-path and achieves DMARC compliance through DKIM alignment.

Testing: The Function is not exercised by pnpm build. End-to-end delivery is verified on the Cloudflare preview or production environment with BREVO_API_KEY set, or locally via wrangler pages dev.

11. Routing

  • URL scheme: apex-locale — DE at root (/), EN under /en/.
  • Localized slugs: /leistungen (DE) ↔ /en/services (EN).
  • Single source of truth: src/lib/page-registry.ts — PAGES array maps PageKey to { de, en } slug pairs.
  • Catch-all route: src/pages/[...path].astro.
  • Home pages: src/pages/index.astro (DE), src/pages/en/index.astro (EN).

12. Quality checklist

Before committing:

  • pnpm build passes (runs lint, typecheck, bilingual check)
  • Both DE and EN locales render correctly
  • No any in TypeScript
  • Mobile layout intact at 375px
  • No hex literals in components
  • New collection entries have translationKey in both locales
  • New i18n strings added to both de.json and en.json
  • German quotes are typed as literal „…“ — a straight closing " renders as ”
  • --color-accent reaches 4.5:1 on white (scripts/check-accent-contrast.mjs enforces this)
  • Changes align with STYLE_GUIDE.md
  • New components have a sidecar .md
  • Skills never invent business facts, commit placeholder text, or ask users to paste secrets into chat

13. Image generation

Social sharing (OG) image — pnpm generate-og

Produces the site's bilingual OG sharing image from project data (no API key, runs in <1 second). Inputs are auto-discovered: site.name + site.tagline from src/i18n/{de,en}.json, accent color from src/styles/global.css, logo from public/favicon.svg. Optional: drop a photo at src/assets/og/bg.png and it gets composited full-cover behind the text (with a left-anchored scrim for legibility). Outputs land at public/og-default-de.png and public/og-default-en.png (1200×630). BaseLayout picks the locale-specific file per page.

pnpm generate-og              # regenerate both locales
pnpm generate-og --lang de    # only DE
pnpm generate-og --lang en    # only EN

Re-run when site.name / site.tagline / favicon / accent color / src/assets/og/bg.png changes. The bilingual check (scripts/check-bilingual.mjs) fails a build if one locale's PNG is present without the other — no half-state can ship.

Content images — pnpm generate-image

Generate hero / background / decorative images using GPT Image models:

pnpm generate-image "your prompt here" -o src/assets/blog/my-image.png

Requires OPENAI_API_KEY in .env. The user must provide their own OpenAI API key. If the key is missing, the script will error with a clear message — prompt the user to add it.

Options: --size (1536x1024 for landscapes, 1024x1536 for portraits), --quality high, --background transparent (png/webp only, not gpt-image-2), --format (png/jpeg/webp).

Prompt guidelines for good results:

  • Be specific about composition, lighting, and mood
  • Reference a visual style ("editorial photography", "Kinfolk magazine", "minimal tech aesthetic")
  • Specify colors to match brand tokens (accent: #6265f0, dark: #1a1a2e)
  • Always end with "No text, no logos" unless text is wanted
  • Use --size 1536x1024 for hero/banner images, 1024x1024 for square thumbnails

14. Quality tooling

Commit hooks (lefthook): pre-commit runs lint-staged (ESLint, Prettier, cspell on changed files) + bilingual check. Commit-msg runs commitlint (conventional commits: feat:, fix:, chore:, docs:).

Spell checker (cspell): checks all markdown content in src/content/. German + English dictionaries loaded. Add unknown words to project-words.txt.

Link checker (linkinator): runs against built dist/ output after astro build. Catches broken internal links — pages referenced in nav or content that don't exist. Runs in CI after build.

Alt text enforcement: jsx-a11y/alt-text is set to error (not warn) in the a11y ESLint config. Missing alt text on images blocks the build.

Accent contrast gate (scripts/check-accent-contrast.mjs, runs as prebuild): fails the build if --color-accent is under 4.5:1 on white, the ratio shared by white-on-accent buttons and accent-colored text, and prints the nearest passing shade. Tested in scripts/check-accent-contrast.test.mjs.

Fixture-leak gate (scripts/check-fixtures.mjs, runs in prebuild): fails the build if the upstream template's demo brand leaks into shipped code (.astro/.ts/.js/.css). Brand identity in code must come from the site.name i18n string + Astro.site, never string literals.

15. Deployment

Default host: Cloudflare Pages (free, fast, automatic HTTPS). Run /deploy to set it up.

How it deploys: connect the GitHub repo in Cloudflare (Git integration). Cloudflare builds with pnpm build, publishes dist, and adds a preview link to each pull request. No API tokens or GitHub secrets are needed.

Contact form vars (BREVO_API_KEY, PUBLIC_FORM_ENDPOINT and the rest of §10) are set in the Cloudflare Pages dashboard, not in GitHub.

GitHub Actions alternative: .github/workflows/deploy.yml stays skipped unless CLOUDFLARE_PROJECT_NAME (variable), CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID (secrets) are set, which keeps the template green out of the box. Don't use both, or the site deploys twice.

Site URL: Update site in astro.config.mjs after deployment. This affects canonical URLs, sitemap, and OG meta tags.

Security headers + caching live in public/_headers (Cloudflare Pages auto-picks this up). Includes HSTS, CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, and long-cache rules for /_astro/*. The CSP is scoped to what's actually used (PostHog + GA4); if you add a new third-party script, iframe, or asset host, update the CSP or it will be blocked silently in the browser console.

CSP violation reporting is opt-in: when PUBLIC_POSTHOG_API_KEY is set at build time, scripts/postbuild-headers.mjs injects Reporting-Endpoints + report-uri/report-to directives pointing at PostHog's /report/ ingest. The script is a no-op without the key, so forks ship safely with reporting disabled. Bump the v=1 tag in the script when materially changing the CSP so historical noise doesn't drown out fresh regressions.

16. Git workflow

Never push directly to main. Every change goes through a pull request, even if it's just you.

The flow:

  1. Create a branch: git checkout -b feat/<short-name>
  2. Make changes, commit (commitlint enforces conventional commits: feat:, fix:, chore:, docs:)
  3. Push: git push -u origin feat/<short-name>
  4. Open a PR: gh pr create --fill (or via GitHub UI)
  5. Wait for CI to pass and Cloudflare to deploy a preview — the preview URL appears on the PR
  6. Review the live preview (visit the URL from the PR comment)
  7. Squash merge when approved — this keeps main history linear and readable
  8. Merging to main automatically triggers a production deploy

Why squash merge: WIP commits ("fix typo", "address review") shouldn't pollute main. One PR = one logical change = one commit. The PR description becomes the commit message.

Repo settings to enable on GitHub:

  • Settings → General → Pull Requests:
    • ✅ Allow squash merging — default to "Pull request title and description"
    • ❌ Allow merge commits
    • ❌ Allow rebase merging
    • ✅ Automatically delete head branches
  • Settings → Branches → Add branch protection rule for main:
    • ✅ Require a pull request before merging
    • ✅ Require status checks to pass (CI workflow)
    • ✅ Require linear history

Preview deployments: Every PR gets a unique preview URL like https://<branch-name>.<project>.pages.dev, updated on every push to the branch.

17. Commands

CommandPurpose
pnpm devLocal dev server
pnpm buildProduction build (sync + lint + typecheck + astro build + postbuild headers)
pnpm previewPreview built output
pnpm typecheckastro check + tsc --noEmit
pnpm lintESLint + Prettier with autofix
pnpm lint:a11yAccessibility lint (alt-text = error, rest = warn)
pnpm testBilingual + og-generator unit tests
pnpm check:spellingSpell check content markdown (DE + EN)
pnpm check:linksBroken link check on built output
pnpm check:allSpelling + a11y + build + link check (full CI locally)
pnpm generate-ogRegenerate localized OG sharing images from project data
pnpm generate-imageGenerate images via GPT Image (needs OPENAI_API_KEY)
/brandReplace placeholder favicon and OG image with your own
/deployInteractive Cloudflare Pages deployment setup
/new-postScaffold a bilingual blog post (DE + EN)
/new-team-memberScaffold a bilingual team member entry (DE + EN)

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.