Major update to chorus.services platform

- Extensive updates to system configuration and deployment
- Enhanced documentation and architecture improvements
- Updated dependencies and build configurations
- Improved service integrations and workflows

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

brand-assets/packs/collaborator/kit.md

@@ -0,0 +1,100 @@
+A collaborator or code-contributor pack is aimed at **developers, artists, or other contributors** who might join your project. The goal is to give them **everything they need to understand, evaluate, and start contributing**, without being overwhelming. For a solo indie project, clarity and structure are key.
+
+Here’s what to include:
+
+---
+
+### **1. Cover / Intro**
+
+* Project name and logo.
+* Tagline or short mission statement.
+* High-level project overview in 1–2 sentences.
+
+---
+
+### **2. Project Overview**
+
+* Genre, style, and scope of the project.
+* Core mechanics or features.
+* Current development stage (prototype, alpha, early access).
+* Vision and goals: what you hope to achieve creatively and technically.
+
+---
+
+### **3. How to Contribute**
+
+* Areas of contribution needed (coding, art, sound, testing, level design).
+* How contributions will be managed (GitHub, GitLab, other VCS).
+* Coding standards or style guides (languages, frameworks, naming conventions).
+* Branching and pull request workflow.
+* Testing and QA procedures.
+
+---
+
+### **4. Technical Overview**
+
+* Tech stack: languages, engines, libraries, frameworks.
+* Hardware/software requirements for running the project locally.
+* Build instructions (how to compile/run the project).
+* Dependencies and installation guides.
+* Architecture overview (how code is organized, major modules).
+
+---
+
+### **5. Assets & Tools**
+
+* Links to art, audio, or other assets contributors can use.
+* Versioning info (if assets are managed separately).
+* Any proprietary tools, scripts, or plugins used in development.
+
+---
+
+### **6. Documentation**
+
+* Links to detailed code documentation or API references.
+* In-line comments and style notes.
+* Roadmap for features or sprints (so contributors know priorities).
+
+---
+
+### **7. Community & Communication**
+
+* Slack, Discord, or other chat channels.
+* Forum or issue tracker guidelines.
+* Code review process (who reviews, turnaround time).
+* Expected commitment or contribution etiquette.
+
+---
+
+### **8. Licensing & Legal**
+
+* Open-source or proprietary license (MIT, GPL, proprietary, etc.).
+* Contributor license agreements if required.
+* IP ownership clarifications (who retains rights to contributions).
+
+---
+
+### **9. Quick Start / First Task**
+
+* A simple, low-friction task to get new contributors involved.
+* Example: fix a small bug, add a small feature, polish an asset.
+* Step-by-step instructions to get up and running.
+
+---
+
+### **10. Contact / Support**
+
+* Primary point of contact (email, messaging).
+* How contributors should ask questions or report issues.
+* Optional: links to FAQs or developer guides.
+
+---
+
+**Tips:**
+
+* Make it **modular**: some contributors only need the technical overview, some only need art assets—don’t force them to wade through everything.
+* Include **visuals and diagrams** for architecture, workflows, or asset pipelines.
+* Keep setup instructions simple—new contributors often drop out if onboarding is too complex.
+* Highlight **low-friction ways to contribute first**, then deeper tasks once they’re familiar.
+
+---

brand-assets/packs/investor/kit.md

@@ -0,0 +1,115 @@
+An investor pack (or investor pitch kit) is more business-focused than a media pack. Its goal is to **convince investors that your project is viable, scalable, and worth funding**. Since you’re a solo indie developer, it should also realistically communicate risk and show how you plan to manage it. Here’s what you should include:
+
+---
+
+### **1. Cover / Intro**
+
+* Project name and logo.
+* Tagline or short mission statement.
+* Eye-catching visuals (game screenshot, concept art, or prototype GIF).
+
+---
+
+### **2. Executive Summary**
+
+* 1–2 paragraphs summarizing the project.
+* Why the project exists (problem/opportunity).
+* What makes it unique or innovative.
+* Current status (alpha, prototype, pre-launch).
+* Funding needs and what the investment will achieve.
+
+---
+
+### **3. The Problem / Opportunity**
+
+* Define the gap your project fills.
+* Why this matters now (market trends, audience demand).
+* Evidence of market interest (community size, early sign-ups, beta testers, Steam wishlists, social media engagement).
+
+---
+
+### **4. The Solution / Product**
+
+* Game description: genre, mechanics, art style.
+* Unique selling points: what makes it stand out.
+* Screenshots, concept art, or short gameplay clips.
+* Current development stage and roadmap.
+
+---
+
+### **5. Market Analysis**
+
+* Target audience: demographics, interests, gaming habits.
+* Market size and growth potential (cite reliable sources).
+* Competitor analysis: similar games or projects, and why yours is better/different.
+
+---
+
+### **6. Business Model**
+
+* How you plan to generate revenue:
+
+  * Game sales, subscriptions, in-app purchases, DLC, merchandising, crowdfunding.
+* Pricing strategy.
+* Any partnerships or distribution plans (Steam, Epic, App Store, etc.).
+
+---
+
+### **7. Development Roadmap**
+
+* Milestones and expected outcomes (don’t need specific release dates if you prefer flexibility).
+* Short-term and long-term goals.
+* Key dependencies (tools, tech, contractors, platforms).
+
+---
+
+### **8. Team**
+
+* Yourself (skills, experience, past projects).
+* Any collaborators, contractors, or advisors.
+* Highlight your ability to execute solo or with minimal overhead.
+
+---
+
+### **9. Financials**
+
+* High-level budget: development costs, marketing, platform fees, potential salaries.
+* Funding sought and equity offered (if relevant).
+* Revenue projections (conservative estimates are fine).
+* Burn rate and runway.
+
+---
+
+### **10. Risk Assessment**
+
+* Key risks (solo development, tech challenges, market competition).
+* How you plan to mitigate them (contingency plans, outsourcing, phased releases).
+
+---
+
+### **11. Call to Action**
+
+* What you want from the investor (funding, mentorship, networking).
+* How they can engage or follow progress.
+
+---
+
+### **12. Optional Extras**
+
+* Prototype or playable demo link.
+* Press clippings or community engagement metrics.
+* Early screenshots, animations, or concept art.
+* Testimonials from players or testers.
+
+---
+
+**Tips for a solo developer:**
+
+* Be honest about being solo—investors respect transparency if you frame it as a lean, efficient operation.
+* Focus on traction and proof-of-concept rather than big projections that aren’t grounded.
+* Visuals are key—show them what you’re building.
+* Keep it concise: investors often skim decks quickly; 10–15 slides or pages is ideal.
+
+---
+
+

brand-assets/packs/media/kit.md

@@ -0,0 +1,99 @@
+A media pack (or press kit) is a curated collection of materials that gives journalists, partners, or potential collaborators all the essential information about your brand, product, or project in one place. Since you’re an indie game developer and creative, I’ll focus it toward that, but this can apply broadly. Here’s a structured breakdown of what to include:
+
+---
+
+### **1. Cover / Intro**
+
+* Logo and tagline.
+* High-quality hero image or screenshot.
+* Short, punchy introduction to the brand or project (1–2 sentences).
+* Optional QR code or link to your website or landing page.
+
+---
+
+### **2. About / Background**
+
+* Company or team overview.
+
+  * Who you are (founders, team members, roles).
+  * Mission, vision, and values.
+  * Key achievements (awards, notable releases, partnerships).
+* Project/game overview.
+
+  * Genre, style, unique selling points.
+  * Current stage (in development, beta, released).
+
+---
+
+### **3. Key Media Assets**
+
+* High-resolution logo (various formats: PNG, SVG, etc.).
+* Game screenshots (varied angles, UI, action shots).
+* Concept art, character renders, environment shots.
+* GIFs or short gameplay clips (if possible).
+* Trailers or promo videos (hosted on YouTube/Vimeo with download links).
+
+---
+
+### **4. Fact Sheet / Quick Stats**
+
+* Release date or launch timeline.
+* Platforms (PC, console, iOS, Android, etc.).
+* Pricing / monetization model.
+* Download stats or early access numbers (if relevant).
+* Social media links and follower counts.
+* Press contact details (email, phone, PR contact).
+
+---
+
+### **5. Features / Selling Points**
+
+* Core gameplay mechanics.
+* Unique features or innovations (voice-controlled mechanics, procedural generation, VR support, etc.).
+* Art style and aesthetics.
+* Any noteworthy technology used (engine, AI, shaders, etc.).
+
+---
+
+### **6. Quotes / Testimonials**
+
+* Developer quotes: insight into inspiration or creative process.
+* Press quotes (if you’ve been covered).
+* Player or community quotes (if beta-tested).
+
+---
+
+### **7. Press / Recognition**
+
+* Previous coverage links or PDF clippings.
+* Awards or nominations.
+* Notable partnerships or collaborations.
+
+---
+
+### **8. Contact Information**
+
+* PR or press contact email.
+* Social media handles.
+* Website / landing page.
+* Optional: mailing address (if you send physical swag or demos).
+
+---
+
+### **Optional Extras**
+
+* Downloadable demo or beta keys.
+* Fact sheets for specific aspects of the project.
+* Brand guidelines (colors, fonts, logo usage).
+* Press release template for easy publication.
+
+---
+
+**Tips:**
+
+* Keep it concise and visually clean; journalists often skim.
+* Provide assets in high-resolution but optimize file sizes for downloads.
+* Make a PDF version and a web version for accessibility.
+* Include a “latest updates” section that you can refresh over time.
+
+---