skills.rest
wfukatsu
wfukatsuCOMMUNITY
Explore all skills by this author →
GitHub

design-scalardb-app-patterns

Identify domain types and apply ScalarDB design patterns for schema design.

5|Updated Feb 10, 2026
Search Tags:#domain-driven-design#data-modeling#design-patterns#distributed-transactions#schema-design#scalardb#architecture-guide
One-click install
npx skills add https://github.com/wfukatsu/architecture-redesign-agent --skill design-scalardb-app-patterns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-scalardb-app-patterns
Source: https://github.com/wfukatsu/architecture-redesign-agent/tree/main/.claude/skills/design-scalardb-app-patterns
Command: npx skills add https://github.com/wfukatsu/architecture-redesign-agent --skill design-scalardb-app-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This agent identifies domain types and prescribes ScalarDB design patterns, data modeling approaches, and schema design guidance to streamline distributed data architectures.

Core Features & Use Cases

  • Domain type identification (Pipeline, Blackboard, Dialogue) and microservice boundaries
  • Domain-type driven design pattern selection (Event Sourcing, Saga, 2PC)
  • Storage/back-end recommendations aligned with ScalarDB and edition constraints
  • ScalarDB schema design (namespace, tables, keys) and access patterns
  • App-architecture pattern guidance by edition (OSS vs Enterprise)

Quick Start

Call the skill with the target project path under work/{project}/scalardb-edition-config.md to begin domain-driven design and pattern recommendations.

Frequently Asked Questions about design-scalardb-app-patterns

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

FAQPage Schema
How do I choose the right design pattern for ScalarDB distributed transactions?▼

ScalarDB schema design involves defining namespaces, tables, and partition keys, guided by the identified domain type and selected distributed transaction pattern to enforce efficient data modeling and access patterns.

Can I use ScalarDB for domain-driven data modeling and microservice boundaries?▼

ScalarDB enforces edition-aware storage recommendations, aligning back-end choices with either OSS or Enterprise edition constraints to ensure storage compatibility and guide app-architecture pattern selection.

What is the best way to design a ScalarDB schema for a domain-driven application?▼

To begin domain-driven design with ScalarDB, place your target project configuration file specifying the ScalarDB edition at the project work path, enabling the skill to generate pattern recommendations and schema specifications.

Does ScalarDB schema design require specific storage configuration for different editions?▼

ScalarDB schema design requires defining namespaces, tables, and partition keys, guided by the identified domain type and selected distributed transaction pattern to enforce efficient data modeling and access patterns.

How do I start domain-driven design patterns for a ScalarDB project?▼

ScalarDB supports domain-driven data modeling by identifying domain types to map microservice boundaries, selecting appropriate design patterns, and enforcing domain-aware schema specifications for distributed data architectures.

Related Skills

Explore More Software Engineering Skills→
wfukatsuwfukatsu
5

select-scalardb-edition

Analyze project requirements to select a ScalarDB edition and generate a configuration file.

Community
Advanced
wfukatsuwfukatsu
8

design-scalardb

Design ScalarDB Cluster topology, storage mapping, and migration plans for microservices.

Community
Advanced
curiositechcuriositech
181

microservices-patterns

Explain microservice architecture patterns including decomposition, communication, and Saga transactions.

Official
Advanced
wfukatsuwfukatsu
6

database-design

Design ScalarDB database schemas and transaction models for multi-storage deployments.

Community
Advanced