skills.rest
MakePrisms
MakePrismsOFFICIAL
Explore all skills by this author →
GitHub

agicash-wallet-architecture

Document Agicash wallet architecture across server, client, Open Secret, and Postgres DB.

55|5|Updated Feb 1, 2024
Search Tags:#architecture#encryption#wallet#postgres#server-client#data-flow#open-secret
One-click install
npx skills add https://github.com/MakePrisms/agicash --skill agicash-wallet-architecture-makeprisms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agicash-wallet-architecture
Source: https://github.com/MakePrisms/agicash/tree/main/.claude/skills/agicash-wallet-architecture
Command: npx skills add https://github.com/MakePrisms/agicash --skill agicash-wallet-architecture-makeprisms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agicash wallet architecture clarification and cross-component boundaries, defining responsibilities and interactions across server, client, Open Secret, and the Postgres DB to guide coherent development and maintenance.

Core Features & Use Cases

  • Clear delineation of component roles (Server, Client, Open Secret, Postgres DB) to prevent scope creep and ensure proper security boundaries.
  • Guidance on data flow, API boundaries, and deployment considerations when evolving the wallet stack.
  • Use Case: When modifying Lightning Address routes, SSR behavior, or encryption/decryption flows, refer to this architecture to decide where changes should live.

Quick Start

Describe the appropriate component ownership and data flow for a proposed change to the wallet architecture.

Frequently Asked Questions about agicash-wallet-architecture

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

FAQPage Schema
How do I define component ownership for a wallet architecture across server, client, and database?▼

To define wallet architecture component ownership, you must delineate responsibilities across the server, client, Open Secret, and Postgres DB to establish clear security boundaries and prevent scope creep during development.

What is the correct data flow for encryption and decryption in a server-client wallet stack?▼

Wallet encryption data flow requires routing through specified server, client, and Open Secret interactions to maintain safe data access patterns and aligned security boundaries across the Postgres DB.

When should I use this architecture documentation for modifying Lightning Address routes or SSR behavior?▼

Use this architecture documentation when modifying Lightning Address routes, SSR behavior, or encryption flows to determine exactly where changes should live across server routes and client logic.

How does Open Secret integration interact with Postgres DB and Realtime subscriptions in a wallet?▼

Open Secret integration interacts with the Postgres DB and Realtime subscriptions by defining clear component boundaries and data access patterns that align with the overall wallet architecture document.

What are the limitations of cross-component boundaries when evolving a wallet stack?▼

Limitations of cross-component boundaries involve strict adherence to established API contracts and deployment considerations to prevent scope creep and maintain safe data flows across server and client components.

Related Skills

Explore More Software Engineering Skills→
HechaoYannetHechaoYannet

create-architecture

Generate a master architecture document from GDDs, ADRs, and governance constraints.

Community
Advanced
gudnufgudnuf
1

agicash-wallet-architecture

Define architectural boundaries across server, client, Open Secret, and database.

Community
Intermediate
ColdBoxColdBox

cbvalidation

Validates inbound webhook payloads for configured triggers and required fields.

Official
Intermediate
onichandameonichandame

client-side-encryption

Encrypt user data client-side with AES-256-GCM and PBKDF2 in SvelteKit.

Community
Advanced