メニュー
Build Patterson-branded documentation sites and doc pages. Use when the user asks for Patterson docs, a documentation site, developer docs, knowledge base, or help center. Ships a VitePress/Diátaxis-styled React UI kit and a standalone docs page template.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Design anything on-brand for Patterson Companies (oral & animal health distribution). Use whenever the user asks for Patterson-branded UI, pages, mocks, decks, components, styling, colors, typography, or brand review. Contains tokens, components, logos, fonts, and framework adapters.
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.
Build screens in the style of the Patterson Companies corporate website. Use when the user asks for corporate-site pages, investor/newsroom pages, or wants to extend the pattersoncompanies.com look. Ships header, footer, home, what-we-do and newsroom screens as React components.
Build a Patterson Companies branded slide deck (16:9 presentation). Use when the user asks for a Patterson deck, presentation, slides, or company overview. Scaffolds from the official deck template with cover, divider, stats, comparison, quote, table, photo-band and closing archetypes.
Build a Patterson Companies executive briefing deck. Use when the user asks for an executive deck, leadership briefing, board-style presentation, or formal readout in the Patterson brand. Denser, editorial layout compared to the standard deck.
Build a Patterson-branded application shell / internal tool prototype (file manager, studio, dashboard). Use when the user asks for a Patterson app UI, admin tool, file browser, or workspace prototype. Scaffolds the Skill Studio shell with top bar, sidebar and content area.
| name | docs-site |
| description | Build Patterson-branded documentation sites and doc pages. Use when the user asks for Patterson docs, a documentation site, developer docs, knowledge base, or help center. Ships a VitePress/Diátaxis-styled React UI kit and a standalone docs page template. |
| user-invocable | true |
Patterson documentation-site package: a VitePress + Diátaxis styled docs UI kit (sidebar nav, content pages, collections) and a browser-openable docs page template.
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/ui_kits/patterson-docs/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/ui_kits/patterson-docs/ — full docs-site UI kit (React 18 UMD + Babel): app.jsx, pages1/2.jsx, collections.jsx, data.jsxds/templates/patterson-docs/PattersonDocs.dc.html + support.js — standalone docs page template, opens directly in a browserds/styles.css, ds/tokens/, ds/assets/, ds/_ds_bundle.jsdata.jsx holds the nav tree and page registry — edit it first.ds/templates/patterson-docs/PattersonDocs.dc.html and edit its content in place.#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.