A planning guide for choosing a software system’s structure and technology stack based on a project’s goals. A technology stack is the set of programming languages, frameworks, databases, and other tools used to build a system.

Use it after analysing a project’s vision to design its architecture and select technologies for each system layer. In workspace mode, it reads and writes the project’s architecture documents in the specified .aha-loop directory.

It gives technical decisions a documented rationale instead of choosing tools ad hoc. It also compares candidate technologies and checks that selected versions are current and stable.

How YougLin-dev/Aha-Loop configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to YougLin-dev/Aha-Loop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/YougLin-dev/Aha-Loop/main/.agents/skills/architect/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/YougLin-dev/Aha-Loop

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/youglin-dev/aha-loop/architect/github.svg)](https://agentmods.dev/skills/youglin-dev/aha-loop/architect)

Your own site

<a href="https://agentmods.dev/skills/youglin-dev/aha-loop/architect"><img src="https://agentmods.dev/badge/skills/youglin-dev/aha-loop/architect/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/youglin-dev/aha-loop/architect"><img src="https://agentmods.dev/badge/skills/youglin-dev/aha-loop/architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,217 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.02217
Opus 5.5	$0.00015	$0.00887
Sonnet 5.5	$0.00007	$0.00443
Haiku 4.5	$0.00004	$0.00222

Measured 2mo ago against content hash 52736e8a95e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

architect scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s "https://crates.io/api/v1/crates/tokio" | jq '.crate.max_stable_version'

.agents/skills/architect/SKILL.md · 402 lines

How it starts

The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Architect Skill

Research, evaluate, and decide on technology stack and system architecture based on project requirements.

Workspace Mode Note

When running in workspace mode, all paths are relative to .aha-loop/ directory:

Vision analysis: .aha-loop/project.vision-analysis.md
Architecture output: .aha-loop/project.architecture.md

The orchestrator will provide the actual paths in the prompt context.

The Job

Read project.vision-analysis.md for requirements
Research candidate technologies for each layer
Evaluate and compare options
Make decisions with documented rationale
Design system architecture
Output project.architecture.md

Core Principles

1. Prefer Latest Stable Versions

Always use the latest stable version of libraries unless there's a specific reason not to.

## Version Selection Process

1. Query official source for latest version:
   - Rust: crates.io API or `cargo search`
   - Node: npmjs.com or `npm view [pkg] version`
   - Python: pypi.org or `pip index versions`

2. Check release date and stability:
   - Released > 2 weeks ago (not bleeding edge)
   - No critical issues in GitHub issues
   - Changelog shows no breaking changes from common patterns

3. Document the version and why:
   - Record in project.architecture.md
   - Add to knowledge/project/decisions.md

2. Consider Long-term Maintenance

Active community and regular updates
Good documentation
Large ecosystem of plugins/extensions
Backed by reputable organization or strong community

3. Evaluate Total Cost

Learning curve for the team/AI
Bundle size / binary size
Runtime performance
Development velocity

Research Process

Step 1: Identify Technology Layers

Based on project type, identify which layers need decisions:

Layer	Examples
Language	Rust, TypeScript, Python, Go
Frontend Framework	React, Vue, Svelte, SolidJS
Backend Framework	Axum, Actix, Express, FastAPI
Database	PostgreSQL, SQLite, MongoDB
ORM/Query Builder	Diesel, SQLx, Prisma, Drizzle
Authentication	JWT, Sessions, OAuth providers
Deployment	Docker, Serverless, VPS
Testing	Built-in, Jest, Pytest, Vitest

Read the full file on GitHub · 402 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 402 lines · 37 tokens per session scan A 52736e8a95e9

Subscribe to this mod's changes

architect is a skill published in the GitHub repository YougLin-dev/Aha-Loop (178 stars, last pushed 9mo ago), licensed MIT. It adds 37 tokens to every session and 2,217 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning

architect next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
architectYougLin-dev/Aha-Loop	Skill	178	9mo ago	MIT	A	37	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	today	MIT	A	103	Claude Code

Aha-Loop: Skill for Claude Code