Files
clide/.claude/skills
Jeroen SchweitzerandClaude Opus 4.8 1746f9c204 whats-next: require pql plan export + commit after ticket mutations
Ticket changes land only in the gitignored .pql/pql.db; the post-checkout/post-merge hooks rebuild it from the committed changelog on every branch switch, so un-exported tickets vanish silently (this is how the T-208-T-225 tree was lost). Add an export-and-commit step to Step 3a and a matching anti-pattern, cross-linked to the pql skill.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-02 20:28:35 +02:00
..

Clide Claude-Code skills

Skills are reusable instruction packs Claude Code loads on demand. Each one lives in its own directory with a SKILL.md (frontmatter + body) and any helper scripts. This index is for humans skimming what's available; Claude discovers skills automatically from the directory structure.

Skill Purpose
d2-diagram Generate technical diagrams from .d2 source with the d2 CLI; renders to PNG.
frame0-wireframe Author UI wireframes as local JSON and sync to the Frame0 desktop app for rendering + export.
git-commit Commit conventions for this repo — message style, CHANGELOG discipline (40/60 word cap), attribution trailer, safety rules.
pql Query and plan against the markdown vault via the pql CLI (decisions, tickets, structural queries).
skill-create Guidance for creating new skills — SKILL.md structure, bundling scripts, packaging.
testmode Run and interpret the ClideTestApp platform integration harness; smoke-test after toolchain / IPC / theme / native changes.
ui-design Visual design guide — surface tokens, control geometry, Phosphor icons.
whats-next Dependency-driven batch selection against the pql backlog. Walks the initiative/epic tree, filters unblocked work, refines, optionally activates.

Adding a skill

Use the skill-create skill (or follow its SKILL.md by hand). Add a row to the table above so the inventory stays accurate; the index is otherwise just a directory listing.