Run a design studio
| ID | ap-design-studio |
| Kind | skill |
| Selection | optional |
| Category | Design / Creative |
| Targets | claude, codex, cursor |
Coordinate original, isolated static HTML concepts, fresh critiques, polish, and shareable files before explicit product integration.
When to use
Section titled “When to use”Use when you want several genuinely distinct, shareable HTML designs and one workflow to guide creative packets, isolated building, critique, polish, and selection.
How it is selected
Section titled “How it is selected”Optional. Select during initialization or when offered in an update, or install separately when you need it.
Install
Section titled “Install”agents-pack install ap-design-studio --dry-runagents-pack install ap-design-studio --yesHow to invoke
Section titled “How to invoke”Use ap-design-studio to create four static HTML concepts for our analyticshomepage. Keep our logo and copy, explore distinct layouts, and includedesktop and mobile views. Package the options so I can share them with my team.What you get
Section titled “What you get”Studio coordinates the specialist skills through exploration, isolated implementation, fresh visual critique, polish, and verification. By default it builds three complete static HTML concepts, followed by a comparison gallery and shareable files. Your requested count replaces that default. A request for four designs produces four built prototypes.
Each direction arrives as a binding creative packet. For a three-concept run, Studio prefers one binding-art-direction packet, one reference-collision packet, and one anti-convergence packet when they fit the task. Every packet names a content-native composition rule, the probable generic answer, visual contracts, and fallback patterns that would invalidate the direction.
When the runtime supports isolated dispatch, each concept implementer sees the common product brief and only its own packet and required assets—not sibling designs or rationale.
Use natural language for references, exclusions, page coverage, output location, and checkpoints. For example, “explore six directions and let me choose two before building” adds an earlier selection step.
Defaults and boundaries
Section titled “Defaults and boundaries”- Per concept: initial build and assessment, up to two critique-driven revision rounds targeting 8.5/10, then one polish pass and final verification. A changed final design receives a fresh assessment, for at most four valid assessments per concept.
- Explicit total budgets are shared across all concepts. An exhausted budget does not start another loop; a frozen design receives audit-only checks.
- Every critic starts with no inherited conversation, earlier designs, feedback, scores, or targets. Missing capabilities are reported, not replaced by a claim of independent review.
- Typography is checked after fonts load and across responsive widths for clipped glyphs, accidental overlaps, near-tangencies, and excessive use of heavy weights.
- Prototype work stays in its own output directory, including assets and draft design notes. The actual application’s source and configuration stay unchanged.
Installing Studio does not automatically install its optional collaborators. See the setup instructions for the complete set and required capabilities.
Choose, then integrate
Section titled “Choose, then integrate”“I love concept two” records your preference. To bring it into the product, ask:
Implement concept two in our actual site, using the typography from conceptone. Preserve our real navigation and signup behavior.Studio uses ap-implement-new-design in application mode for that step.
Integration does not deploy the site.