config

Generate ScalarDB configuration files for deployment mode, API style, transaction mode, and database backend.

12|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/wfukatsu/nexus-architect --skill config-wfukatsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config
Source: https://github.com/wfukatsu/nexus-architect/tree/main/skills/config
Command: npx skills add https://github.com/wfukatsu/nexus-architect --skill config-wfukatsu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the setup of ScalarDB configurations, saving time and reducing the potential for manual errors when starting a new project or switching between ScalarDB backends and editions.

Core Features & Use Cases

  • Automated Configuration Generation: Generates database.properties and build.gradle files based on user choices.
  • Deployment Mode Selection: Supports Core and Cluster modes.
  • API Style Configuration: Handles CRUD API and JDBC/SQL API styles.
  • Transaction Mode Support: Includes One-phase commit (1PC) and Two-phase commit (2PC) modes.
  • Database Backend Choice: Offers MySQL, PostgreSQL, Cassandra, DynamoDB, Cosmos DB, Oracle, SQL Server, and Multi-storage backend options.
  • Use Case: When you start a new ScalarDB project or need to switch to a different backend/edition or interface, this Skill simplifies the configuration process.

Quick Start

Use the /scalardb:config command to generate your ScalarDB configuration files.

Frequently Asked Questions about config

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

FAQPage Schema
How do I generate ScalarDB configuration files for a new project?

To generate ScalarDB configuration files, you can use an automated setup tool to create your database.properties and build.gradle files based on your chosen deployment mode, API style, transaction mode, and database backend, reducing manual errors.

Can I use ScalarDB with PostgreSQL and Cassandra in a multi-storage setup?

Yes, ScalarDB supports multi-storage backend configurations. You can select PostgreSQL, Cassandra, MySQL, DynamoDB, Cosmos DB, Oracle, or SQL Server as your database backend during the configuration generation process.

What is the difference between ScalarDB Core and Cluster deployment modes?

ScalarDB deployment modes determine your architecture topology. The configuration setup supports both Core and Cluster modes, allowing you to generate the appropriate database.properties and build.gradle files for your specific deployment strategy.

How do I switch my ScalarDB backend from CRUD API to JDBC/SQL API?

To switch your ScalarDB API style from CRUD to JDBC/SQL, you can regenerate your configuration files by specifying the new API style, which updates your database.properties and build.gradle files for the new interface.

Does ScalarDB configuration support Two-phase commit transaction mode?

Yes, ScalarDB configuration supports both One-phase commit (1PC) and Two-phase commit (2PC) transaction modes. The setup process generates the necessary database.properties file based on your selected transaction mode.

What's the best way to debug ScalarDB configuration errors?

For debugging ScalarDB configuration errors, you can regenerate your configuration files by re-running the automated setup to ensure your database.properties and build.gradle files correctly match your intended backend, edition, and API choices.