sjinks/architecture-skills
Architecture and design workflow skills for AI agents: recording decisions, comparing tradeoffs, designing interface contracts, reviewing dependency choices, designing failure behavior, building type-safe designs, and planning development containers.
Use when: writing, rewriting, or auditing an architecture decision record (ADR), design decision log entry, or technical decision write-up: context, decision drivers, options considered with costs, chosen option, positive and negative consequences, and revisit triggers.
Use when: comparing two or more candidate architectures, designs, or technical approaches against weighted quality attributes: performance, consistency and correctness, operability, cost, evolvability, team fit — making what each option worsens explicit before the choice is made.
Use when: deciding at design time whether to build, buy, or adopt a library, framework, service, or platform dependency: maintenance signals, API stability, lock-in and exit cost, operational burden, license fit, and the conditions under which the choice should be reversed.
Use when: turning an architecture specification and repository evidence into a development-oriented container setup (Dockerfile, .dockerignore, and optional compose.yaml): base image and pinned tag selection, dependency-layer caching, dev affordances (bind mounts, watch, dev dependencies), backing services, non-root user, healthchecks, and secret-safe configuration.
Use when: designing failure behavior for an architecture or component design before implementation: per-dependency failure modes (slow, down, wrong, partial), degradation policy, retry, timeout, idempotency and backpressure decisions, blast-radius containment, and failure observability.
Use when: designing or auditing the contract of a boundary before implementation: API, service interface, module boundary, message schema, or webhook — operations, inputs and outputs, error semantics, idempotency, ordering, versioning posture, and invariant ownership.
Use when: designing, reviewing, refactoring, or test-planning type-safe architecture, compiler-enforced contracts, validation-as-types, explicit interfaces, generic misuse, reflection boundaries, polymorphic factories, closure-based extension, SOLID change complexity, or change-locality risks.