Skills

Packaged instructions Claude loads when a particular kind of work comes up. A skill is how a procedure that would otherwise be re-explained every time becomes something the model just knows.

What lives here, and the exception it carries

Skills that produce marketing and go-to-market artefacts. Today that is one: building product demos for landing pages, videos, decks and explainers.

CLAUDE.md rule 4 says this repository holds no code, and rule 3 says technical documentation belongs in erudeon/passtheyear. This directory is a deliberate exception, decided on 2026-08-27, and it is worth being honest about rather than quietly contradicting the rule:

• A demo is a marketing artefact. It ships to a landing page or a video editor, never to a student, and it is commissioned by whoever is making the campaign — not by engineering.
• The engine it uses is frozen. It is not product code, nothing imports it, and no deploy depends on it.
• Keeping it beside go-to-market/ means the person who needs a demo can find how demos get made.

The cost is real: this directory contains an HTML template and a Python script, so rule 4 is now "no code except .github/ and skills/". If a second exception is ever proposed, that is the moment to ask whether these belong in the product repository after all.

What still holds: a skill here may describe how to make something, never restate a technical rule that erudeon/passtheyear owns. Where a skill needs the palette, the components or the vocabulary, it says go and read them there rather than copying them — because a copy is the "two implementations of one rule" bug rule 3 exists to prevent.

The skills

Skill	Use it when
product-demo/	Somebody needs a recordable, self-contained demo of a product flow — for a landing page loop, a marketing video, a sales deck, an explainer, or a preview of something not built yet

Using one

In a Claude session with this repository available, the skill triggers on its own description; you can also invoke it by name. Each skill directory holds SKILL.md (the instructions), plus assets/, scripts/ and references/ where it needs them.

Adding one

A skill earns its place when the same request has come up a third time and the answer was long both times. Give it a SKILL.md with name and description frontmatter — the description is what decides whether it ever gets used, so write it as when to reach for this, not as a title. Then add a row above.