Amu-chan Developer -v1.0- -kano Workshop- 〈2026〉
Amu-Chan Developer -v1.0- -Kano Workshop- is a significant experiment in affective computing for software development. By prioritizing emotional safety, constrained tool use, and persona-driven interaction, it challenges the notion that developer tools must be neutral and robotic. While not suitable for all contexts, its success in lowering barriers for beginners and reducing burnout among indie creators validates the Kano Workshop’s ethos. As local LLMs improve, Amu-Chan may represent a template for the future of companion coding agents.
(Best for a game description, Steam page, or fan-fiction intro)
"System Boot... Check. Memory Allocation... Check. Soul Synchronization... 100%." Amu-Chan Developer -v1.0- -Kano Workshop-
From the depths of the Kano Workshop, a new spark of life emerges. Meet Amu-Chan, the v1.0 Developer unit.
She isn't your average digital companion. Created with meticulous care by Kano, Amu-Chan represents the perfect harmony between high-functioning code and heartfelt design. Whether she is pointing out a missing semicolon in your script or simply reminding you to take a break, her presence turns the sterile environment of a development terminal into a warm workspace. Amu-Chan Developer -v1
This is only the beginning—version 1.0. Watch as she grows, learns, and codes alongside you. Welcome to the workshop.
The -v1.0- specification defines three layers: (Best for a game description, Steam page, or
| Layer | Component | Description |
|-------|-----------|-------------|
| 1 | Persona Engine | System prompt with character card, memory of user’s preferred coding style, and rejection rules. |
| 2 | Tool Use | Restricted function calling: explain_code(), suggest_fix(), draw_ascii_diagram(), calm_user() (for frustration detection). |
| 3 | Output Filter | Limits code block length, adds friendly warnings, strips proprietary data, appends # Amu-Chan was here ~ to every suggestion. |
Storage: Uses a local .amu_chan JSON file to remember user’s project naming preferences, typical errors, and pet names (e.g., “you can call me Senpai if you want”).