Ghostmind System Orchestration FAQs

Question 1

When should I use this skill?

Accepted Answer

Use this skill whenever you are working within the Ghostmind ecosystem to create or modify configurations, set up new applications, manage secrets via Vault, or troubleshoot interconnectivity between Docker, Compose, and cloud infrastructure.

Question 2

How does this skill improve my AI-assisted coding workflow?

Accepted Answer

It transforms Claude into a specialized DevOps orchestrator. Instead of managing tools in isolation, Claude can use this skill to ensure your local environment (Tmux/Compose) perfectly aligns with your deployment infrastructure (Terraform) using a single source of truth.

Question 3

What does the Ghostmind System Orchestration skill do?

Accepted Answer

This skill enables Claude Code to manage complex full-stack development environments. It uses a centralized 'meta.json' file to orchestrate Docker containers, Terraform infrastructure, Tmux sessions, and custom Deno/TypeScript scripts through a unified CLI tool.

Question 4

Why is fetching the schema emphasized as a critical step?

Accepted Answer

The Ghostmind system is schema-driven. Fetching the latest JSON schema ensures Claude understands the authoritative structure, validation rules, and available properties for 'meta.json', preventing configuration errors and ensuring compatibility with the latest system updates.

Question 5

What core capabilities does this skill provide to Claude?

Accepted Answer

It provides deep integration with the 'run' CLI for unified operations, automated secret management via Google Cloud Secret Manager (Vault), variable substitution for dynamic environments, and standardized VS Code devcontainer setup for reproducible development.

Ghostmind System Orchestration

Ghostmind System Orchestration

Key Features

Use Cases

Key Features

Use Cases