Build a Patterson-branded web page (marketing, landing, informational). Use when the user asks for a Patterson web page, landing page, or site section. Scaffolds a React shell with sticky nav, navy hero, content band, and footer wired to brand tokens and components.
How this skill is triggered — by the user, by Claude, or both
Slash command
/patterson-corporate-page:corporate-page-templateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Patterson corporate web page shell: sticky nav with logo, navy hero, content band, and footer — a React starting point for any on-brand marketing or informational page.
Patterson corporate web page shell: sticky nav with logo, navy hero, content band, and footer — a React starting point for any on-brand marketing or informational 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/corporate-page/index.html.
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/corporate-page/index.html — page shell (React 18 UMD + Babel, in-browser JSX)ds/templates/corporate-page/ds-base.js — loads tokens + _ds_bundle.js (base path ../..)ds/styles.css, ds/tokens/, ds/assets/, ds/_ds_bundle.jsindex.html.window.PattersonCompaniesDesignSystem_1f7cbe (Button, Card, Stat, Badge, …) once _ds_bundle.js loads.<main> between hero and footer; use pat-container for the centered max-width column and --space-* rhythm (64–128px between sections).#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-corporate-page