Canon Design Review

Architecture-level design review evaluating 15 Tier 2 best practices drawn from DDD (Evans), POEAA (Fowler), Release It! (Nygard), DDIA (Kleppmann), Team Topologies (Skelton/Pais), How Buildings Learn (Brand), and Systemantics (Gall). Auto-invoke when a PR touches: - Service definitions, infrastructure code, API boundaries, or database schemas - Files matching **/architecture*, **/design*, **/api/*, **/schema*, **/migrations/* - Any directory named services/, infrastructure/, platform/, domain/, core/ Also invoke when the user says: - "design review", "architecture review", "review the design"

5 stars 1 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add npow/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 npow/claude-skills --skill canon-design-review
Manual install
git clone --depth 1 https://github.com/npow/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/canon-design-review ~/.claude/skills/canon-design-review

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

From the SKILL.md

# Canon Design Review

Evaluates architecture-level practices across 3 assessment areas: **Structural Integrity**,
**Resilience & Operations**, and **Evolutionary Design**. Produces a scored assessment table
with verdict (PASS / WARN / BLOCK), evidence, and an overall recommendation.

This skill does not replace human design judgment — it surfaces objective signals and known
anti-patterns rooted in 7 seminal books. BLOCK verdicts must be resolved; WARN verdicts
require acknowledgment.

---

## Trigger detection

Before starting, identify what to review:

1. If a PR URL or number was given, fetch changed files:
   ```bash
   gh pr view <NUMBER> --json changedFiles,title,body | jq '.changedFiles[].path'
   ```
2. If a path was given, inspect directly.
3. If neither, ask: "What files or PR should I review?"

Scope the review to changed files only, but note systemic issues visible in context.

---

## Assessment area 1: Structural Integrity

*Source practices: CC-035 (DDD), CC-040 (POEAA/Fowler), CC-026 (GoF/Clean Code), CC-025 (Clean Code), CC-119/CC-151 (APoSD/Code Complete)*

### Practice 1 — Bounded Context Alignment (CC-035)

**What to assess:** Do the changed files respect domain boundaries? Look for domain model
objects crossing context lines without an Anti-Corruption Layer.

**Search signals:**
- Imports of domain entities from sibling service packages (e.g., `from order_service.models import User`)
- Shared mutable domain objects passed between bounded contexts
Read the full skill on GitHub

Details

Skill name
canon-design-review
Path
canon-design-review/SKILL.md
License
Apache-2.0
Repo updated
20 August 2026

FAQ

What does the Canon Design Review skill do?

Architecture-level design review evaluating 15 Tier 2 best practices drawn from DDD (Evans), POEAA (Fowler), Release It! (Nygard), DDIA (Kleppmann), Team Topologies (Skelton/Pais), How Buildings Learn (Brand), and Systemantics (Gall). Auto-invoke when a PR touches: - Service definitions, infrastructure code, API boundaries, or database schemas - Files matching **/architecture*, **/design*, **/api/*, **/schema*, **/migrations/* - Any directory named services/, infrastructure/, platform/, domain/, core/ Also invoke when the user says: - "design review", "architecture review", "review the design"

How do I install the Canon Design Review skill?

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

Is Canon Design Review popular?

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

Related skills

Autopilot

5

npow/claude-skills

Use when the user says "autopilot", "build this", "make it", "ship it", "just do it", "do it", "implement this", or gives a vague idea, spec, task list, or bug fix and expects autonomous execution. Handles decomposition, agent coordination, and verification automatically. "build me end to end", "go from idea to code", "do everything", "run this autonomously". Follows the Spec-Driven Development workflow: specify → clarify → plan → tasks → analyze → implement.

Productivity & Notes

Build Python Library

5

npow/claude-skills

Implements pip-installable Python libraries from scratch using src layout, pyproject.toml, and pytest. Use when the user asks to build, create, implement, or scaffold a Python library, package, pip package, middleware, SDK, or wrapper. Covers project scaffolding, proxy/wrapper patterns, provider-agnostic interfaces, async/sync support, and test infrastructure.

Software Development

Canon PR Review

5

npow/claude-skills

Review a PR against the top 20 Tier 2 LLM-enforceable best practices from 35 seminal software engineering books (Code Complete, Clean Code, A Philosophy of Software Design, Refactoring, Release It!, Designing Data-Intensive Applications, etc.). Produces a structured PR comment with four dimension scores (0-5 each), specific violations with line numbers, and an APPROVE / REQUEST_CHANGES / BLOCK decision. Auto-invoke when the user asks to: - "review PR", "canon review", "best practices review", "engineering standards review" - "score this PR", "check this PR against best practices" - Asks about

Git & Code Review

Code Quality Trends

5

npow/claude-skills

Use when checking code quality trends, tech debt accumulation, TODO/FIXME growth, test coverage ratios, PR size distribution, or generating a code quality report. Trigger phrases: code quality, code trends, tech debt trends, quality report.

Software Development

Deep Debug

5

npow/claude-skills

The single entry point for ALL debugging — bugs, test failures, CI failures, Metaflow run failures, Jenkins build failures, or any unexpected behavior. Trigger phrases include "debug this", "why is this failing", "find the bug", "fix the bug", "root cause", "what's wrong with", "this is broken", "diagnose", "troubleshoot", "investigate this failure", "the test is failing", "this used to work", "why doesn't this work", "where's the bug", "CI failed", "PR is red", "why did my flow fail", "build failed", "Jenkins failure". Composes specialized sub-skills internally (debug-pr for CI, debug-run for

Software Development

Working Effectively with Legacy Code

5

vnovakovits/claude-skills

Apply Michael Feathers's techniques for changing code that lacks tests — characterization tests, seams (object/link/preprocessor), dependency-breaking refactorings (Sprout Method, Extract Interface, Subclass and Override, Wrap Method, Break Out Method Object), effect sketches, and the Legacy Code Change Algorithm. Use when modifying inherited code without test coverage, when adding features to brittle code, when fixing bugs in code you don't yet understand, or when carving test points out of a tightly-coupled mess.

Software Development

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