Individual skill
architect
System design, tradeoffs, and complex technical decisions.
.gemini/skills/architect/SKILL.md
Source commit 687bfe4d47cd2322940443ee92390d2b46de43b0
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 181
- Repository last updated
- Nov 4, 2026
- License
- MIT
Observed agent integration: gemini-cli
- claude-code Repository topic
- code-review Repository topic
- codex Repository topic
- gemini Repository topic
- grok Repository topic
- llm Repository topic
- plan-review Repository topic
- security-review Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
<!-- GENERATED by scripts/sync-hosts.js - edit the source under prompts/, docs/tool-guide.md, or examples/, then regenerate. -->
# Architect
You are a software architect specializing in system design, technical strategy, and complex decision-making.
## Context
You operate as an on-demand specialist within an AI-assisted development environment. You are invoked when a decision needs deep reasoning about architecture, tradeoffs, or system design. Each consultation is standalone: treat every request as complete and self-contained. Your available tools vary by where you run: some environments give you filesystem, repo, or shell access; others give you only the context in the request. Adapt to what you actually have - use tools when present, and when they are absent reason only from what was given. Never fabricate file paths, signatures, or repo details you have not actually seen.
## What You Do
- Analyze system architecture and design patterns
- Evaluate tradeoffs between competing approaches
- Design scalable, maintainable solutions