Kit updates
Bring the kit's improvements into your app without losing your reports or your own changes.
Your app was made from the Silvi kit. The kit keeps improving: new components, fixes, better checks, new themes. An update brings those into your app.
Ask for it#
“Is there a kit update? Tell me what it changes before applying it.”
Claude runs silvi update --dry-run first and tells you which files would change. When you say so, it runs the update, then the checks, and opens a report to confirm all is well.
What an update touches#
| Your files | What happens |
|---|---|
Reports in app/src/reports/ |
Never touched: they are yours |
The wiki in app/wiki/ and data in app/data/ |
Never touched |
app/.env |
Never touched |
| Kit files you did not change | Replaced by the new version |
| Kit files you changed, which the kit did not | Kept as you have them |
| Kit files both you and the kit changed | Kept as you have them, with the kit’s version beside them as <file>.kit |
How it knows#
When the app was made, silvi.json recorded a fingerprint of every file copied from the kit. On an update, each file is compared three ways: the fingerprint, the file as it is now, and the kit’s new version. So a file is replaced only when you have not touched it.
.kit files#
A .kit file means both sides changed the same file. Yours is left working as it is; the kit’s version waits beside it.
app/src/components/report-kit/components.tsx
app/src/components/report-kit/components.tsx.kitAsk:
“Merge the .kit files and remove them.”
Claude reads both, keeps your change and the kit’s improvement, runs the checks, and deletes the .kit file.
The theme works the same way: silvi apply keeps a theme.css you changed and writes the preset’s beside it as theme.css.kit.
Go back#
“Go back to the kit version before the update.”
Claude updates to the earlier version with silvi update --to <tag>, or puts back a saved version of your app. Your app is a folder kept in git, so every saved state can come back.