studio

Generates visual assets by routing to a structured prompt engineering procedure.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/manusco/wolfgang --skill studio-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: studio
Source: https://github.com/manusco/wolfgang/tree/main/.cursor/skills/studio
Command: npx skills add https://github.com/manusco/wolfgang --skill studio-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating consistent, high-quality visual assets requires disciplined prompt engineering, which is hard to reproduce manually. This Skill routes the /studio command to a defined design procedure so visual asset generation follows a repeatable, structured workflow. ## Core Features & Use Cases - Command Routing: Maps the /studio command directly to the underlying studio design procedure. - Structured Prompt Engineering: Delegates to a procedure that produces visual assets through disciplined prompt construction. - Definition of Done Enforcement: Executes the referenced procedure exactly, including its completion criteria. - Use Case: A designer needs a set of on-brand marketing visuals; invoking /studio runs the full design procedure and delivers assets that meet the documented Definition of Done. ## Quick Start Run the /studio command to generate production-ready visual assets following the studio design procedure.

Frequently Asked Questions about studio

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate visual assets with the /studio command?▼

Invoke /studio and the Skill routes the request to the studio design procedure, which it reads and executes in full. The procedure handles structured prompt engineering and produces the visual assets according to its Definition of Done.

What does the studio skill actually do?▼

It acts as a router: the /studio command loads and executes the design procedure located at .agents/skills/design/studio/SKILL.md. All generation logic lives in that referenced procedure, not in this file.

Where is the studio procedure defined?▼

The procedure is defined in .agents/skills/design/studio/SKILL.md. The /studio command file only routes to that location and instructs the agent to execute it exactly, including its Definition of Done.

What happens if the referenced studio procedure file is missing?▼

The Skill depends on reading .agents/skills/design/studio/SKILL.md in full. If that file is absent or moved, the routing fails and the /studio command cannot complete the asset generation workflow.