Renaissance Architecture

A thoughtful counterpoint to cargo cult development that challenges you to build new things instead of variations on existing patterns. Invokes it when architecting features, reviewing designs, or making framework choices. The strength here is the pragmatic decision tables: when to move from SQLite to Postgres, monolith to services, local to cloud. It's opinionated about starting simple and adding complexity only when pain is measurable, not anticipated. The UI/UX section on immediate feedback and visible state is solid. Fair warning: this assumes you have the luxury of first-principles thinking. If you're building in a regulated industry or extending legacy systems, much of this won't apply.

skills.sh installs: 3.4K
GitHub stars: 491
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add bencium/bencium-marketplace --skill renaissance-architecture --agent claude-code

Installs into .claude/skills of the current project.

Files

Renaissance Architecture

Build genuinely new things. Not "X but for Y."

Core Philosophy

The problem isn't modern tools. It's building commentaries instead of creations.

Medieval scholars wrote commentaries on Aristotle instead of new philosophy. We build Star Wars spin-offs instead of new sci-fi. We add AI to existing workflows instead of asking what workflows become possible.

Renaissance architecture means: