# Make a studio with Homie

For a maker of games, music or video.

Say: “Make a studio for my games, music and video.”

Toolkit: @homie-rocks/studio 0.58.19. Keep this version throughout this task.

1. Read the [packaged setup skill](https://unpkg.com/@homie-rocks/studio@0.58.19/guides/studio-setup/SKILL.md) and [toolkit README](https://unpkg.com/@homie-rocks/studio@0.58.19/README.md) for installation in your AI app. If it requires a new session, reopen the project and continue the person's original request.
2. With a shell, create their project using `npx -y @homie-rocks/studio@0.58.19 new ./my-project --name "My project"`. Choose their name and an empty folder, then open that folder and read its AGENTS.md. For a remote assistant, [Homie's MCP](https://homie.rocks/mcp) offers `studio_scaffold` with `purpose: "studio"`; use the version and package links returned together by that call.
3. Follow the [packaged studio-setup skill](https://unpkg.com/@homie-rocks/studio@0.58.19/guides/studio-setup/SKILL.md) and the [packaged guides](https://unpkg.com/@homie-rocks/studio@0.58.19/README.md), or the same files under node_modules/@homie-rocks/studio. For payments read the [shop skill](https://unpkg.com/@homie-rocks/studio@0.58.19/guides/shop/SKILL.md); for reuse read the [parts skill](https://unpkg.com/@homie-rocks/studio@0.58.19/guides/parts/SKILL.md) and browse the [site catalogue](https://homie.rocks/parts/index.json).

Those files belong to this exact published version and are the authority for capabilities, commands, testing and approvals. Their tool names refer to the installed toolkit’s local MCP; the remote server has its own tools/list. Use the installed CLI or local MCP for tools absent from the remote list. Continue the person's request using them.