Brand a TutorialKit (Astro interactive-tutorial) project for Patterson Companies, or scaffold a new Patterson-branded TutorialKit starter. Use when the user mentions TutorialKit, interactive tutorials, or hands-on training content in the Patterson brand.
How this skill is triggered — by the user, by Claude, or both
Slash command
/patterson-tutorialkit:tutorialkit-themeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Patterson theme for TutorialKit (Astro-based interactive tutorials): a runnable starter project with the canonical theme.css, brand logos, and a static theme-preview page.
Patterson theme for TutorialKit (Astro-based interactive tutorials): a runnable starter project with the canonical theme.css, brand logos, and a static theme-preview page.
Everything lives under ${CLAUDE_PLUGIN_ROOT}/ds/, laid out exactly like the Patterson design-system source tree, so every relative reference inside the files (../../styles.css, ../../assets/brand/…, ../../_ds_bundle.js) resolves without edits.
Copy the snapshot into the user's project, preserving the tree:
cp -R "${CLAUDE_PLUGIN_ROOT}/ds" ./patterson
If the project already has a patterson/ design-system folder from another Patterson plugin, merge instead of duplicating — only add the subfolders that are missing.
The working entry point is then patterson/templates/tutorialkit/README.md.
Edit CONTENT in place; keep the structure, class names, and token usage intact. Never inline raw hex colors — use the CSS variables.
Open the entry file in a browser (or a static server) to preview.
ds/templates/tutorialkit/ — runnable TutorialKit starter (Astro + UnoCSS): theme.css (the canonical brand theme), astro.config.mjs, uno.config.ts, src/, public/ (logo.svg, logo-dark.svg)ds/ui_kits/tutorialkit/index.html — static preview of the themed TutorialKit shell (renders entirely from --tk-* vars)ds/assets/brand/ — logo lockupstheme.css into the project root and public/logo*.svg; every color is a --tk-* variable TutorialKit reads natively.ds/templates/tutorialkit/ folder, then bun install && bun run dev (or npm equivalents). See its README.theme.css — never copy values out of it; change the token, and both update.#003767 (primary), Sky #00A8E1 (accent, hovers, stats). Secondary blue #147EC2. Tertiary green #7BC24D, teal #00817D, purple #522E91 — data/infographics only, never page chrome. Body gray #58585B, light gray #ECECEC.All of this is encoded as CSS custom properties in ds/tokens/*.css (linked via ds/styles.css). Always style with the --pat-*, --surface-*, --space-*, --fs-*, --shadow-* variables rather than raw hexes.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
npx claudepluginhub danielbodnar/patterson-design-plugins --plugin patterson-tutorialkit