Cupid Properties

Apply Dan North's CUPID properties (Composable, Unix philosophy, Predictable, Idiomatic, Domain-based) — a 2022 alternative framing to SOLID, oriented toward "joyful code" and properties to lean toward rather than principles to obey. Use when evaluating code quality, when SOLID feels like a rulebook rather than a guide, or when looking for a complementary lens that emphasizes ergonomics, composability, and fit with the surrounding ecosystem.

5 stars 2 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill cupid-properties
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/cupid-properties ~/.claude/skills/cupid-properties

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# CUPID Properties (Dan North, 2022)

Apply this skill when evaluating or designing code with an emphasis on *ergonomics, composability, and joy* — what code feels like to work with, not just whether it satisfies abstract principles. CUPID is Dan North's 2022 response to the perception that SOLID had become a rulebook recited without understanding.

## Core Philosophy

**Properties, not principles.** SOLID names principles — discrete rules. CUPID names *properties* — qualities to lean toward, never fully achieved, useful as directions of travel. You don't "comply with" CUPID; you cultivate it.

**Joy as a quality signal.** Joyful code is easier to read, easier to change, more satisfying to work with — and not coincidentally, it tends to be more correct. When code resists you, the discomfort is design feedback. CUPID names the properties that make code feel right.

**Born from critique.** North spent a decade observing that SOLID was often invoked as cargo-cult — "make it SOLID" as a vague approval, "this violates LSP" as a vague objection — without people understanding the underlying tensions. CUPID is intended to invite design judgment rather than rule-checking.

**Complementary, not opposed.** CUPID does not replace SOLID. Many CUPID-joyful designs satisfy SOLID; many SOLID-clean designs are CUPID-joyful. Use both as lenses.

---

## C — Composable

**Code is composable when it plays well with others.**

Composable code:
- Has a small, focused surface area.
Read the full skill on GitHub

Details

Skill name
cupid-properties
Path
plugins/engineering-practices/skills/cupid-properties/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Cupid Properties skill do?

Apply Dan North's CUPID properties (Composable, Unix philosophy, Predictable, Idiomatic, Domain-based) — a 2022 alternative framing to SOLID, oriented toward "joyful code" and properties to lean toward rather than principles to obey. Use when evaluating code quality, when SOLID feels like a rulebook rather than a guide, or when looking for a complementary lens that emphasizes ergonomics, composability, and fit with the surrounding ecosystem.

How do I install the Cupid Properties skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Cupid Properties popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

Debugging

5

vnovakovits/claude-skills

Find and fix bugs systematically with David Agans's "Debugging — The 9 Indispensable Rules" (2002) and Andreas Zeller's "Why Programs Fail" (2nd ed. 2009), led by a feedback-loop-first discipline — no theory until one fast, deterministic command goes red on this exact bug. Covers the defect → infection → failure chain, Zeller's TRAFFIC procedure and scientific method (falsifiable hypotheses, a debugging log), Agans's nine rules (make it fail, quit thinking and look, divide and conquer, change one thing at a time, check the plug, if you didn't fix it it ain't fixed), minimising repros, delta de

Software Development

Create Master Skill

8

Freddy-CHEN-ux/00_claude_skills

Create a master system skill (shared resource library) for any integration. Load when user mentions "create master skill", "new master skill", "shared skill library", "integration master", or wants to build a reusable skill foundation for multiple related skills.

Software Development

Dev API Design

8

Freddy-CHEN-ux/00_claude_skills

Production-grade API design patterns for REST, GraphQL, and gRPC. Covers API architecture, OpenAPI/Swagger specs, versioning strategies, authentication flows, rate limiting, pagination, error handling, and documentation best practices for modern API development.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.