Skill

create-studio

Generate a specialized Claude Code studio for any tech stack. Infers patterns from existing code or accepts user-defined conventions.

npx claudepluginhub dvrd/ui-studio --plugin studio-generator

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Generate a new Claude Code studio tailored to a specific project or stack.

SKILL.md

Similar Skills

setup-claude-code

Generates Claude Code project setups including CLAUDE.md, hooks, permissions, commands, and agents. Analyzes stack (TypeScript, JavaScript, Python, Go, Rust, etc.) to create minimal/standard/full configs.

bkit-starter

solo-scaffold

Scaffolds full projects from PRD + stack templates: directory structure, configs, CLAUDE.md, git repo init, GitHub push. Studies existing projects via SoloGraph, uses Context7 for library versions.

1 file15 tools

solo

prompt-mini

Refines vague Claude Code prompts into structured, project-context-aware instructions by scanning package.json, CLAUDE.md, imports, and directory structure.

4 files

prompt-mini

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 17, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Create Studio

Generate a new Claude Code studio tailored to a specific project or stack.

Steps

Gather context

Ask the user: what project do you want to generate a studio for?
Is there existing code? If yes, get the project path.
If no code: what stack/framework? What conventions should the studio know?

Detect or confirm stack

If project path provided: call create_studio with project_path — patterns are inferred automatically
If no code: call create_studio with stack_description and optionally user_conventions

Generate the studio

With existing code:

create_studio(
  name: "{project-name}-studio",
  project_path: "/path/to/project"
)

Without code:

create_studio(
  name: "{stack}-studio",
  stack_description: "Next.js 14 + Drizzle + Stripe + Clerk",
  user_conventions: "... conventions text ..."
)

Report result

Show what patterns were inferred
Remind user to restart Claude Code to activate the studio
Show path where the studio was installed

Notes

Studios are installed to ~/.claude/plugins/{name}/

The MCP server is registered in ~/.claude/settings.json automatically

To refresh patterns after adding more code: use expand_studio

Each studio gets its own pattern MCP server + session hook + rules

Create Studio

Generate a new Claude Code studio tailored to a specific project or stack.

Steps

Gather context
- Ask the user: what project do you want to generate a studio for?
- Is there existing code? If yes, get the project path.
- If no code: what stack/framework? What conventions should the studio know?
Detect or confirm stack
- If project path provided: call create_studio with project_path — patterns are inferred automatically
- If no code: call create_studio with stack_description and optionally user_conventions

Generate the studio

With existing code:

create_studio(
  name: "{project-name}-studio",
  project_path: "/path/to/project"
)

Without code:

create_studio(
  name: "{stack}-studio",
  stack_description: "Next.js 14 + Drizzle + Stripe + Clerk",
  user_conventions: "... conventions text ..."
)

Report result
- Show what patterns were inferred
- Remind user to restart Claude Code to activate the studio
- Show path where the studio was installed

Notes

Studios are installed to ~/.claude/plugins/{name}/
The MCP server is registered in ~/.claude/settings.json automatically
To refresh patterns after adding more code: use expand_studio
Each studio gets its own pattern MCP server + session hook + rules