Architect logo

Architect

Community
Omar-Obando
architect

System architecture design skill with pattern recognition, trade-off analysis, and documentation. Use when designing new features, evaluating architecture decisions, or planning system refactoring.

Overview

PublisherOmar-Obando
Repositoryqwen-orchestrator
Skill namearchitect
Stars
53
Forks
13
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Omar-Obando on GitHub. Read the source before you install it.

Installation

Install the Architect AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/architect
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Omar-Obando/qwen-orchestrator.git /tmp/qwen-orchestrator
mkdir -p .claude/skills
cp -r /tmp/qwen-orchestrator/skills/architect .claude/skills/architect
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Architect in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Architect on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Architect is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Architect Skill — System Design Expert

This skill provides comprehensive architecture design guidance with evidence-based decision making.

Design Principles

SOLID

  • Single Responsibility: One reason to change
  • Open/Closed: Open for extension, closed for modification
  • Liskov Substitution: Subtypes must be substitutable
  • Interface Segregation: Many specific interfaces > one general
  • Dependency Inversion: Depend on abstractions, not concretions

CUPID

  • Composable: Works well with other components
  • Understandable: Clear purpose and usage
  • Predictable: Behaves as expected
  • Idempotent: Same operation, same result
  • Domain-focused: Names and structure reflect the domain

Architecture Patterns

Monolith vs Microservices Decision Matrix

FactorMonolithMicroservices
Team sizeSmall (1-5)Large (5+)
Deployment frequencyLowHigh
Scaling needsUniformVariable per component
ComplexityLowHigh
Data consistencyEasyHard (eventual)

Recommended Patterns by Domain

DomainPatternWhy
API LayerHexagonal/CleanTestability, flexibility
Data AccessRepository PatternAbstraction from storage
EventsEvent SourcingAudit trail, replay
CachingWrite-throughConsistency
AuthRBAC + ABACFine-grained control

Decision Record Template

markdown
## ADR-[N]: [Decision Title]

### Status: PROPOSED | ACCEPTED | DEPRECATED | SUPERSEDED

### Context

[What is the issue that we're seeing that is motivating this decision?]

### Decision

[What is the change that we're proposing/making?]

### Alternatives Considered

1. [Alternative 1]: [Pros] / [Cons]
2. [Alternative 2]: [Pros] / [Cons]

### Consequences

**Positive**: [Benefits]
**Negative**: [Costs/Risks]
**Neutral**: [Side effects]

### Reversibility

[How hard would it be to undo? What is the blast radius?]

Design Review Checklist

  • Requirements clearly understood
  • At least 2 alternatives evaluated
  • Trade-offs documented
  • No circular dependencies introduced
  • Layer boundaries respected
  • Error handling strategy defined
  • Performance characteristics understood
  • Security implications evaluated
  • Testability ensured
  • Documentation planned

When NOT to Use

Do NOT use this skill when:

  • Writing application business logic (use domain-driven skill for complete business modules with all sub-modules)
  • Designing database schemas (use database-design skill for normalization, indexing, and query optimization)
  • Reviewing code for quality issues (use code-review skill for comprehensive code audits)
  • Writing API endpoint implementations (use api-design skill for REST/GraphQL endpoint patterns)
  • Performing security audits (use security-auditor skill for vulnerability analysis and threat modeling)
  • Analyzing deployment configurations (use deployment skill for CI/CD pipelines and infrastructure)
  • Writing SQL queries (use sql-best-practices skill for query optimization and N+1 prevention)
  • Reviewing git workflows (use git-workflow skill for branching strategies and commit conventions)
  • Redesigning existing websites (use website-redesign skill for UI/UX improvements from URLs/screenshots)

Frequently asked questions

What does the Architect AI skill do?

System architecture design skill with pattern recognition, trade-off analysis, and documentation. Use when designing new features, evaluating architecture decisions, or planning system refactoring.

Why use Architect on TypingMind?

Because you install it once and use it with any model. Architect is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Architect in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/architect. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Architect?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Architect?

As many as you like. As long as a model supports skills, you can use Architect with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Architect AI skill free?

Yes. It is published on GitHub by Omar-Obando under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇