Architect

Translate strategic vision into technical designs and manage cross-system data flows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Ghabs95/agents --skill architect-ghabs95
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architect
Source: https://github.com/Ghabs95/agents/tree/main/wlbl-agents/.agent/skills/architect
Command: npx skills add https://github.com/Ghabs95/agents --skill architect-ghabs95

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that technical designs align with strategic vision, enforce architectural best practices, and manage the flow of data across different projects and systems.

Core Features & Use Cases

  • Enforces Design Patterns: Maintains consistency in architecture across mobile, backend, and infrastructure.
  • Manages Data Flow: Oversees secure and efficient data movement between applications.
  • Decision Records: Documents significant technical choices.
  • Use Case: When a new feature requires changes in both the mobile app and the backend API, the Architect Skill ensures the design is sound, data contracts are clear, and the changes adhere to established patterns.

Quick Start

Use the Architect skill to review the proposed data flow for the new user authentication system.

Frequently Asked Questions about Architect

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

FAQPage Schema
How do I design data flows between mobile apps and backend APIs?

To design data flows between mobile and backend, translate strategic vision into concrete technical designs that enforce architectural patterns and ensure secure, efficient data movement. This approach manages cross-system data contracts and maintains consistency across infrastructure.

What is the best way to enforce design patterns across backend and mobile systems?

Enforcing design patterns across backend and mobile systems requires translating strategic vision into concrete technical designs. This ensures architecture consistency, maintains decoupling, and manages data movement to guarantee scalability and adequate testing coverage.

How do you document technical design decisions for system architecture?

Documenting technical design decisions for system architecture involves creating decision records that capture significant technical choices. This ensures designs align with strategic vision while enforcing architectural best practices and managing data flow across projects.

When do I need to review technical designs for cross-system data movement?

You need to review technical designs for cross-system data movement when a new feature requires changes in both mobile apps and backend APIs. This ensures the design is sound, data contracts are clear, and changes adhere to established patterns.

Does this architectural approach support scalability and decoupling for infrastructure?

Yes, this architectural approach supports scalability and decoupling for infrastructure by enforcing design patterns and managing data flow. It translates strategic vision into technical designs that ensure adequate testing coverage and secure data movement.

Why does system architecture fail to align with strategic vision during technical design?

System architecture fails to align with strategic vision when technical designs do not enforce architectural patterns or manage data flows properly. Translating strategic vision into concrete designs with decision records ensures alignment and maintains cross-system consistency.