skills.rest
gudnuf
gudnufCOMMUNITY
Explore all skills by this author →
GitHub

agicash-wallet-architecture

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

1|Updated May 16, 2026
Search Tags:#design#architecture#security#server#wallet#client#open-secret
One-click install
npx skills add https://github.com/gudnuf/agicash-rs --skill agicash-wallet-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agicash-wallet-architecture
Source: https://github.com/gudnuf/agicash-rs/tree/main/.claude/skills/agicash-wallet-architecture
Command: npx skills add https://github.com/gudnuf/agicash-rs --skill agicash-wallet-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agicash wallet architecture clarification helps engineering teams understand the boundaries and interactions between Server, Client, Open Secret, and Postgres DB, enabling safer cross-component changes and better alignment with security and data access rules.

Core Features & Use Cases

  • Clear delineation of component responsibilities (Server, Client, Open Secret, Postgres DB) to guide changes.
  • Guidance on where new functionality should live (server vs client) and how data flows across boundaries.
  • Real-world example: when modifying encryption flows, Lightning Address routes, or SSR behavior to ensure alignment with architecture constraints.

Quick Start

Map the current feature involving Lightning Address routing to identify which layer owns it and update responsibilities accordingly.

Frequently Asked Questions about agicash-wallet-architecture

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

FAQPage Schema
How do I determine where new wallet features should live between server and client?▼

To determine where new wallet features should live, map the architectural boundaries between server, client, Open Secret, and database to identify component ownership and enforce data handling rules.

What is the correct architecture for routing Lightning Address updates in a wallet client?▼

The correct architecture for routing Lightning Address updates involves identifying which layer owns the route and updating responsibilities across server, client, and database boundaries accordingly.

How do I safely modify encryption flows across server and client boundaries?▼

To safely modify encryption flows, enforce security constraints and data access rules by defining scope and scenarios where architecture decisions apply across server and client boundaries.

Does the wallet architecture component ownership apply to realtime subscriptions and SSR behavior?▼

Yes, wallet architecture component ownership applies to realtime subscriptions and SSR behavior, defining the scope and scenarios where architecture decisions enforce data handling and security constraints.

What are the limitations when introducing new functionality across wallet server and database boundaries?▼

Limitations when introducing new functionality include strict security constraints and data access rules, requiring you to define scope and scenarios to ensure appropriate component ownership across boundaries.

Related Skills

Explore More Software Engineering Skills→
MakePrismsMakePrisms
55

agicash-wallet-architecture

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

Official
Advanced
TbK0ngTbK0ng

improve-ut

Analyze changed files and unit-test specs to update and validate tests.

Community
Intermediate
bovinphangbovinphang
21

fec-nextjs-project-standard

Enforce Next.js 14+ App Router project conventions and best practices.

Community
Advanced
aryanshrai03aryanshrai03

security

Generate PlantUML security architecture diagrams with AWS stencil icons.

Community
Intermediate