skills/theme-factory/SKILL.md
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
npx skillsauth add MoonBoi9001/claude-code-cli-tools theme-factoryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill provides a curated collection of professional font and color themes themes, each with carefully selected color palettes and font pairings. Once a theme is chosen, it can be applied to any artifact.
To apply consistent, professional styling to presentation slide decks, use this skill. Each theme includes:
To apply styling to a slide deck or other artifact:
theme-showcase.pdf file to allow users to see all available themes visually. Do not make any modifications to it; simply show the file for viewing.The following 10 themes are available, each showcased in theme-showcase.pdf:
Each theme is defined in the themes/ directory with complete specifications including:
After a preferred theme is selected:
themes/ directoryTo handle cases where none of the existing themes work for an artifact, create a custom theme. Based on provided inputs, generate a new theme similar to the ones above. Give the theme a similar name describing what the font/color combinations represent. Use any basic description provided to choose appropriate colors/fonts. After generating the theme, show it for review and verification. Following that, apply the theme as described above.
testing
Bring a branch up to date with its base by MERGING the base in (a merge commit), never rebasing — so no commit hashes are rewritten and no force-push is needed. Use this whenever the user asks to "use the merge skill", "bring my branch up to date", "merge main/the base into this branch", "update my branch from its base without rebasing", "do a merge commit instead of rebasing", or "clear the conflict on my stacked PR without a force-push" (a common situation right after a parent PR squash-merges and the child branch suddenly shows conflicts). It handles both cases: a base that only re-packaged work the branch already has, and a base that carries genuinely new work to fold in. It always verifies the merge preserved exactly the branch's own change before pushing. This is an explicitly-invoked workflow — reach for it when the user talks about merging or updating a branch from its base, but don't hijack unrelated git merges.
development
Run a deep multi-agent review of a GitHub PR — 6 specialized agents covering architecture, correctness, security, tests, code quality, and integration. ONLY trigger when the user's message contains the explicit phrase 'deep review' (e.g. 'deep review this PR', 'deep review PR #1234', 'do a deep review of 1234', '/deep-review'). Do NOT trigger on bare 'review', 'review this', 'review the PR', 'code review', 'what do you think of this PR', or pasted PR URLs without 'deep review' in the message — those are handled by the lighter /review skill. The literal phrase 'deep review' must appear in the user's message; absence of that phrase means do not invoke this skill.
data-ai
--- name: re-explain description: Re-explain a concept from the ground up when an earlier explanation didn't land. Trigger aggressively whenever the user signals confusion about recent technical content — phrases like "i don't get it", "from scratch", "ground up", "explain again", "this makes no sense", "try again", "you need to work better", "what's X" (where X was something just mentioned), or invoking /re-explain directly. Also trigger on quieter cues like the user re-quoting a phrase from th
development
Load a high-fidelity recap of a prior Claude Code session into the current session's context. The goal is to be LESS lossy than running /compact would be — the user is invoking this skill precisely because /compact discards detail they need. Use this when the user wants to "resume", "pick up", "continue", or "load context from" a previous session — especially a long one (hundreds of thousands of tokens) where actually resuming the session would be prohibitively expensive, or where the session was auto-compacted mid-flow and a lot of detailed work happened after the last compaction that another /compact pass would crush. Also trigger on phrases like "recap the last session", "what was I working on yesterday", "load the prior chat", or "/load-prior-session". The skill extracts via a subagent so the full transcript never enters the current session's context.