slides.inly.se · team
For the team
Building a deck
Decks are built as data — write a deck.json, push, and
it’s live at its own private link. Here’s the loop.
Get started
Clone the repo and open it in Claude Code
Everything lives in the inly-3.0 monorepo under apps/slides.
git clone git@github.com:InlyTechnology/inly-3.0.git cd inly-3.0
Run the /slides skill
Tell it what the deck is — e.g. “En deck inför teammötet:
följ upp kvartalsmålen, siffrorna och roadmappen.” It
scaffolds the deck folder, writes deck.json from your
numbers, and follows the Inly voice. Hand it the real figures — it
never invents a metric.
Group decks in a category subfolder (one per kind of deck, e.g.
monthly/) and name each for the occasion — a year-month
for a recurring deck, any name you like for a one-off — always with a
random secret suffix. So a folder looks like
<category>/<name>-<secret>/.
Preview locally
Serve the slides root and open your folder. Edit deck.json and refresh — no build step.
python3 -m http.server -d apps/slides 8000 # → http://localhost:8000/<category>/<name>-<secret>/
Open a PR — it goes live at its private link
Once merged, Vercel deploys it automatically. Your deck is at slides.inly.se/<category>/<name>-<secret>/ — the random suffix is what keeps it private. The site is public, so anyone with the full link can open it; nothing lists or indexes it, so the link is the access. The skill hands you the URL when it’s done — share that, not the folder name. Export a print-sharp PDF alongside it with:
bash apps/slides/scripts/build-pdf.sh <category>/<name>-<secret>