architecture

Guide architectural decisions across RxDB, Neon, Ably, and Bluetooth layers.

Updated Aug 27, 2026

Search Tags:#architecture #system design #data sync #Neon #WTFPOS #Ably #RxDB

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/pyroboy/midcodes/tree/main/apps/WTFPOS/.claude/skills/architecture
Command: npx skills add https://github.com/pyroboy/midcodes --skill architecture-pyroboy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive oversight for the WTFPOS architecture, guiding decisions across multiple technology layers and ensuring cohesive system design.

Core Features & Use Cases

Cross-Layer Decision Making: Assists in architectural choices spanning RxDB, Neon, Ably, Bluetooth, offline sync, and data replication.
Strategic Guidance: Answers questions about system integration, best approaches, and feature impact on data sync and real-time capabilities.
Use Case: When considering how to implement cross-branch data visibility, this skill helps determine the optimal approach by referencing the overall architecture map and phase roadmap.

Quick Start

Ask about the best approach for implementing cross-branch data visibility in WTFPOS.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I implement cross-branch data visibility in a POS system using RxDB and Neon?▼

Cross-branch data visibility in a POS system requires mapping data synchronization pathways across RxDB and Neon. You can determine the optimal approach by referencing the overall architecture map and phase roadmap to guide cross-layer integration decisions.

What is the best way to handle offline data sync and replication for a Point of Sale architecture?▼

Offline data sync for a Point of Sale architecture involves coordinating local database replication with remote servers. Strategic oversight ensures cohesive system design across technology layers including RxDB, Neon, and Ably for seamless offline capabilities.

How does real-time data synchronization work with Ably and RxDB in a cross-device architecture?▼

Real-time data synchronization with Ably and RxDB operates by managing real-time pipelines across cross-device environments. Architectural oversight ensures that feature implementations correctly impact data sync and real-time capabilities across the entire system stack.

Can I use Bluetooth integration alongside offline sync capabilities in a POS system design?▼

Bluetooth integration functions alongside offline sync capabilities within a POS system design by spanning multiple technology layers. Cross-layer decision making ensures cohesive architectural choices across Bluetooth, RxDB, and data replication mechanisms.

What are the architectural limitations when scaling data synchronization across multiple branches?▼

Architectural limitations when scaling data synchronization across branches depend on the phase roadmap and technology stack boundaries. Complex queries regarding cross-branch data management require understanding the stack diagram to anticipate feature impacts on real-time pipelines and offline sync.