Skip to content
Back to search

pbk-design-skills

MarketplaceWorks with Claude CodeGitHub

Claude skills for design practice and brand systems: brief to handoff, brand identity, art direction, token drift.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pitchblacknight--claude-design-skills/badge.svg)](/listings/pitchblacknight--claude-design-skills)

HTML

<a href="/listings/pitchblacknight--claude-design-skills"><img src="/api/listings/pitchblacknight--claude-design-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

**Claude Code**, as a plugin marketplace:

/plugin marketplace add PitchBlacKnight/claude-design-skills
/plugin install design-practice@pbk-design-skills
/plugin install brand-systems@pbk-design-skills

On Claude Code 2.1.275 or later, one line per plugin also works: `/plugin install brand-systems --marketplace PitchBlacKnight/claude-design-skills`.

**Any setup that reads skill folders:** copy a folder from `plugins/*/skills/` into your skills directory, for example `~/.claude/skills/`. Each folder is one skill. Only the `description` line of each `SKILL.md` stays in context until a task matches.

**A Claude project:** add the skill folders to the project and paste `plugins/design-practice/PROJECT-INSTRUCTIONS.md` into the project instructions, so the house rules apply to everything.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 38 lines
  1. {
  2. "name": "pbk-design-skills",
  3. "owner": {
  4. "name": "Mikel Rosenthal",
  5. "email": "mikelrosenthal@me.com",
  6. "url": "https://mikelrosenthal.com"
  7. },
  8. "metadata": {
  9. "description": "Claude skills for design practice and brand systems, by Mikel Rosenthal.",
  10. "version": "1.0.0"
  11. },
  12. "plugins": [
  13. {
  14. "name": "design-practice",
  15. "source": "./plugins/design-practice",
  16. "description": "Nine skills that carry a product engagement from a raw brief to a developer handoff.",
  17. "version": "1.0.0",
  18. "author": {
  19. "name": "Mikel Rosenthal",
  20. "email": "mikelrosenthal@me.com",
  21. "url": "https://mikelrosenthal.com"
  22. },
  23. "license": "MIT"
  24. },
  25. {
  26. "name": "brand-systems",
  27. "source": "./plugins/brand-systems",
  28. "description": "Brand identity, art direction and a token drift check, written so a model can run them.",
  29. "version": "1.0.0",
  30. "author": {
  31. "name": "Mikel Rosenthal",
  32. "email": "mikelrosenthal@me.com",
  33. "url": "https://mikelrosenthal.com"
  34. },
  35. "license": "MIT"
  36. }
  37. ]
  38. }
README.md · README · 55 lines
  1. # Claude design skills
  2. Skills for Claude that carry design work the same way every time: a product engagement from brief to handoff, and a brand from idea to a system other people can apply. Written by Mikel Rosenthal, a Chicago designer with 23 years in product, brand and design systems.
  3. Every skill carries rules about what it must not do. Never invent a number. Never report a count you did not count. Say what you could not test. The refusals do more work than the procedures.
  4. ## What is here
  5. | Plugin | Skills | For |
  6. |---|---|---|
  7. | `design-practice` | brief-intake, ds-inventory, heuristic-audit, research-synthesis, flow-map, copy-standards, a11y-spec, critique, handoff-spec | A product engagement, from a raw brief to the developer package |
  8. | `brand-systems` | brand-identity, art-direction, ds-drift | A brand identity, the visual direction of a build, and a check that Figma and code tokens agree |
  9. The design-practice plugin also holds a demo runbook, project instructions and seven example outputs. The examples are a composite project, not a client engagement, and their numbers are invented for illustration.
  10. ## Install
  11. **Claude Code**, as a plugin marketplace:
  12. ```
  13. /plugin marketplace add PitchBlacKnight/claude-design-skills
  14. /plugin install design-practice@pbk-design-skills
  15. /plugin install brand-systems@pbk-design-skills
  16. ```
  17. On Claude Code 2.1.275 or later, one line per plugin also works: `/plugin install brand-systems --marketplace PitchBlacKnight/claude-design-skills`.
  18. **Any setup that reads skill folders:** copy a folder from `plugins/*/skills/` into your skills directory, for example `~/.claude/skills/`. Each folder is one skill. Only the `description` line of each `SKILL.md` stays in context until a task matches.
  19. **A Claude project:** add the skill folders to the project and paste `plugins/design-practice/PROJECT-INSTRUCTIONS.md` into the project instructions, so the house rules apply to everything.
  20. ## Anatomy of a skill
  21. Every skill has the same parts in the same order, so a second person gets comparable output:
  22. ```
  23. ---
  24. name: heuristic-audit
  25. description: When to load it, in one line
  26. ---
  27. # Title
  28. ## When to use
  29. ## Procedure
  30. ## Severity scale (or rubric)
  31. ## Rules
  32. ## Bundled files
  33. ```
  34. ## More
  35. - The skill library, with a side-by-side example: https://mikelrosenthal.com/process/skill-library.html
  36. - NorthStar, a design system with files written for AI agents: https://mikelrosenthal.com/northstar/
  37. - Contact: mikelrosenthal@me.com
  38. MIT licensed. Use them, change them, credit appreciated.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.