Architecture Friction Scan

Use when assessing a codebase for evidence-backed opportunities to deepen shallow modules, improve locality and AI navigability, or reduce seam and testing friction before choosing a refactor.

9 stars 3 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sandbaseai/workbuddy-skill --skill architecture-friction-scan
Manual install
git clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/architecture-friction-scan ~/.claude/skills/architecture-friction-scan

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

From the SKILL.md

# Architecture Friction Scan

Use this Skill before a broad refactor when the codebase feels difficult to understand, change, test, or navigate. The scan finds evidence-backed deepening opportunities; it does not silently choose an interface, edit production code, or turn every stylistic preference into architecture work.

## Establish scope and vocabulary

Read repository instructions, the domain glossary or context map, relevant ADRs, architecture documentation, test conventions, and the current working tree. Use the repository's canonical domain terms. For architecture, use precise terms: **module**, **interface**, **implementation**, **depth**, **seam**, **adapter**, **leverage**, and **locality**. Do not rename a module merely to make the report sound consistent.

If the user names a module, subsystem, pain point, or recent change, scope the scan there. Otherwise inspect a meaningful slice of commit history and prioritize hot spots: files and concepts that change repeatedly, attract bug fixes, have many consumers, or repeatedly require cross-module context. Record the scope and evidence window.

## Scan for real friction

Explore the code, tests, contracts, and history for:

- shallow modules whose interface is nearly as complicated as their implementation;
- behavior duplicated across callers instead of concentrated behind one interface;
- seams that leak provider, storage, ordering, retry, authorization, or error details;
Read the full skill on GitHub

Details

Skill name
architecture-friction-scan
Path
skills/architecture-friction-scan/SKILL.md
License
MIT
Repo updated
8 September 2026

FAQ

What does the Architecture Friction Scan skill do?

Use when assessing a codebase for evidence-backed opportunities to deepen shallow modules, improve locality and AI navigability, or reduce seam and testing friction before choosing a refactor.

How do I install the Architecture Friction Scan skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill architecture-friction-scan. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Architecture Friction Scan popular?

It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.

Related skills

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