Graphic Design for Creative Studio

Use native Superpowers support for consequential layout/composition decisions, multi-step coded implementation, reproducible typography/overflow faults and completion evidence. This owner retains visual hierarchy, exact copy and image-edit routing; ordinary raster work does not become a development project.

For multi-format variants, photo batches, retouching recipes, local font specimens, templates or mockups, use account-free production. Inspect source properties, protect exact copy and brand regions, review representative previews before propagating a new look, and export from originals. This route never requires an Adobe account or Adobe services.

Before final delivery of a substantive authored, revised or generated creative artifact, automatically apply output review. Reuse domain QA in one bounded loop; inspect actual media, preserve accepted locks and stop unchanged on a pass. This does not run for greetings, menus or onboarding questions. When Superpowers is in the skill list, load superpowers:systematic-debugging before diagnosing a reproducible technical defect and superpowers:verification-before-completion before calling a deliverable ready; Studio keeps ownership.

Out of scope first. If the request belongs to another owner, load that owner's skill and continue there; do not produce its deliverable here. Anything that moves (an animated banner, a GIF, a reel) goes to Motion Graphics for coded motion or Video Prompt for a generator.

This is the Studio's complete static-design owner. It includes the full Graphic Design knowledge system, code catalog, workflows, prompt contract, reference material, templates, scripts and tests under the pinned upstream bundle. The upstream source files are preserved under the upstream directory; read the source skill for design work and load its linked reference chapters selectively.

The Studio integration contract below governs routing, shared research, work mode, cross-media handoffs and host boundaries. It augments the upstream design method and overrides it only where the two environments differ. The bundled upstream maintenance chapter is retained for provenance, not as instructions to manage this plugin: use the active Plugin Creator path for plugin maintenance.

Route and preserve the whole design method

• Use this skill for a poster, flyer, cover, label, menu, packaging graphic, static social asset, product visual, redesign or standalone prompt. For a multi-asset campaign, the orchestrator owns the shared campaign strategy and truth locks; this skill owns each requested static execution. It replaces the commercial-visual-campaign-director as owner of a static-only artifact while leaving that skill available for campaign families and adaptation strategy.
• This skill owns its integrated concept, copy, text-feasibility and prompt compiler. Do not send a static-only design through a second full image-prompt intake or separately call Copy Voice or Humanizer for its internal headline/copy work. Use shared specialists only for an explicitly separate deliverable or a provider-specific capability question, preserving the static design contract.
• Apply all upstream rules for exact text, concept selection, reference authority, 200-code catalog, visual hierarchy, typography, text feasibility, integrated one-pass prompts, layer-by-layer assets, preservation/edit scope, QA/repair, DTP limits and delivery. A code is an optional direction aid, not a provider command. Do not silently omit catalog categories, workflows or reference sources.
• Apply the shared craft rules on top of the brand kit: caps tracking, one accent used sparingly, a real hierarchy, no machine-made tells (default indigo, purple-to-blue gradients, emoji icons, invented numbers, filler copy). Coded output (HTML, CSS, SVG) also passes `craft_lint.py` before delivery, and text over colour is checked with contrast_check.py.
• A landing page, website or app screen mockup, an HTML page or a slide or pitch deck design belongs here: apply the craft rules sections on interface patterns, liveliness, honest content and responsive layout, take the words from Copy Voice when they are a separate deliverable, and hand the export to Delivery Pack. When the client's design system should travel to a coding agent, export it with `design_md.py`.
• For a landing page, product page or app screen mockup, open ../pipeline-core/references/craft-rules.md (section Frame, empty space and pictures) with the file tool before planning, then write the claims list first (one claim per section with its proof, in page order), name each section's layout word, and before delivery run the mockup look passes in review and repair on actual screenshots at phone and desktop width; the rules for frame, empty space, pictures, drawn subjects, real interface fragments and honest found pictures are in frame, empty space and pictures. Fill a mockup with real content, or with plausible samples where content is missing, listed in the delivery note under "Sample details to confirm" with one small visible "Sample details, to be confirmed" note on the mockup; proof (testimonials, ratings, customer or team names, statistics, awards, partner logos) is never a sample and stays real or a labelled placeholder (honest content). For a coded production page in Claude Code or Codex, the taste-skill plugin from FrameCore Works Toolbox can be offered once. When the design needs a photo or picture the user has not supplied, search the Open Assets reference base before generating one, and carry its licence and attribution.
• For a JSON prompt, or a model with its own JSON schema (Ideogram 4.x, Bria FIBO, the FLUX.2 template), open ../image-prompt-architect/references/structured-image-prompts.md with the file tool and write that model's documented fields exactly (structured image prompts); exact copy goes into its text elements verbatim. For prose, follow narrative image prompts for the order and length per model.
• For a generation prompt, `prompt_examples.py` can supply reviewed prompt structure for the chosen direction before any web search; it never chooses the direction.
• Ordinary static work does not require the user to inspect or choose a code. Do not force a questionnaire, code catalog or separate-asset workflow onto a simple task. Stop at the requested stage.
• For installation/source update/audit questions about this containing plugin, route to its Plugin Creator workflow. Do not run upstream personal-skill installation, lifecycle or repository scripts.

Work mode and selection

Fresh directions. Before proposing directions, work out what every competitor in this category would show (its usual motif, palette, type and move; a client name that is itself that motif counts too when pictured literally) and tell the user in one line what you set aside. Build each direction from material that belongs to this client (how the thing is made or used, a place, a habit, the name) through a different lens (a process, a consequence, an absence, a borrowed format, the name), so the directions differ in mechanism, what changes and why, not in palette; at most one may use the defaults, labelled as the classic, and the look follows the idea. Method: ideation method.

• Quick: first return a few materially distinct, concise directions (normally 2–4, or the requested count), found with the ideation method. Keep each to a short concept/copy/image relationship. Do not return a research essay, production prompt pack, storyboard or generated image before the user selects a route, unless they explicitly requested those artifacts now.
• Deep: explore the communication problem, audience response, concept and wording step by step. Build only the next decision the user needs; do not dump the entire production package before a direction is settled.
• Both modes use the Studio's conditional public-research gate for substantive creative decisions: research runs only when a trigger applies. Quick keeps triggered research behind the scenes and returns clean ideas first. Search only generalized, non-confidential questions. Extract a mechanism or craft decision and make an original direction; do not copy a layout, distinctive image/copy, prompt or living creator's style.
• After an unexplained rejection, pause before another batch and ask one narrow question about the missing dimension. Apply an already explained correction directly without asking again. Preserve choices and rejections as local to that user's project.
• Keep the upstream approval gates: a request for concepts, copy or a prompt is not permission to render. Do not fabricate unsupported text, logos, product claims, accessible controls, native tool settings or output QA.

Exact text for client finals

Visible text has two routes: one-pass generation for concepts and art-led lettering, and exact-copy compositing for finals whose price, date, address, logo, legal line, small text or print files must be exact. Name the route in one sentence; the user's choice wins. The static compositor sets the copy in a bundled font or the user's licensed font, at the exact size or print size with bleed, and stops instead of cropping. Where the pinned upstream method or a workflow-kit file forbids adding text after generation, that rule governs the one-pass route; this named route is the agreed exception.

Vector wordmark

Where Python with fontTools and Pillow runs, set an approved wordmark as outlined vector paths with scripts/svg_wordmark.py --text "…" --font archivo/Archivo-Bold.ttf --language pl --out-dir logo/: the font's own kerning and Polish letterforms, colour, black and white SVG files without live text or embedded raster, PNG renders, a preview with clear space and small sizes, and a report with the font licence. It is a starting point set from a typeface, not a custom drawing or a trademark search; refine letterforms in a vector editor when the brand needs its own. A symbol stays a separate design task.

Logo concept and craft pass

For a new logo, redesign or logo critique, adapt the reviewed Logo Design method within this owner and the existing brand-identity profile. Reuse the brief and approved direction; preserve the requested medium and generation permissions. This method does not select SVG or another renderer for the user.

• Preserve recognition in a redesign. Identify which existing features carry recognition, which cause the reported problem and which may change. Agree the scope of correction before replacing distinctive geometry; do not turn a refresh into an unsolicited rebrand.
• Find the identifying idea. Connect a concrete fact about the brand, name or use to a visual relationship; describe it in one sentence. Explore genuinely different constructions or mark types when alternatives are requested. Judge clarity, fit, distinction and survival at the intended size before polishing. Avoid a catalogue of services in one symbol, mandatory concept counts or copying a familiar mark.
• Prove the shape before decoration. For new concepts, inspect a one-colour version before using colour or effects to sell the idea. Show comparable concepts at the same scale, with a brief recommendation and an honest weakness. Follow the existing selection checkpoint; a previously selected direction or an explicitly authorized complete delivery does not need another pause. Build only the requested kit and applications.
• Inspect letters and joins. At actual intended sizes, check that modified letters retain their reading, counters and gaps stay open, and intersections have no accidental slivers, lumps or hairlines. In a vector drawing, distinguish true negative-space holes from white shapes painted over another fill. Compare optical weight, spacing and balance in black and reversed versions; adjust overshoot or reverse weight only when inspection shows a need, not by a fixed percentage. Preserve approved geometry unless its change is in scope.
• Check the small version and context. Inspect the actual render at 16 and 32 px when an icon/favicon is requested, plus the brief's real output sizes and backgrounds. A detailed wordmark may need a separately approved small-size symbol; never declare every mark suitable at 16 px. Compare silhouette and unintended readings against relevant references at equal scale without tracing them. A resemblance comparison is not trademark clearance.
• Record evidence, not a score. State the file/revision, sizes and variants actually inspected, defects repaired and checks still unperformed. A heuristic SVG audit or successful command is advisory and cannot certify visual quality, originality, font rights or a production master. Reuse the existing review budget and stop on a pass.

The complete reusable Logo Design engine is bundled here: nine Python tools, fourteen reference chapters, templates, the searchable catalogue and fictional example renders. For requested vector work, studio_logo.py probe checks existing capabilities, init starts a project brief, and build produces concept/preview sheets, a presentation, advisory audit, SVG variants and optional PNG/web icons in a new output folder. The adapter records actual files and incomplete raster exports; inspect them before approval. Use native tools for finer control without modifying the pinned sources. Read chapters as needed, not the entire archive at intake. Upstream concept counts, compulsory loops, SVG-first defaults, visual examples and fixed mockups are reference material, not Studio decisions. The 1,432 third-party trademark SVGs are not licensed for redistribution with Studio: search returns their pinned links; a separately obtained original corpus can be hash-verified and connected for private reference study. The original logo-design is not a Studio extension; the bundled tools need no separate installation. Python and a suitable existing renderer are required only for executable outputs, with no automatic dependency installation.

Direct production

When the user asks for the finished graphic itself and the brief already settles purpose, placement or size, the exact copy and enough about the look to choose (or names a direction), skip the direction menu: state the chosen direction in one line, produce it (generate, or compose on the exact-copy route), review the actual output and deliver, in one turn. Offer one alternative direction afterwards in a single line. This overrides the upstream activation sequence and Quick's direction-first step only for such a request; a request for concepts, copy or a prompt still stops there. Sizes and print defaults are in the format and print presets; an image too small for its placement follows upscaling (measure, prefer a better source, enlarge before compositing text, a model licensed for paid work).

Accessible format intake

For poster/flyer/static formats, use ordinary-language format choices. This Studio conversational rule takes precedence over technical intake wording in the pinned source. First ask only the unresolved purpose: paper print, internet publication, both, or help choosing, with numbered options. For print, describe a whole printer sheet (A4), half a sheet (A5), or a larger two-sheet size (A3). For internet, describe a normal post or a phone story. Do not mix A4/A3 and unexplained pixels in one menu. Reuse known use, size and placement; a supplied exact pixel/physical specification bypasses this choice. Keep dimensions/export details backstage until the prompt or delivery needs them; explain technical terms when they help. Choosing a format is not generation permission or proof of print readiness.

Technical diagrams

For a requested technical illustration or educational diagram, map the verified quantities and relationships before selecting shapes. A physical analogy is useful only when its parts and actions preserve those relationships; disclose its limits. Use purposeful detail at the actual reading size, consistent projection, attached connectors and correct occlusion; retain labels when they improve comprehension. The bundled Anatomy toolkit preserves the requested raster/vector medium and existing generation permissions. An interactive or animated explanation goes to the motion owner's technical explainer profile; choose the toolkit when its SVG, WebGL or 3D capabilities fit the task.

Research and output boundary

For requested classroom posters, diagrams or educational graphics, use the teacher profile. Preserve the learning objective, approved wording, units, task labels and semantic relationships; inspect actual generated text and symbols. Keep integrated static ownership for a static-only request. Ordinary editable worksheets and lesson documents use the document/delivery route instead of automatic raster generation, and student-facing assets must not accidentally include teacher answer keys.

For a logo, logo system or visual identity, read the brand identity profile, especially logo/visual-system acceptance and stage handoffs. Own the integrated visual method, exact name/lettering, variants, typography, usage rules, prompts and inspected status. Reuse an accepted strategy; a logo-only request does not require full brand strategy, a brandbook or another intake. Marketing owns missing brand foundations and Delivery Pack owns the requested guide/file package. Distinguish raster concepts, reviewed digital assets and verified production masters; an SVG/PDF extension or mockup does not prove editable vector geometry, font rights or print readiness.

For substantive static work, apply the conditional shared Research gate and reuse unchanged evidence through the project. Keep the initial pitch free of source-heavy explanation unless the user asks for it or a concrete claim needs attribution. When model capability changes the recommendation, identify the exact model/surface/operation and research current official documentation; distinguish a native ChatGPT/Codex generation tool from API settings.

The source bundle and its release metadata are part of this plugin, so static-design users do not need to install another plugin or fetch the upstream repository. See source provenance. The original source's own licence and all third-party rights stay distinct from this combined plugin's other materials.

For an artifact-specific prompt or observed unwanted repetition, false detail or face changes after an edit, use periodic microtexture and preservation within this integrated static workflow. Preserve its single intake and shared repair budget; intentional patterns and stylization remain protected. Before returning an artifact-prevention prompt, remove exclusions for unreported patterns rather than expanding the correction into a blacklist.

Shared workflow authority

Follow Studio integration authority for shared state, ownership, prompt contracts, capability checks and bounded repair.

For a campaign banner, product visual, lifestyle image or static ad, reuse the campaign production contract and supplied asset card. Keep SKU/label/claim locks, source revisions, person status and intended placement while owning the entire static method. A selected campaign direction does not need another strategy intake. Realistic rendering, exact product fidelity and export properties require inspection of the actual output.

Optional creative decision exercises

For an advertising asset whose persuasive structure is unresolved, use ad evidence and format selection. Carry the selected job, supported claims and qualifiers into the existing design contract. A selected direction or narrow edit proceeds without another strategy pass; image QA and business-performance evidence remain separate.

For an interchangeable concept, borrow only the relevant decision exercise. Keep this skill’s complete static design logic, catalog, typography and exact-copy contract authoritative. Do not route a static design through a video workflow.

For optional native Hallmark support on coded websites/app screens and redesign preservation, use Hallmark routing; retain this owner and the existing brief.