Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component...
npx skills add YuniorGlez/gemini-elite-core --skill "code-architect"
Install specific skill from multi-skill repository
# Description
Senior Software Architect. Expert in AI-Native Systems, Modular Monoliths, and Edge-Cloud Orchestration for 2026 ecosystems.
# SKILL.md
name: code-architect
id: code-architect
version: 1.1.0
description: "Senior Software Architect. Expert in AI-Native Systems, Modular Monoliths, and Edge-Cloud Orchestration for 2026 ecosystems."
ποΈ Skill: Code Architect (v1.1.0)
Executive Summary
The code-architect is the visionary behind the system's structural integrity, scalability, and "Agent Friendliness." In 2026, architecture is no longer just about connecting components; it's about designing Reasoning Loops, enforcing Module Boundaries, and optimizing for Agent Experience (AX). This skill provides the high-level blueprint for building maintainable, elite-tier software in an AI-saturated world.
π Table of Contents
- Core Architectural Philosophies
- The "Do Not" List (Anti-Patterns)
- The Modern Modular Monolith
- AI-Native Architecture (Reasoning Layers)
- Edge Orchestration Standards
- Designing for Agent Experience (AX)
- Reference Library
ποΈ Core Architectural Philosophies
- Decoupling is Mandatory: Business logic (Domain) must be agnostic of infrastructure (DB, UI, External APIs).
- Contracts Over Implementation: Define strict interfaces (Zod/Valibot) before writing a single line of logic.
- AX-First Design: If an AI agent can't understand your module, it's poorly architected.
- Gradual Complexity: Start with a Modular Monolith; extract services only when horizontal scaling or team isolation requires it.
- Zero-Trust Security: Design every module as if its neighbors were potentially malicious.
π« The "Do Not" List (Anti-Patterns)
| Anti-Pattern | Why it fails in 2026 | Modern Alternative |
|---|---|---|
| Premature Microservices | High operational tax and latency. | Use Modular Monoliths. |
| Spaghetti Context | AI gets lost in tangled dependencies. | Use Explicit Module Interfaces. |
| Silent Failures | Agents cannot self-heal or retry. | Use Actionable Feedback APIs. |
| Hard-Coded Workflows | Limits system adaptability. | Use Goal-Driven Architectures. |
| Stateful Edge | Inconsistent UX and high egress. | Use Lazy Sync & Ephemeral State. |
π§± The Modern Modular Monolith
In 2026, we prioritize Development Velocity via:
- Strict Namespaces: modules/auth, modules/billing.
- In-Memory Event Bus: Decoupling modules without network overhead.
- Atomic Deployments: Ensuring all modules are always in sync.
See References: Modular Monoliths for the blueprint.
π€ AI-Native Architecture
We design systems that "Think":
- Guardian Agents: Architectural validation of every state change.
- Reasoning Logs: Storing the "Why" behind every AI decision.
- Context-Rich DBs: Merging SQL and Vector stores.
See References: AI-Native Architecture for patterns.
π Edge Orchestration
- Global Routing: Requests land on the node closest to the user.
- WASM Runtimes: Minimal cold starts for edge functions.
- Policy-Driven Placement: Moving data based on usage patterns.
π Reference Library
Detailed deep-dives into Architectural Excellence:
- Modular Monoliths: The modern standard for speed and scale.
- AI-Native Design: Systems with integrated reasoning.
- Edge Orchestration: Global patterns for 2026.
- Agent Experience (AX): Designing for machine users.
Updated: January 22, 2026 - 19:20
# Supported AI Coding Agents
This skill is compatible with the SKILL.md standard and works with all major AI coding agents:
Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.