Chisle
The coding-agent plugin that bills 52% of a bare model across 20 live tasks. Terse persona + tool-output compressor + context diet.
passionfruit — die zweisprachige Website-Vorlage für Claude Code. Repo erstellen, /onboard tippen, fertig.
Translation pending
Developer toolsGitHub @passion4it-gmbhAvailability not checked yetOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Repository information has not been collected yet.
No updates detected yet. GitHub releases will appear here.
The marketing site for passionfruit — built with passionfruit.
Loading the full README.
Read the full README ↗The marketing site for passionfruit — the bilingual website template that turns Claude Code into your web developer.
Live at passionfruit.passion4it.de.
This site is itself a passionfruit project. The repo doubles as a working example of what users get out of the box — no custom components, no special tricks. If a feature exists here, it exists in every passionfruit scaffold.
pnpm install
pnpm dev # local server at http://localhost:4321
pnpm build # production build (lint + typecheck + bilingual check)
pnpm check:all # full CI suite locally
passion4it-gmbh/passionfruit — the template this site usespassion4it-gmbh/create-passionfruit — pnpm create passionfruitpassionfruit is a one-shot template — your project is yours once it's scaffolded. But passionfruit itself keeps evolving (new components, design improvements, security fixes), and you can pull those in whenever you want.
The Claude-driven way (recommended):
Check passion4it-gmbh/passionfruit/releases for versions newer than
ours. Pull in the newsletter signup component from the latest release
and adapt it to our brand colors.
Claude fetches the relevant files from the latest release, adapts them to your codebase, and wires them in. You only adopt what's useful.
The git-native way:
git remote add upstream https://github.com/passion4it-gmbh/passionfruit.git
git fetch upstream main
git log HEAD..upstream/main --oneline # see what's new
git cherry-pick <sha> # pick a specific change
Expect conflicts on src/i18n/*.json, src/lib/page-registry.ts, and src/content/ — those are your business content, keep your version.
Watch Releases (click "Watch" → "Custom" → "Releases" on the repo) to get notified when there's something worth adopting.
MIT