skills.rest
stanz-stanz
stanz-stanzCOMMUNITY
Explore all skills by this author →
GitHub

architect

Define and enforce system architecture and component boundaries for the Heimdall pipeline.

Updated Aug 27, 2026
Search Tags:#architecture#scalability#adr#code-review#system-design#data-flow#agent-orchestration
One-click install
npx skills add https://github.com/stanz-stanz/heimdall --skill architect-stanz-stanz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/stanz-stanz/heimdall/tree/main/.claude/agents/architect
Command: npx skills add https://github.com/stanz-stanz/heimdall --skill architect-stanz-stanz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Application Architect agent eliminates ambiguity around system structure, component responsibilities, and data flow by providing clear architecture guidance, API contracts, and decision records so teams can scale and maintain Heimdall reliably.

Core Features & Use Cases

  • System design ownership: Owns and maintains docs/architecture/, ADRs, and high-level system-design artifacts.
  • Code & component reviews: Reviews proposed changes for structural soundness, separation of concerns, and adherence to architecture principles.
  • Integration planning: Designs agent orchestration, JSON handoffs, API contracts, and scaling strategies for transitioning from Pi to cloud.
  • Use case: When adding a new delivery channel or refactoring the memory model, the Architect defines where logic lives, specifies schemas, and records trade-offs.

Quick Start

Ask the architect to review a proposed change by describing the component, its inputs and outputs, and the desired deployment targets in one message.

Frequently Asked Questions about architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define system architecture and component boundaries for a scanning and delivery pipeline?▼

Define system architecture by owning module design, data-flow diagrams, and API contract specifications to eliminate ambiguity around component responsibilities and scale reliably.

What is the best way to create Architecture Decision Records for agent orchestration and deployment?▼

Create Architecture Decision Records by documenting structural trade-offs, component logic locations, and scaling strategies for transitioning agent orchestration from Pi to cloud environments.

How do I structure API contracts and JSON handoffs for a single-writer memory model?▼

Structure API contracts by specifying schemas and defining where logic lives, ensuring JSON-based handoffs satisfy single-writer client memory requirements and clear component separation.

Does this approach support code review for separation of concerns and structural soundness?▼

Code review for separation of concerns evaluates proposed changes against architecture principles, ensuring structural soundness and adherence to defined system boundaries and data flow.

When do I need to update high-level system design artifacts during a memory model refactoring?▼

Update system design artifacts during memory model refactoring when component responsibilities shift, requiring new API contract specifications and recorded trade-offs in architecture decision records.

Related Skills

Explore More Software Engineering Skills→
rickyanandarickyananda
1

architecture-diagram

Generate standalone dark-themed HTML architecture diagrams from system descriptions.

Community
Intermediate
nesihaver-ILnesihaver-IL

aws-strands

Build model-agnostic AI agents with ReAct reasoning and multi-agent orchestration.

Community
Intermediate
vladm3105vladm3105
16

doc-adr-validator

Validate ADR documents against Layer 5 schema for structural and metadata compliance.

Community
Advanced
virajpvirajp
1

architecture

Create and maintain system architecture blueprints with project registries and dependencies.

Community
Advanced