torre-tech-arch

Maintains a database of bike models, brands, and categoriesbba.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/lfggarcia/dnd-app --skill torre-tech-arch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: torre-tech-arch
Source: https://github.com/lfggarcia/dnd-app/tree/main/.github/skills/torre-tech-arch
Command: npx skills add https://github.com/lfggarcia/dnd-app --skill torre-tech-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill documents the TORRE architectural and data-model decisions to support deterministic seeds, offline-first persistence, and scalable state management in a React Native stack.

Core Features & Use Cases

  • Seed-driven determinism: Each seed creates an isolated ecosystem with reproducible results.
  • SQLite-backed persistence: Local database schema with Seeds, Parties, Characters, Items, Events, Alliances, Bounties.
  • Zustand-based state management: Centralized client-side state with deterministic updates.
  • Offline-first design: No server required; all logic runs locally.

Quick Start

Review the GameState model and SQLite schema to verify deterministic behavior when extending the seed-based architecture.

Frequently Asked Questions about torre-tech-arch

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

FAQPage Schema
How do I structure offline-first React Native game state with SQLite and Zustand?

To structure offline-first React Native game state, you use a centralized Zustand store for deterministic updates and a local SQLite database schema to persist game elements like Seeds, Parties, and Characters without requiring a server.

What is seed-driven determinism in offline-first game architecture?

Seed-driven determinism is an architectural pattern where each seed creates an isolated ecosystem with reproducible results, ensuring that game logic and state updates run locally and predictably across devices without server dependencies.

How do I design a SQLite schema for React Native game persistence?

You design a SQLite schema by defining local database tables for core game entities such as Seeds, Parties, Characters, Items, Events, Alliances, and Bounties to support offline-first data persistence.

Does Zustand work well for deterministic game state updates in React Native?

Zustand works for deterministic game state updates by providing a centralized client-side state container that applies reproducible logic, which pairs directly with a SQLite-backed persistence layer for offline-first gaming.

When should I use an offline-first architecture for mobile games?

You should use an offline-first architecture when your mobile game requires all logic to run locally without server availability, relying on local SQLite persistence and deterministic seed-based models to maintain state continuity.

Why does my seed-based game state lose determinism across React Native sessions?

Your seed-based game state loses determinism if state updates deviate from the centralized Zustand store guidelines or if the SQLite schema fails to properly isolate ecosystem data for Seeds, Characters, and Events.