architecture

Create ADR-driven architecture designs for Rust/WASM projects.

Updated Aug 23, 2026

Search Tags:#design #architecture #ADR #Rust #WASM #system-design

Ready to run

npx skills add https://github.com/terraphim/terraphim-skills --skill architecture-terraphim

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/terraphim/terraphim-skills/tree/main/skills/architecture
Command: npx skills add https://github.com/terraphim/terraphim-skills --skill architecture-terraphim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

System architecture decisions are often scattered and hard to trace. This skill produces ADR-driven designs for Rust/WASM projects, ensuring decisions are documented, traceable, and aligned with future needs.

Core Features & Use Cases

ADR creation: Create Architecture Decision Records in a standard format (Context, Decision, Consequences) and link related ADRs.
System Design: Define module boundaries, responsibilities, data flow, and concurrency patterns; design ergonomic public APIs in Rust.
Integration & Deployment Architecture: Plan plugin points, external service integrations, feature flags, and deployment topologies to enable scalable architectures.
Open Source Friendly: Emphasize backward compatibility and contributor-friendly documentation.

Quick Start

Draft ADR-001 for a new WASM data-processor module and outline its module boundaries and public API.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I create Architecture Decision Records for Rust and WASM projects?▼

To create Architecture Decision Records for Rust and WASM projects, use a standard format covering Context, Decision, and Consequences. This approach ensures architecture decisions are documented, traceable, and linked to related design choices.

What is the best way to design module boundaries and public APIs in Rust?▼

Designing module boundaries and public APIs in Rust requires defining clear responsibilities, data flow, and concurrency patterns. This ensures ergonomic interfaces and robust architectures while maintaining backward compatibility for open-source contributors.

How do I document deployment topology and integration points for distributed WASM components?▼

Documenting deployment topology and integration points for distributed WASM components involves planning plugin points, external service integrations, and feature flags. This enables scalable architectures aligned with your system design decisions.

Does this approach generate actual Rust and WASM implementation code?▼

No, this approach does not generate Rust and WASM implementation code. It strictly focuses on producing ADR-driven designs, module boundaries, and API design documentation while avoiding implementation work.

When do I need Architecture Decision Records for system design?▼

You need Architecture Decision Records for system design when your architecture decisions are scattered and hard to trace. Using ADRs ensures decisions are documented, traceable, and aligned with future project needs.