using-workday-design
The shared look-and-feel for rendering Workday data as a page. Load this whenever a Sana skill produces a visual artifact — a snapshot page, card, or chart — so the result reads as Workday's own product (Canvas Design System tokens, Roboto, the app chrome, status pills) instead of a generic page. This is the branding source of truth: every artifact inlines its styling from here. The connector has no render tool, so the look ships here in the skill, not in the platform.
Install
With your agent
Install OMGSkills skill "workday/everywhere:plugins/sana/skills/using-workday-design" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Workday/everywhere /tmp/everywhere && ln -s /tmp/everywhere/plugins/sana/skills/using-workday-design ~/.claude/skills/using-workday-designFrom README
Rendering Workday data — make it look like Workday The Sana connector has no render tool, so an artifact you build won't be branded unless you brand it. Every visual must read as Workday's product. Reconstruct it from the tokens and components below — do not invent a look, and never hand-draw the logo. Build the artifact as a single self-contained HTML document (published artifacts can't link a shared stylesheet across URLs), so inline the :root block below into the page's . The file is a document, not a fragment. It begins with: A file that starts at has no charset, and names such as O'Shaughnessy render as mojibake. Commit to Workday's light product theme. Ground every figure in a real agent answer or clearly-labeled sample data. Include only chrome that works — no dead search box, menus, or notification icons. Do not load fonts, scripts, or stylesheets from the network. The font stack below falls back to Helvetica and Arial.