skills.rest
EZoneLai
EZoneLaiCOMMUNITY
Explore all skills by this author →
GitHub

rsun-architect

Generates client-specific module architecture blueprints from OSS cluster briefs and contingency profiles.

Updated May 20, 2026
Search Tags:#multi-tenant#architecture design#module design#blueprint generation#contingency theory#oss reference#wbs estimation
One-click install
npx skills add https://github.com/EZoneLai/claude-plugin-ronsunai-os --skill rsun-architect-ezonelai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rsun-architect
Source: https://github.com/EZoneLai/claude-plugin-ronsunai-os/tree/main/commands/rsun-architect
Command: npx skills add https://github.com/EZoneLai/claude-plugin-ronsunai-os --skill rsun-architect-ezonelai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing a module architecture (CRM, CMS, ERP, dashboard, auth, etc.) that fits a specific client's constraints is hard: a one-size-fits-all blueprint ignores auditability, multi-tenancy, latency, and compliance differences. This Skill applies contingency theory to produce a tailored architecture variant blueprint for a chosen client profile, grounded in real OSS reference designs. ## Core Features & Use Cases - Contingency-Driven Design: Selects one of four client profiles (apex-gold-esg, rsun-dashboard-internal, legal-single-tenant, fortune-teller-d2c) or a custom 7-constraint profile, then writes a variant blueprint responding to those constraints. - OSS-Grounded Blueprints: Reads cluster briefs and BORROW-verdict OSS candidates via MCP tools (get_cluster_brief, get_candidates, list_ready_categories) so designs cite at least 3 real reference projects. - Three-Stage Authoring: Opus writes the judgment-critical skeleton (TL;DR, constraints, non-applicable scenarios), a Sonnet sub-agent fills sections 2-8 (naming, drizzle schema, Hono API, UI, WBS), then Opus reviews and assembles. - Use Case: Run /rsun-architect crm to produce a complete rsun-crm blueprint for the apex-gold-esg profile, including unified naming, tenant isolation strategy, API endpoints, WBS effort estimates (160 hr/MM, NT$120k/MM), and explicit boundaries on where the variant does not apply. ## Quick Start Ask the assistant to design an architecture blueprint for a module category, for example: run /rsun-architect crm and choose the apex-gold-esg client profile to generate the variant blueprint.

Frequently Asked Questions about rsun-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an architecture blueprint for a CRM module?▼

Run /rsun-architect crm and select a client profile such as apex-gold-esg. The skill reads the CRM cluster brief and OSS candidates, then produces an 8-section blueprint covering naming, data model, API endpoints, UI, WBS, and risks.

What client profiles does the contingency matrix support?▼

Four built-in profiles exist: apex-gold-esg (strong audit, multi-tenant, ESG compliance), rsun-dashboard-internal (speed-first SMB), legal-single-tenant (encryption, single-tenant), and fortune-teller-d2c (edge cache, high concurrency). Custom profiles can be added by defining 7 constraints.

How does the skill use OSS reference projects in architecture design?▼

It calls MCP tools to fetch cluster briefs and BORROW-verdict candidates, then requires at least 3 OSS sources to be cited in the blueprint's borrowing trade-off table. Designs must unify naming rather than mixing conventions from different repositories.

Can I add a custom client profile for architecture design?▼

Yes. Provide values for 7 constraints (auditability, multi-tenancy, compliance, latency budget, team size, data volume, customization). The profile is written as a YAML block into contingency-matrix.md, committed, then used for blueprint generation.

When should I use rsun-architect instead of rsun-sysdesign?▼

Use rsun-sysdesign for greenfield whole-system architecture selection across an entire product. Use rsun-architect for designing multiple client-specific variants of a single module category after the macro architecture is decided.

Why must the blueprint include a non-applicable scenarios section?▼

Contingency theory requires every design to know its boundaries. Section 9 forces the blueprint to name at least one client profile it does not fit and explain why, preventing a single variant from being misapplied to all customers.

Related Skills

Explore More Software Engineering Skills→
FRIKKernFRIKKern
6

deep-interview

Spawn a tmux interview workspace to extract structured requirements and generate goal.md.

Community
Advanced
FoundationForgeFoundationForge

architecture

Create and evaluate Architecture Decision Records with structured context and trade-offs.

Official
Advanced
Renzo-TognellaRenzo-Tognella

create-architectural-decision-memory

Document architectural decisions with rationale, alternatives, and affected modules.

Community
Advanced
Uxcel-LabUxcel-Lab
12

ux-design-from-scratch

Orchestrates foundations, components, screens, and flows into a complete from-scratch UX design build.

Official
Advanced