Does it ever allow for complex code architectures?

Yes. Complexity is considered justified if it is backed by measured performance needs, proven scale requirements, regulatory compliance, or specific security threat models.

What kind of alternatives does the skill suggest?

It suggests simpler patterns like using standard libraries over frameworks, feature flags over complex plugin architectures, and direct function calls over generic repositories.

How does the Sanity Check skill identify over-engineering?

It scans for specific 'complexity smells' such as indirect solutions, premature abstractions (like factories for single implementations), and using heavy frameworks for simple CRUD tasks.

When is the best time to trigger this skill?

You should use it during the feature planning phase, when choosing new frameworks or libraries, or whenever a team member mentions a solution might be 'overkill' or 'too complex.'

Sanity Check

Name: Sanity Check
Author: outfitter-dev

byoutfitter-dev

•

Productivity & Workflow

Prevents over-engineering and promotes architectural simplicity by systematically identifying and challenging unnecessary technical complexity.

The Sanity Check skill serves as an architectural guardrail for Claude, ensuring that projects remain maintainable by providing a systematic pushback against premature abstraction, framework overkill, and 'performance theater.' It guides the development process through a structured workflow—Identify, Alternative, Question, and Document—to ensure every layer of complexity is justified by actual requirements rather than 'just in case' planning. Whether you are making build-vs-buy decisions or choosing between a library and a native implementation, this skill provides concrete patterns and escalation protocols to keep your codebase lean and focused.

Key Features

01Structured escalation protocol ranging from minor alternatives to high-risk hazards

022 GitHub stars

03Build-vs-buy decision framework for authentication, state management, and infrastructure

04Detection of common complexity smells like premature abstraction and performance theater

05Automated proposals for simpler alternatives with specific code examples

06Integrated workflow for documenting justified complexity via ADRs

Use Cases

01Evaluating whether to implement a custom solution or adopt an existing industry-standard library

02Reviewing architectural proposals to remove unnecessary layers of indirection and abstraction

03Determining if a heavy framework is overkill for a project's specific scale and performance needs

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add outfitter-dev/outfitter sanity-check

For use in Claude.ai and ChatGPT

Download Skill