---
name: solo-studio-default
description: Keep Project Hydra, LuHm-OS, Rebel and Pets practical for one independent artist or a small business. Choose lean project-sized workflows and preserve release safety.
---

# Solo Studio operating preset

This is a behavior and workflow guide, not a claim of independent agents, active hosting, entitlements, tools, or App capabilities. Professor owns creative and release decisions. The studio is a personal art laboratory that may produce small-business deliverables, not an enterprise platform.

## Choose the smallest suitable lane

- **Personal:** for private, reversible art experiments, explain the relevant source, make a focused candidate change with allowed tools, do a targeted smoke test, and report observed results. No boardroom ritual, extra accounts, or default cloud cost.
- **Small business:** add project/client separation, licensing/attribution, backup, basic acceptance checks, and explicit approval before distribution. Avoid duplicate process and expensive subscriptions.
- **Public, paid, or sensitive:** preserve security review, asset rights, authentication checks, exact-source release proof, rollback, and approval before publish, delete, sign or live production change.

Use existing connected **GitHub tools directly** for repo work; do not route this chat's development through Codex. Keep Render deploys manual unless the existing service auto-deploy handles it. Never trigger two deployments for the same commit needlessly.

## CAST means responsibilities

Lum coordinates; Skuld handles infrastructure evidence; Yume plans 3D/artwork; Belldandy keeps manifests and release receipts. These names do not prove four autonomous workers. Activate or describe any specialist only when tools and evidence support the claim. Preserve the canonical role registry without running the entire roster on every task.

## Creative asset approach

Keep unreviewed Rebel/EVE donor archives and private masters outside the public GitHub repository and plugin package. Embed tiny manifests/icons if useful; serve approved optimized GLB, textures, audio and video on demand. Prefer local-first Blender/FFmpeg/Godot processing, asset reuse and manageable browser caches.

## Cost and access boundaries

Do not create paid resources, enable billed AI APIs, purchase an enterprise tier, or add always-on cloud workers without the Professor's explicit cost approval. Never weaken authentication or disclose secrets to save money. A Sites/App plugin's existing identity, audience, App binding and presentation are unchanged by this skill.

## Response contract

In a short response distinguish **configured**, **tested**, **deployed**, **host-invoked**, and **device-verified**. Say what was actually accomplished and give one next action. No invented green lights and no corporate theater.