Brainstorm Prototypes
Neeeophytee/finding-unknowns-skills
Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to.
Software architecture and UI/UX principles for building genuinely new solutions, not derivative work.
Install Renaissance Architecture
$ npx skills add bencium/bencium-marketplace --skill renaissance-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bencium/bencium-marketplace renaissance-architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/renaissance-architecture/skills/renaissance-architecture .claude/skills/renaissance-architecture && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "renaissance-architecture" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/renaissance-architecture/skills/renaissance-architecture into .claude/skills/renaissance-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renaissance-architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bencium/bencium-marketplace/tree/main/renaissance-architecture/skills/renaissance-architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bencium/bencium-marketplace --skill renaissance-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bencium/bencium-marketplace renaissance-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/renaissance-architecture/skills/renaissance-architecture .agents/skills/renaissance-architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "renaissance-architecture" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/renaissance-architecture/skills/renaissance-architecture into .agents/skills/renaissance-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renaissance-architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bencium/bencium-marketplace --skill renaissance-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bencium/bencium-marketplace renaissance-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/renaissance-architecture/skills/renaissance-architecture .cursor/skills/renaissance-architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "renaissance-architecture" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/renaissance-architecture/skills/renaissance-architecture into .cursor/skills/renaissance-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renaissance-architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bencium/bencium-marketplace.git --path renaissance-architecture/skills/renaissance-architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bencium/bencium-marketplace --skill renaissance-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bencium/bencium-marketplace renaissance-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/renaissance-architecture/skills/renaissance-architecture .gemini/skills/renaissance-architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "renaissance-architecture" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/renaissance-architecture/skills/renaissance-architecture into .gemini/skills/renaissance-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renaissance-architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bencium/bencium-marketplace renaissance-architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bencium/bencium-marketplace --skill renaissance-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/renaissance-architecture/skills/renaissance-architecture .github/skills/renaissance-architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "renaissance-architecture" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/renaissance-architecture/skills/renaissance-architecture into .github/skills/renaissance-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renaissance-architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bencium/bencium-marketplace --skill renaissance-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bencium/bencium-marketplace renaissance-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bencium/bencium-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/renaissance-architecture/skills/renaissance-architecture .opencode/skills/renaissance-architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "renaissance-architecture" agent skill from https://github.com/bencium/bencium-marketplace/tree/main/renaissance-architecture/skills/renaissance-architecture into .opencode/skills/renaissance-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "renaissance-architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
renaissance-architecture- GitHub stars
- 446
- Token cost
- ~3.3k tokens
- SKILL.md length
- 1,582 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Software architecture and UI/UX principles for building genuinely new solutions, not derivative work.
- Works in 10 steps: Simplicity as Default, Complexity When… → Framework Choices → Human-Legible Systems → …
- Designing features
- SKILL.md covers Core Philosophy, Architecture Principles, Cloud & Infrastructure and UI/UX Philosophy, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Renaissance Architecture is an agent skill from bencium/bencium-marketplace. Software architecture and UI/UX principles for building genuinely new solutions, not derivative work. Use when designing features, architecting software, brainstorming apps, reviewing designs, or during strategy discussions. Focuses on first-principles thinking, simplicity where it matters, and creating rather than commenting.
Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering UI design, Software architecture and Brainstorming. It works with React. The repository describes itself as: comprehensive skills based on the Anthropic Skills guide and our design and development philosophy. The licence is MIT.
When your agent uses it
- Designing features
- Architecting software
- Brainstorming apps
- Reviewing designs
Example prompts
- “/renaissance-architecture”
Requirements
- Python 3
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5de46a3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Renaissance Architecture loads about 3.3k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 1,582 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from bencium/bencium-marketplace at commit 5de46a3, republished under its MIT licence (© bencium). 1,582 words, ~3,307 tokens.
Download SKILL.mdSave it as
.claude/skills/renaissance-architecture/SKILL.md (or your agent's skills folder).- name
- renaissance-architecture
- description
- Software architecture and UI/UX principles for building genuinely new solutions, not derivative work. Use when designing features, architecting software, brainstorming apps, reviewing designs, or during strategy discussions. Focuses on first-principles thinking, simplicity where it matters, and creating rather than commenting.
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:
- First-principles thinking about WHAT to build
- Pragmatic choices about HOW to build it
- Creating new paradigms, not extending old ones
- Using modern tools to make genuinely new things possible
Architecture Principles
1. Simplicity as Default, Complexity When Earned
Start simple, add complexity when pain is measurable.
| Start With | Move To | When |
|---|---|---|
| SQLite | Postgres | >10 concurrent writers, >100GB, need PostGIS/full-text |
| Single file | Multiple files | File exceeds ~500 LOC or has multiple responsibilities |
| Monolith | Services | Team can't work on same codebase, or genuine scale isolation needed |
| Static hosting | Server | Need auth, real-time, or server-side computation |
| Local state | Cloud sync | Multi-device is a real user need, not assumed |
Not dogma, but defaults. Violate with documented reasoning.
2. Framework Choices
Use frameworks when they provide genuine leverage.
| Framework | When to Use | When to Avoid |
|---|---|---|
| Next.js | Full-stack React apps, SSR matters, team knows it | Simple static sites, non-React teams |
| Remix | Data-heavy apps, progressive enhancement priority | Simple SPAs, unfamiliar teams |
| Astro | Content sites, partial hydration valuable | Highly interactive apps |
| SvelteKit | Smaller bundles critical, team willing to learn | Large existing React codebases |
| Rails/Django | Rapid CRUD apps, admin panels, proven patterns | Real-time heavy, team prefers JS |
| FastAPI | Python APIs, async matters | Simple scripts, team prefers other languages |
| Hono/Elysia | Edge functions, lightweight APIs | Complex apps needing full framework |
The question isn't "framework or not" but "does this framework serve the thing we're creating, or are we creating something that serves the framework?"
3. Human-Legible Systems
Configuration
- YAML/JSON are fine - the format isn't the problem
- Problem is: 500-line configs with nested conditionals
- Good: Config a new team member can read and modify in 10 minutes
- Document non-obvious settings inline
Error messages that teach
- What happened
- Why it happened
- What to do about it
- Link to docs if complex
Logs you can understand
- Structured logging (JSON) for machines
- Human-readable format for development
- Timestamps, context, severity
- Searchable without specialized tools
Documentation lives WITH code
- README in each significant directory
- API docs generated from code
- Architecture decisions recorded (ADRs)
- External wikis for onboarding/process only
4. Local-First Where It Matters
Not "never use cloud" but "don't require cloud unnecessarily."
| Feature | Local-First Approach | Cloud When |
|---|---|---|
| Core functionality | Works offline | Never required for core |
| Data storage | SQLite/local storage | Sync, backup, multi-device |
| Computation | Client-side where possible | Heavy processing, shared resources |
| Auth | Local sessions work | OAuth for third-party, enterprise SSO |
State should be inspectable
- Serialize state to file for debugging
- State machines explicit, not implicit
- Reproducible from snapshot
Sync as enhancement
- Local is source of truth where possible
- Sync failures don't break the app
- Conflict resolution explicit, user-controlled
5. Composition Mindset
Libraries over frameworks when:
- You need one capability, not an ecosystem
- You want to control the architecture
- Exit cost matters more than speed
Frameworks over libraries when:
- Team expertise exists
- Time-to-market critical
- Convention over configuration is valuable
- The framework's opinions align with your needs
APIs expose primitives
- Convenience methods are fine
- But power users can access lower levels
- Don't hide the machine
Minimize exit costs
- Data exportable in standard formats
- Avoid proprietary lock-in where practical
- Document the exit path even if you never use it
Cloud & Infrastructure
When Cloud Makes Sense
| Use Case | Cloud Appropriate | Local/Edge Better |
|---|---|---|
| Auth | Enterprise SSO, OAuth providers | Simple username/password |
| Storage | Multi-device sync, collaboration | Single-user, offline-capable |
| Compute | Heavy ML inference, video processing | Text processing, simple transforms |
| Database | Multi-writer, global distribution | Single user, local-first |
| Real-time | Multi-user collaboration | Single-user state |
Cloud Pragmatically
- Serverless for spiky, unpredictable loads
- Edge functions for latency-sensitive operations
- Managed databases when ops overhead > cost
- Self-hosted when control/cost/compliance require it
The question: Does cloud serve your users, or does it serve your assumptions about scale you don't have?
UI/UX Philosophy
1. Immediate Feedback
<100ms for user actions, honest progress for longer operations
- Optimistic updates where safe (can rollback)
- Progress indicators that reflect actual work
- Spinners are fine - they indicate honest work
- Skeleton screens for predictable loading patterns
Loading states should:
- Show what's happening
- Estimate time when possible
- Allow cancellation for long operations
- Never fake progress
2. Visible State
User always knows what the system is doing
- Status visible without digging
- Background processes surfaced
- Errors prominent, not hidden
- System explains its decisions when non-obvious
No black boxes
- User can understand why something happened
- Audit trail for important actions
- State inspectable in dev tools
3. Spatial Consistency
Things stay where you put them
- No layout shifts after load
- No rearranging "for the user"
- Muscle memory works
- Consistent component placement
Predictable navigation
- Back button works
- URLs are bookmarkable and shareable
- State survives refresh
- Deep linking works
4. Undo & Recovery
Implemented at the data layer, not just UI
- Soft delete by default
- Versioned state where valuable
- Recovery path documented
- "Are you sure?" is not a substitute for undo
Destructive actions
- Confirmation for irreversible operations
- Grace period before permanent deletion
- Clear communication of consequences
5. Respect Attention
Notifications
- User opts in explicitly
- Meaningful, not engagement-driven
- Batched where appropriate
- Easy to adjust or disable
Modals & Interruptions
- User-initiated, not system-initiated
- Dismissable
- Don't trap focus unnecessarily
- Keyboard accessible
Autoplay
- Never for audio
- Video only with explicit user intent
- Motion respects prefers-reduced-motion
Defaults over customization
- Good defaults eliminate settings
- Power user options available but not required
- Complexity progressive
What This Rejects
Derivative Thinking
- "X but for Y" without asking if Y needs X
- Features because competitors have them
- Patterns because tutorials use them
- Architecture because FAANG does it
Cargo Cult Engineering
- "Best practices" from different-scale companies
- Microservices for 3-person teams
- Kubernetes for single-server loads
- OAuth for internal tools
Show full SKILL.md (626 more words)Show less
Premature Complexity
- Abstraction layers "for future flexibility"
- Scale architecture before scale problems
- Features before foundations work
- Real-time before single-user works
Process Over Thinking
- Scrum ceremonies replacing actual thought
- Documentation for compliance, not clarity
- Meetings about meetings
- Roadmaps pretending to predict
Application
When Reviewing Designs
First-Principles Check
- What new thing does this create? (Not "what existing thing does it extend?")
- Why does this need to exist?
- What becomes possible that wasn't before?
Simplicity Check
- Is complexity earned or assumed?
- Can a new developer understand this in an hour?
- What's the simplest version that solves the core problem?
Tool Fitness Check
- Do tool choices serve the creation, or does creation serve the tools?
- Is the framework justified by team expertise + problem fit?
- Are cloud dependencies necessary or assumed?
Human-Legibility Check
- Can someone read the config and understand it?
- Do error messages teach?
- Is documentation where developers will find it?
UI/UX Check
- Is feedback immediate or honestly progressive?
- Can users see what the system is doing?
- Is everything recoverable/undoable?
- Are interruptions user-initiated?
When Generating Solutions
Start by asking:
- What genuinely new thing are we creating?
- What's the simplest architecture that enables it?
- What complexity is earned by real constraints?
Default to:
- Simplest tool that works
- Framework if team knows it and it fits
- Local-first where possible
- Cloud where genuinely needed
Add complexity when:
- Pain is measurable, not theoretical
- Team agrees on the tradeoff
- The path back to simple is documented
Threshold Triggers
When to upgrade from defaults:
| From | To | Trigger |
|---|---|---|
| SQLite | Postgres | >10 concurrent writers OR >100GB data OR need PostGIS/full-text search |
| Monolith | Services | Team can't work on same codebase OR genuine scale isolation needed |
| Static | Server | Need auth, real-time, or server-side computation |
| Local storage | Cloud sync | Multi-device is validated user need, not assumption |
| Library | Framework | Team expertise exists AND time-to-market critical AND framework opinions align |
| Simple | Complex | Pain is measurable, not theoretical |
Justified Exceptions
Complexity is acceptable when:
- Frameworks: Team expertise exists AND problem fits framework opinions AND time-to-market matters
- Cloud dependencies: Multi-user collaboration OR heavy compute OR compliance requires it
- Microservices: Teams can't coordinate on monolith OR genuine scale isolation needed
- Heavy tooling: Build time investment pays off in development velocity
Document the reasoning. Future you will thank present you.
Pragmatic Defaults
Start simple, add complexity when pain is measurable.
- Begin with the simplest architecture that could work
- Wait for real problems, not imagined ones
- Measure before optimizing
- Document why you're adding complexity
- Ensure the path back to simple exists
Premature complexity is technical debt with interest.
Anti-Dogma Clause
These are defaults, not laws. Violate with documented reasoning.
Every principle here has valid exceptions. The goal isn't purity - it's intentionality.
Valid reasons to deviate:
- Team expertise strongly favors different approach
- Business timeline requires faster path
- Regulatory/compliance requirements
- Measured performance needs
- User research contradicts assumption
Invalid reasons to deviate:
- "Everyone does it this way"
- "We might need it someday"
- "The tutorial used this"
- "It's best practice" (without understanding why)
When you deviate, write down why. One sentence in a comment, ADR, or README.
Quick Reference
| Dimension | Default | Upgrade When |
|---|---|---|
| Storage | SQLite | Concurrent writes, scale, features |
| Framework | Yes, if team knows it | Build from scratch if simpler |
| Cloud | Where genuinely needed | Don't assume, validate |
| Config | YAML/JSON, well-documented | - |
| Errors | Teaching messages | - |
| Loading | Spinners with honest progress | - |
| State | Visible, inspectable | - |
| Undo | Data-layer versioning | - |
| Complexity | Earned, not assumed | Document reasoning |
The Core Question
When designing anything, ask:
"Am I creating something new, or commenting on something that exists?"
Renaissance architecture isn't about rejecting modern tools. It's about using them to build genuinely new things - not just another variation on established patterns.
Medieval scholars could only write commentaries because they believed truth was revealed in the past. We have no such limitation. We can create.
© bencium, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in renaissance-architecture/skills/renaissance-architecture of bencium/bencium-marketplace.
Open the folder on GitHubat commit 5de46a3
Compare with similar skills
Renaissance Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Renaissance Architecture this skillbencium/bencium-marketplace | 446 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Brainstorm PrototypesNeeeophytee/finding-unknowns-skills | 343 | — | ~492 | Automated safety check: Pass | MIT | |
| Audit Flowzebbern/claude-code-guide | 4.7k | — | ~4.2k | Automated safety check: Pass | MIT | |
| Visual Companionhashgraph-online/awesome-codex-plugins | 1.3k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Electron Multi-Process ArchitectureiOfficeAI/AionUi | 33k | 1 repos | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Evolutionary Modular Architecturetech-leads-club/agent-skills | 7k | — | ~3.7k | Automated safety check: Pass | CC-BY-4.0 |
Similar skills
Audit Flow
zebbern/claude-code-guide
Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export.
Visual Companion
hashgraph-online/awesome-codex-plugins
Browser-based visual brainstorming companion for showing mockups, diagrams, and visual options.
Electron Multi-Process Architecture
iOfficeAI/AionUi
Tells the agent where new code belongs in an Electron multi-process project and which APIs each process may use, with rules for new bridges, services, agents and workers.
Evolutionary Modular Architecture
tech-leads-club/agent-skills
Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.
Chatgpt App Builder
alpic-ai/skybridge
Guide developers through creating and updating ChatGPT plugins.
More from bencium/bencium-marketplace
All 13 skills in this repoVanity Engineering Review
bencium/bencium-marketplace
Reviews codebases, architectures, PRs, and technical plans for vanity engineering — code and systems built for the developer's ego, resume, or intellectual pleasure rather than delivering user or…
Adaptive Communication
bencium/bencium-marketplace
A skill your agent uses when detecting ambiguous user intent, hedging language, open-ended framing, personal context before requests, or when unsure whether user wants exploration vs direct answer.
Insurgent Campaign
bencium/bencium-marketplace
Grassroots-first campaign design for anyone being outspent — startups vs.
Eu AI Act Reviewer
bencium/bencium-marketplace
Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions.
Hungarian Humanizer
bencium/bencium-marketplace
Detect and remove AI-generated markers from Hungarian text, making it sound like a native Hungarian speaker wrote it.
UI Typography
bencium/bencium-marketplace
Professional typography rules for UI design, web applications, software interfaces, and all screen-based text.
Related
Works with
Questions about Renaissance Architecture
What does Renaissance Architecture do?
Software architecture and UI/UX principles for building genuinely new solutions, not derivative work. Renaissance Architecture is an agent skill from bencium/bencium-marketplace. Software architecture and UI/UX principles for building genuinely new solutions, not derivative work.
When should I use Renaissance Architecture?
Renaissance Architecture fits situations like: designing features; architecting software; brainstorming apps; reviewing designs.
How do I install Renaissance Architecture in Claude Code?
Run `npx skills add bencium/bencium-marketplace --skill renaissance-architecture -a claude-code`. Or copy the skill folder (renaissance-architecture/skills/renaissance-architecture in bencium/bencium-marketplace) into .claude/skills/renaissance-architecture in your project. Claude Code loads it when a task matches its description.
How do I install Renaissance Architecture in Codex?
Run `npx skills add bencium/bencium-marketplace --skill renaissance-architecture -a codex`. Or copy the skill folder (renaissance-architecture/skills/renaissance-architecture in bencium/bencium-marketplace) into .agents/skills/renaissance-architecture in your project. Codex loads it when a task matches its description.
Can I use Renaissance Architecture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bencium/bencium-marketplace --skill renaissance-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/renaissance-architecture, .gemini/skills/renaissance-architecture, .github/skills/renaissance-architecture and .opencode/skills/renaissance-architecture in your project.
What does Renaissance Architecture need to run?
SKILL.md names no scripts, command-line tools or credentials: Renaissance Architecture is instructions for the agent only. Our summary lists: Python 3.
Does Renaissance Architecture access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Renaissance Architecture safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Renaissance Architecture use?
Renaissance Architecture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Renaissance Architecture use?
About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Renaissance Architecture?
Skills that share tags, products or a category with Renaissance Architecture: Brainstorm Prototypes (Neeeophytee/finding-unknowns-skills, 343 stars), Audit Flow (zebbern/claude-code-guide, 4.7k stars), Visual Companion (hashgraph-online/awesome-codex-plugins, 1.3k stars) and Electron Multi-Process Architecture (iOfficeAI/AionUi, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Renaissance Architecture?
bencium (a GitHub user) maintains it in bencium/bencium-marketplace, which has 446 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 4, 2026.
Source: bencium/bencium-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.