🧭
WritingHTML

Engineering Onboarding

by murphytrueman

Engineering Onboarding is a Writing skill for Claude Code, published by murphytrueman in design-system-ops.

176 stars7 forkson murphytrueman/design-system-opsAdded 2026/09/07+1% in starsRepository updated 2026/08/22
claude-codeclaude-code-plugindesign-systemdesign-systemsdesign-tokensfigmaskills
Install in seconds
Install Engineering Onboarding
Copy Engineering Onboarding into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/murphytrueman/design-system-ops/tree/main/skills/engineering-onboarding ~/.claude/skills/engineering-onboarding

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/murphytrueman/design-system-ops.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/engineering-onboarding/SKILL.md in murphytrueman/design-system-ops
Installs to
~/.claude/skills/engineering-onboarding
Collection
One of 25 skills cataloged from this repository
Category
Writing1328 skills

What Engineering Onboarding does

Engineering Onboarding creates a first-day guide for engineers joining a team that consumes a design system. It covers installation, component usage, token access, testing, and the rules that prevent local wrappers and hardcoded values.

Engineering Onboarding is cataloged under Writing on DirSkills. Engineering Onboarding comes from a repository tagged claude-code, claude-code-plugin, design-system, design-systems and design-tokens.

Documentation

README

Context

Engineering onboarding is genuinely different from designer onboarding. The mental model is different (consuming an API vs composing with a library), the first tasks are different (install and import vs connect Figma library), the tooling is different (package manager, TypeScript types, test harness vs Figma, documentation platform). Most importantly, engineers are where component drift originates — wrapping system components in local styled wrappers, hardcoding token values, reimplementing components locally. Proper onboarding from day one is the highest-leverage adoption intervention.

Key principles

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Engineering Onboarding

  • What else does murphytrueman publish alongside Engineering Onboarding?

    Engineering Onboarding is one of 25 skills that DirSkills catalogs from murphytrueman/design-system-ops, the repository it ships in. Its siblings there include AI Component Description, Accessibility Per Component and Adoption Report. Each one is a separate skill with its own page in this directory, installs the same way Engineering Onboarding does, and is maintained by murphytrueman in that same repository. The rest of the collection is listed on the murphytrueman/design-system-ops page.

  • How does Engineering Onboarding compare to other Writing skills?

    Engineering Onboarding ranks #1137 by stars among the 1328 Writing skills in this catalog. The most-starred ones next to it are Article Writing, Social Media Content Calendar and Knowledge Comic Creator. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Engineering Onboarding against them. Open each page to compare what they document and how they install.

More from murphytrueman/design-system-ops

Engineering Onboarding is one of 25 skills cataloged on DirSkills from murphytrueman/design-system-ops.

See all 25 skills
🤖
2h ago

AI Component Description

AI Component Description generates six-section prose descriptions for components so LLMs can understand purpose, props, composition, accessibility, and examples. Use it when writing Figma MCP descriptions or other text meant to make components legible to Claude and similar agents.
AI Engineering
1767
2h ago

Accessibility Per Component

Accessibility Per Component runs a structured accessibility audit on a single design system component. It checks keyboard use, screen reader behavior, colour contrast, focus, and ARIA against WCAG 2.1 AA.
Quality
1767
📈
2h ago

Adoption Report

Adoption Report separates design system coverage from actual adoption, with trend direction and risk flags. Use it when you need to measure which teams are using the system and where usage is low or declining.
Data
1767
🗂️
2h ago

Backlog Generator

Backlog Generator turns audit findings into sprint-ready work items with titles, effort estimates, acceptance criteria, and rationale. Use it when you need to convert review output into actionable tickets instead of running an audit or defining contribution guidelines.
Automation
1767
⚙️
2h ago

CI/CD Integration

CI/CD Integration generates pipeline files that automate design system checks such as token validation, component linting, accessibility scans, visual regression, and release gating. Use it when you need CI to enforce the same rules audit skills check manually.
DevOps
1767
📣
2h ago

Change Communication

Change Communication produces release notes, migration guidance, and team announcements for design system changes that have already been decided. Use it when you need to communicate a patch, enhancement, breaking change, or system update to consuming teams.
Writing
1767