architecture-foundation

# Architecture Foundation ## Overview Use this skill to turn an architecture discussion into explicit boundaries, contracts, validation gates, and a small execution plan. The goal is not to copy an admired project, but to identify the project's shape and choose the minimum architecture that keeps ownership, effects, errors, and tests clear. For large existing repos, first explain the architecture they already have, then decide whether the work is boundary creation, boundary completion, or boundary deletion. ## When To Use - The user asks "what architecture should this use?", "is this stacked work?", "make a complete spec", "design the runtime", or "compare good libraries". - The change touches runtime, state ownership, adapters, plugins, event loops, rendering, schedulers, persistence, or cross-module contracts. - A repo has many issues/PRs that look individually valid but may not converge on one architecture. - A mature repo has duplicated paths, compatibility shims, generated configs, workflow definitions, or docs that may disagree about the source of truth. - A new skill, framework, library, or large feature needs a foundation guide before implementation. Do not use this for small, local fixes where the existing architecture is obvious and no boundary decision is needed. ## Workflow 1. Search first. - Inspect existing architecture docs, entrypoints, manifests, module trees, public APIs, open issues/PRs, and tests before proposing new structure. - If the ...