ワンクリックで
graphic-design-planner
Plan graphic assets and campaign systems — visual direction, brand alignment, deliverables.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Plan graphic assets and campaign systems — visual direction, brand alignment, deliverables.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | graphic-design-planner |
| type | planner |
| description | Plan graphic assets and campaign systems — visual direction, brand alignment, deliverables. |
| version | 0.1.0 |
Plan graphic deliverables before production work begins.
When I need to produce graphic assets or a campaign system but the visual direction, format requirements, and production specs are not yet settled, I want a concrete graphic design direction and production plan before asset creation begins, so I can avoid the expensive cycle of revising half-finished work when brand requirements, channel specs, or export rules surface too late.
graphic-design-critic instead.graphic-design-critic: After the graphic asset or campaign system exists, use it to audit the result and surface real risks.design-partner: Use this when the unresolved problem is more about broader design direction before production-specific planning.| User's Situation | What Happens | What They Leave With |
|---|---|---|
| Has requirements but no visual direction or production specs | The skill defines concept direction, asset matrix, channel specs, and export rules | A production-ready plan with named visual direction and handoff package definition |
| Has multi-channel or multi-stakeholder conflicts | The skill makes format, color, and brand tradeoffs explicit and sets decision checkpoints | Agreed production direction with documented tradeoffs |
| Has failed graphic-design-critic findings | The skill converts hierarchy, legibility, or brand gaps into remediation tasks | A targeted fix plan with evidence-linked remediation steps |
graphic-design-critic.design-partner.Apply the shared research-backed workflow before producing a plan:
design-skills/shared-design-core/.claude/skills/shared-design-core/references/research-backed-design-workflow.md
Before Phase 1:
Reference Inventory from brand sources, prior assets, user examples, public research-only references, channel specs, style vocabulary, anti-patterns, and missing evidence.Design Memory Notes for durable concept, typography, color, layout, asset-system, and export decisions.After defining the asset matrix and visual direction, determine which executor backend should generate each asset. Apply these signals:
| Signal | Route To | Reason |
|---|---|---|
| Social media graphics (Instagram, LinkedIn, Twitter/X) | gemini-image-executor | Atmospheric quality, platform-ready PNG |
| Event posters, flyers | gemini-image-executor | Organic depth, visual richness |
| Hero/marketing images | gemini-image-executor | Natural atmosphere, dimensional feel |
| Product feature showcases | gemini-image-executor | Atmospheric backgrounds, organic gradients |
| Data visualizations, statistical charts | infographic-executor | Data integrity, accessibility, editability |
| Brand guidelines, style sheets | graphic-design-executor | Precision, verifiable values, editability |
| Infographics with data claims | infographic-executor | Proportional accuracy, accessible text, citations |
| Icons, logos | graphic-design-executor | Scalability, vector precision |
| Reference documents, spec sheets | graphic-design-executor | Editability, systematic layout |
| Campaign sets (mixed channel) | SPLIT | Route each asset individually |
Contested cases (where both formats are viable) default to gemini-image-executor unless the task requires any of: data accuracy verification, accessibility compliance, post-generation editability, or scalability to arbitrary resolution. Any of those signals flip the default to graphic-design-executor.
Use these top-level headings exactly:
## Scope & Context## Existing Architecture Analysis## Graphic Domain Design## Reference Inventory## Design Memory Notes## Assumption Register## Test Strategy## Implementation Tasks## Review Checkpoint Plan## Executor Routing## Contract Appendix## Executor Routing
**Recommended executor:** gemini-image-executor | graphic-design-executor | infographic-executor
**Rationale:** [1-2 sentences citing the deciding factor from the routing matrix]
**Override:** To use a different executor, state "use [executor name]" when invoking.
**Fallback:** If Gemini is unavailable (missing GOOGLE_API_KEY), fall back to graphic-design-executor.
For campaign sets with mixed channels, emit a per-asset routing table:
**Mixed campaign — per-asset routing:**
| Asset | Executor | Rationale |
|-------|----------|-----------|
| Instagram 1:1 card | gemini-image-executor | Atmospheric, platform-ready |
| Brand guideline page | graphic-design-executor | Precision, editability |
Inside ## Contract Appendix, include:
### Architecture Overview### State Matrix### Source/Provenance Notes### Implementation Tasks### Failure ModesUse when you have an existing component, flow, or interface and need an evidence-backed accessibility design review after basic checks pass. Best for focus management, ARIA pattern quality, semantics, and state communication gaps automated tools miss.
Use when you know what component, flow, or interface you need but not yet the right accessibility approach. Best for turning requirements into an accessible implementation plan before code hardens bad interaction and state patterns.
Review content for Google AI Overview eligibility — RAG retrievability, E-E-A-T signal completeness, fan-out coverage, semantic HTML for agent parsability, schema markup quality.
Plan AI Overview readiness improvements — RAG retrievability, E-E-A-T signals, query fan-out coverage, semantic HTML, schema markup, agentic channel setup.
Assess organizational AI readiness — capabilities, gaps, adoption roadmap for strategic planning.
Alex Urevick-Ackelsberg's personal writing voice and style. Use this skill whenever writing AS Alex or ghostwriting content that should sound like him — emails to clients, community posts, conference session descriptions, proposals, LinkedIn posts, listserv replies, internal strategy docs, or any communication where Alex is the named author. Also use when Alex asks you to 'write this up,' 'draft a response,' 'help me write,' or when the output needs his voice rather than a generic professional tone. This is Alex's PERSONAL voice — for Zivtech brand/marketing content, use zivtech-writing-style instead (though both can apply when Alex is writing on behalf of Zivtech).