system-architecture

Document system components, responsibilities, and data flows for mobile, backend, and database.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/MoisesAldas/OficiosYA --skill system-architecture-moisesaldas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-architecture
Source: https://github.com/MoisesAldas/OficiosYA/tree/main/.agents/system-architecture
Command: npx skills add https://github.com/MoisesAldas/OficiosYA --skill system-architecture-moisesaldas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The architecture overview provides a concise, high-level description of the system's structure, guiding developers and stakeholders to understand how the frontend, backend, and database interact while keeping the project simple, scalable, and maintainable.

Core Features & Use Cases

  • Lightweight client-server pattern separating concerns between the mobile client, backend services, and data store.
  • Three core parts: a mobile application frontend (Expo/React Native), a managed backend, and a PostgreSQL database.
  • Design principles emphasize simplicity, scalability, modularity, and fast end-user interactions.
  • Use case: quickly onboard new team members by referencing the architecture to understand responsibilities and data flow.

Quick Start

Review the architectural overview to understand how the mobile app, backend API, and database interact to serve users.

Frequently Asked Questions about system-architecture

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

FAQPage Schema
How do I document system architecture for a React Native and PostgreSQL project?

Document system architecture by outlining core components like the Expo/React Native frontend, backend services, and PostgreSQL database, along with their responsibilities and data flows. This clarifies interactions for onboarding and maintenance.

What is the best way to structure a scalable client-server architecture overview?

A scalable client-server architecture overview separates concerns between the mobile client, backend services, and data store. It emphasizes design principles like simplicity, modularity, and fast end-user interactions to guide development.

How does documenting data flow help with onboarding new developers?

Documenting data flow helps onboarding by giving new developers a concise, high-level description of how the frontend, backend, and database interact. This allows them to quickly understand system responsibilities and project structure.

Can I use this architecture documentation for planning future scalability?

Yes, this architecture documentation supports scalability planning by outlining core components and design principles. It highlights modularity and simplicity to ensure the system remains maintainable as future scalability plans are implemented.

What should be included in a system architecture overview for a mobile application?

A system architecture overview for a mobile application should include the client-server pattern, specifically detailing the mobile frontend, backend API, and database interactions. It must also document design principles and future scalability plans.

Why does my system architecture need to separate frontend and backend concerns?

Separating frontend and backend concerns in your system architecture keeps the project simple, scalable, and maintainable. This lightweight pattern ensures distinct responsibilities between the mobile client, backend services, and data store.