skills.rest
firefly-oss
firefly-ossOFFICIAL
Explore all skills by this author →
WebsiteGitHub

banking-domain-conventions

Enforces predefinedOrion-style naming and packaging across banking domain modules.

Updated Aug 27, 2026
Search Tags:#software-engineering#module-structure#sdk-generation#banking-platform#domain-architecture#openapi-generation#pom-inheritance
One-click install
npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill banking-domain-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: banking-domain-conventions
Source: https://github.com/firefly-oss/firefly-oss-claude-skills/tree/main/skills/banking-domain-conventions
Command: npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill banking-domain-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns and enforces standardized domain architecture and packaging conventions across Firefly service repositories.

Core Features & Use Cases

  • Standard domain taxonomy with six prefixes (core-banking-, core-lending-, core-common-, domain-, exp-, app-)
  • Consistent package naming and multi-module structure (-interfaces, -models, -core, -web, -sdk) and BOM usage
  • SDK client wiring via domain -infra factories and environment-driven API base paths

Quick Start

Review your repository structure and ensure modules align with banking-domain-conventions, updating POMs and OpenAPI generation as described.

Frequently Asked Questions about banking-domain-conventions

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

FAQPage Schema
How do I standardize module structure and naming conventions across banking platform repositories?▼

Standardize banking platform repositories by enforcing six domain prefixes (core-banking-*, core-lending-*, core-common-*, domain-*, exp-*, app-*) and consistent multi-module structures. This ensures aligned domain architecture and packaging conventions across all services.

What is the standard module structure for Firefly domain orchestration services?▼

The standard module structure for domain services includes -interfaces, -models, -core, -web, -sdk, and -infra modules. This structure enforces consistent packaging, API separation, and SDK client wiring across domain orchestration services.

How do I wire SDK clients using environment-driven API base paths in a banking platform?▼

Wire SDK clients in a banking platform by utilizing domain -infra factories that configure environment-driven API base paths. This approach standardizes client generation and ensures consistent API connectivity across services.

Does banking-domain-conventions support BOM-based versioning for multi-module repositories?▼

Yes, banking-domain-conventions supports BOM-based versioning for multi-module repositories. It enforces BOM usage to standardize dependency versions across core banking, lending, and domain orchestration services.

When should I apply domain architecture conventions to my OpenAPI client generation process?▼

Apply domain architecture conventions to OpenAPI client generation when standardizing service repositories for core banking or lending platforms. This ensures consistent SDK generation patterns and aligned packaging across all domain services.

Related Skills

Explore More Software Engineering Skills→
jagodabiejagodabie

add-domain-module

Generate Express and TypeScript backend domain modules with layered architecture.

Community
Advanced
farmountainfarmountain
1

Integration Builder Agent

Generate type-safe API clients from OpenAPI, GraphQL, and gRPC specifications.

Community
Advanced
pluginagentmarketplacepluginagentmarketplace
40

java-maven

Configure Maven POM files, manage dependencies, and orchestrate multi-module projects.

Community
Intermediate
diegoliriodiegolirio

kotlin-spring

Scaffold a Kotlin and Spring multi-module project with a buildingBlocks/core presenter architecture.

Community
Intermediate