agicash-wallet-documentation

Document Agicash wallet transaction flows, entities, and state machines.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/gudnuf/agicash-rs --skill agicash-wallet-documentation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agicash-wallet-documentation
Source: https://github.com/gudnuf/agicash-rs/tree/main/.claude/skills/agicash-wallet-documentation
Command: npx skills add https://github.com/gudnuf/agicash-rs --skill agicash-wallet-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Documentation for Agicash wallet transaction flows and entities to help developers understand and implement send/receive, Lightning Address, and Spark interactions.

Core Features & Use Cases

  • Comprehensive overview of Quote/Swap lifecycle, entities, and state machines
  • Reference mappings to source files under app/features and references/
  • Guidance for cross-account flows and Lightning/Spark paths

Quick Start

Read this guide to understand Agicash wallet flows and consult the references for deeper details.

Frequently Asked Questions about agicash-wallet-documentation

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

FAQPage Schema
How do Agicash wallet transaction flows work for send and receive operations?

Agicash wallet transaction flows map state machines and entities across app/features/send and receive operations, detailing data structures and lifecycle transitions for developers and product teams.

How does the Cashu and Spark quote and swap lifecycle function?

The Cashu and Spark quote and swap lifecycle defines token flows and state machine transitions, mapping references to source files under app/features and references/ directories.

What is the best way to document Lightning Address pathways for wallet integrations?

Documenting Lightning Address pathways involves mapping data structures, roles, and lifecycle transitions used by Cashu and Spark integrations to ensure consistent terminology across reference files.

Can I use this documentation for cross-account flows and Spark interactions?

Yes, the documentation provides guidance for cross-account flows and Lightning/Spark paths, mapping references to source files to describe entities and state machines used by integrations.

Why does consistent terminology matter when documenting wallet state machines?

Consistent terminology ensures developers and product teams accurately understand lifecycle transitions and data structures, mapping references directly to source files under app/features and references/.