banking-architect

Design architecture and saga orchestration for Firefly Banking Platform features.

Updated Aug 23, 2026

Search Tags:#architecture #integration #orchestration #engineering #saga #domain-driven #firefly

Ready to run

npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill banking-architect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: banking-architect
Source: https://github.com/firefly-oss/firefly-oss-claude-skills/tree/main/agents/banking-architect
Command: npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill banking-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Banking teams often struggle to decide where a feature should live (core, domain, experience, or app) and how to design sagas and integration with the Firefly Banking Platform; this Skill provides architectural guidance and decision frameworks.

Core Features & Use Cases

Provides strategic placement guidance (Core vs Domain vs Experience vs App)
Guides saga design, orchestration patterns, and integration touchpoints across many repos in the Firefly ecosystem
Helps ensure multi-tenancy, compliance, and data ledger considerations in architecture decisions

Quick Start

Describe an architecture plan for designing a new banking feature, including saga flows and integration points with existing core, domain, experience, and app services.

Frequently Asked Questions about banking-architect

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

FAQPage Schema

How do I design saga orchestration for a new banking platform feature?▼

Saga orchestration for banking features is designed by crafting saga steps and defining integration touchpoints across core, domain, experience, and app layers. This ensures multi-tenancy, compliance, and data ledger considerations are enforced across the ecosystem.

How do I decide if a banking service belongs in the core or domain layer?▼

Deciding service placement across core, domain, experience, and app layers requires evaluating strategic architectural guidance and alignment with framework conventions. This determines the correct layer for features involving core banking, domain lending, and experience journeys.

What is saga orchestration in banking architecture and when is it needed?▼

Saga orchestration in banking architecture coordinates distributed transactions across service layers and multiple repositories. It is needed when designing features that require consistent data ledger updates, compliance auditing, and multi-tenancy enforcement across integration points.

What's the best way to structure integration points across multiple banking repositories?▼

Structuring integration points across banking repositories involves defining connections among approximately 55 repositories within the Firefly ecosystem. It requires documenting guardrails for cross-layer reflexive method generation to maintain architectural alignment.

Does domain-driven design work with multi-tenancy and compliance requirements in banking?▼

Domain-driven design works with multi-tenancy and compliance by enforcing these considerations directly within architecture decisions. It aligns service placement and saga steps with framework conventions to ensure data ledger integrity across all layers.