microsoft / microsoft/agentsleague
Project: Creative Apps - Neon Myth Studio
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 286
- Forks
- 92
- Avg merge
- 12h 44m
- Merged PRs (30d)
- 1
Description
Track
Creative Apps (GitHub Copilot)
Project Name
Neon Myth Studio
GitHub Username
@UltimateCoding9
Repository URL
https://github.com/UltimateCoding9/neon-myth-studio
Project Description
Neon Myth Studio is a creative storytelling app that turns a small prompt into a complete micro-fiction package. Users choose a protagonist, genre, setting, signature object, emotion, and chaos level. The app generates a story hook, a three-beat narrative arc, a contextual dialogue duel, a cinematic poster prompt, a color palette, and an ASCII sigil.
The generator is seed-based, so results are reproducible and shareable. This supports remix workflows and makes demos deterministic for judges. The project includes a browser UI, a CLI mode, a local MCP server for Copilot integration, a Creator Vault (save/load/delete variants in local storage), compare mode, and creator-pack JSON export for reuse in demos or content workflows.
The app was built with GitHub Copilot-assisted workflows for ideation, refactoring, MCP scaffolding, and tests. Copilot usage is documented in COPILOT_USAGE.md. Reliability is covered by deterministic unit tests and no external APIs are required, which reduces secret-handling and runtime failure risk.
Demo Video or Screenshots
Demo Video (GitHub file): https://github.com/UltimateCoding9/neon-myth-studio/blob/main/docs/demo/neon-myth-demo.mp4
Screenshots: https://github.com/UltimateCoding9/neon-myth-studio/tree/main/docs/screenshots
Demo assets folder: https://github.com/UltimateCoding9/neon-myth-studio/tree/main/docs/demo
Primary Programming Language
TypeScript/JavaScript
Key Technologies Used
- Node.js (local server, CLI, tests)
- Vanilla JavaScript (UI + generation engine)
- HTML/CSS (responsive UI)
- Playwright (automated demo recording and screenshots)
- MCP (Model Context Protocol) local stdio server
- GitHub Copilot (development assistant)
Submission Type
Individual
Team Members
No response
Submission Requirements
- My project meets the track-specific challenge requirements
- My repository includes a comprehensive README.md with setup instructions
- My code does not contain hardcoded API keys or secrets
- I have included demo materials (video or screenshots)
- My project is my own work with proper attribution for any third-party code
- I agree to the Code of Conduct
- I have read and agree to the Disclaimer
- My submission does NOT contain any confidential, proprietary, or sensitive information
- I confirm I have the rights to submit this content and grant the necessary licenses
Quick Setup Summary
- Clone the repository
- Install dependencies:
npm install - Start the app:
npm start - Open
http://localhost:3000
Technical Highlights
- Deterministic seeded generator for reproducible creative outputs
- Multi-surface experience: Web UI + CLI + MCP server for Copilot
- Creator Vault for local variant save/load/delete/compare workflows
- Creator Pack JSON export for downstream content/demo pipelines
- Automated demo video and screenshot generation with Playwright
- Unit tests covering determinism, normalization, and export payload shape
Challenges & Learnings
- Balancing creativity with reproducibility led to a seed-first generation design.
- Template-based dialogue initially felt too generic, so the dialogue engine was refactored to include genre style, emotion, setting, object, and chaos context.
- MCP integration improved the project’s relevance for the Creative Apps track and required careful tool schema design.
Contact Information
koltman.a@gmail.com
Country/Region
Switzerland
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This issue is a project submission rather than a scoped change request, so it does not identify a file, failing test, or specific definition of done. Start with the submitted repository's README.md and COPILOT_USAGE.md, then follow the listed npm install and npm start steps to inspect the application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, javascript, node.js, playwright, typescript
- Domain
- cli, documentation, full-stack, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100