stacks-config

Consolidate 44 Stacks config files into a unified environment with define* builders.

622|17|Updated Apr 26, 2022
One-click install
npx skills add https://github.com/stacksjs/stacks --skill stacks-config
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stacks-config
Source: https://github.com/stacksjs/stacks/tree/main/.claude/skills/stacks-config
Command: npx skills add https://github.com/stacksjs/stacks --skill stacks-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing configuration across the Stacks ecosystem can be verbose and error-prone. This skill provides a centralized approach to configure app, database, services, and environment overrides using the @stacksjs/config tooling and the 44 config files.

Core Features & Use Cases

  • Unifies access to 44 core config files and defaults
  • Provides builder-based configuration via defineApp, defineDatabase, defineCache, etc.
  • Supports environment-specific overrides for dev, staging, and prod

Quick Start

Install and configure your Stacks project by updating the config/ directory and using defineApp/defineDatabase builders to apply defaults.

Frequently Asked Questions about stacks-config

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

FAQPage Schema
How do I manage environment-specific configuration overrides for dev, staging, and prod?▼

To configure a Stacks app environment, update the config/ directory and use define* builders like defineApp and defineDatabase. This consolidates 44 config files and defaults into a unified environment setup for apps, databases, and services.

What is the best way to define app and database infrastructure in a Stacks project?▼

Use define* builders like defineApp and defineDatabase within your config/ directory to define infrastructure. This builder-based configuration approach applies defaults and unifies access to 44 core config files across your Stacks project.

Do I need the @stacksjs/config package to set up my project configuration?▼

Yes, the @stacksjs/config package is required. It provides the tooling needed to consolidate 44 config files and defaults, enabling builder-based configuration workflows via defineApp, defineDatabase, and defineCache across your project.

How does consolidating config files work within the Stacks ecosystem?▼

Consolidating config files unifies access to 44 core config files and defaults via the config/ directory structure. This exposes a unified Stacks environment, reducing verbose and error-prone manual configuration across apps, databases, and services.

Can I use builder-based configuration for caches and services across different environments?▼

Yes, builder-based configuration via defineCache and other define* builders supports caches and services. It applies environment-specific overrides for dev, staging, and prod, managing defaults across apps, databases, and deployment workflows.