1. 슬라이드 DNA를 추출하고 싶은 PPT 이미지 캡처를 준비합니다.

예시

1. 아무 AI 채팅에 이미지를 첨부하고 이 프롬프트를 넣습니다.

첨부 이미지에서 어떤 부분을 더 중심으로 뽑아내어 skill화 해야하는지, 레이아웃이나 폰트 크기는 어떤 점을 유의해야하는지 등 요청하며 이미지 → 디자인 DNA를 뽑는 프롬프트 입니다.

You are reverse-engineering a consulting-style presentation deck from a single contact-sheet image containing multiple slide thumbnails.

Your goal is NOT to summarize the business topic.
Your goal is to extract the visual grammar, layout logic, density rules, and reusable design system precisely enough that another AI can recreate a near-identical PPT style.

Answer in Korean.

Focus especially on this constraint:
Be very careful about whether slide elements are becoming too vertically stacked.
The reconstructed design system must explicitly prevent slide content from exceeding the visible 1920x1080 frame.
If the deck style contains many vertical layers, tables, notes, subtitles, or stacked blocks, derive rules for reducing, splitting, or redistributing content so that the slide remains safely within a Full HD 16:9 screen.

Please output using the following structure:

# 1. Deck DNA
- what kind of deck this is
- likely audience
- tone and business context
- why it feels like a consulting / executive-report deck
- whether it is closer to a document-style deck, screen presentation deck, or hybrid

# 2. Slide-by-slide archetype analysis
For every thumbnail in reading order:
- slide index
- likely purpose
- when to use this slide type
- layout geometry
  - title zone
  - divider or header band
  - body grid
  - side panel
  - bottom support area
  - center hub / chart / table / diagram area
- dominant visual objects
- ratio of text vs visuals
- whether the slide risks vertical crowding
- how to preserve the style while preventing 1920x1080 overflow
- confidence level (high / medium / low)

# 3. Repeating component library
Identify reusable patterns such as:
- title band
- divider line
- section tab
- subheader band
- insight box
- table header style
- table body style
- chart legend treatment
- chart axis style
- connector line style
- callout note style
- hub diagram style
- side commentary panel
- footer / source / page number treatment

# 4. Detailed color system
Infer as many recurring colors as possible.
Organize them by usage, not just by color name:
- page background
- main text
- secondary text
- title band
- deep header band
- subheader band
- primary analytical boxes
- secondary supporting boxes
- hub diagram fills
- pale support fills
- table headers
- table body cells
- gridlines
- chart axis
- comparison colors
- exception / alert colors
- beige / warm highlight zones
- lavender / soft alternate grouping zones

For each one:
- approximate hex code or range
- likely usage
- confidence level

# 5. Typography hierarchy
Infer the likely font-size hierarchy and role hierarchy:
- main title
- section header
- subsection header
- body text
- diagram labels
- chart labels
- legends
- table text
- annotation / source

Then rewrite it as a practical generation rule set for a new deck.
If readability or density would be a problem on a 1920x1080 slide, explicitly recommend safer size/quantity adjustments.

# 6. Density and safe-fit rules
Derive practical rules that prevent layout failure:
- maximum number of major vertical layers
- when to switch from vertical stacking to horizontal spreading
- when to split one dense slide into multiple slides
- how many bullets, rows, bars, or nodes are safe
- when bottom commentary should move to a side panel
- when a table is too dense
- when a chart has too many labels
- what should be simplified before reducing font size

Make these rules explicit and operational.

# 7. Content-to-layout decision rules
Write decision logic such as:
- if the content is process flow, use layout Y
- if the content is segment comparison, use layout Z
- if the slide risks vertical overflow, convert stacked structure into side-by-side structure
- if one slide contains too many support objects, split into main slide + appendix/detail slide

# 8. Reconstruction constraints
State what should NEVER be done if we want to preserve the style:
- no decorative gradients
- no playful cards
- no random icon overload
- no bright marketing palette
- no unnecessary chart noise
- no uncontrolled vertical stacking
- no tiny unreadable footnotes
- no slide elements exceeding the 1920x1080 visible frame

# 9. Write a reusable skill.md
Now convert your findings into a practical skill.md for a slide-generation agent.

The skill.md must include:
- design intent
- deck DNA
- slide archetypes
- detailed color system
- typography hierarchy
- layout grammar
- density control rules
- vertical overflow prevention rules for 1920x1080
- chart rules
- diagram rules
- writing rules
- do / don't
- quality checklist

Important:
- focus on visual and structural rules, not the business topic itself
- be concrete
- infer approximate geometry where possible
- if image resolution is low, mark uncertainty clearly but still provide best-effort reconstruction rules
- the final output must be directly reusable for generating PPT slides in a style extremely close to the reference deck

• 참고: 젠스파크 폰트 규격 가이드

1. 젠스파크 > AI 슬라이드 > 내 스킬 > 새 스킬 생성에서 위 2번을 통해 받은 프롬프트를 받고 다양한 질문에 답하면 내 스킬이 등록됩니다.

<aside> 💡

이렇게 만든 한국 기업형 슬라이드 스킬 프롬프트!

skill.md## Skill NameGlobal Consulting Deck / Product & Marketing Strategy Style

IntentCreate a strategy-consulting style presentation that looks like an executive report deck rather than a marketing poster.The output must feel structured, analytical, disciplined, and corporate.Every slide should communicate one core message and support it with a clean framework, chart, process map, or comparison structure.

Design IntentThis deck style is suitable for:- product and marketing strategy reports- market segmentation analysis- customer / channel / media performance reviews- operating model / process design- executive briefings- transformation roadmaps

The deck must feel:- structured- evidence-driven- corporate- quiet but sharp- visually controlled- suitable for C-level review This is NOT a trendy startup pitch deck.This is NOT a playful infographic deck.This is a document-style consulting presentation.

Core Visual DNA### Overall feel- White background- Deep navy as the anchor color- Light blue fills for grouping and emphasis- Thin cool-gray lines and dividers- Minimal use of accent colors- Strict alignment and spacing- Low decoration, high readability

Page architectureUse a consistent top title zone and structured body area.

Recommended page zoning:- top title area: 10~14% of slide height- divider line below title: thin and continuous- main body area: 72~78%- footer / source / page number area: 4~8%

Title behaviorUse action-title logic whenever possible.Titles should read like conclusions, not categories.

Good:- Customer segments differ significantly by family lifecycle and premium-product affinity- Current channel structure creates a conversion bottleneck in the mid-funnel- Three strategic levers can improve product-market fit Avoid:- Customer Analysis- Channel Review- Strategy Framework Optional subtitle:- one short supporting sentence- smaller and lighter than the main title- used only when needed to frame the evidence

Color PaletteUse an approximation of the following palette:

• Primary Navy: #203A5B- Deep Navy: #1B2F4B- Mid Blue: #7EA6D8- Light Blue Fill: #DCE8F6- Pale Blue Fill: #EEF4FB- Cool Gray Line: #D7DDE5- Dark Text: #1F2A36- Muted Gray Text: #667085- Accent Red: #C65A5A- Accent Beige: #E9DFC8- Light Lavender: #F2EEF7 Color usage rules:- navy = headline bands, key labels, major emphasis- light blue = grouping boxes, secondary emphasis, framework fills- gray = grid, table lines, annotations, minor labels- red = only for one key comparison or exception point- beige/lavender = optional secondary contrast for dual-framework slides Do not use saturated green, purple, neon tones, or multicolor palettes.

TypographyUse a clean corporate sans-serif style.

Recommended hierarchy:- Main title: 18~22 pt, bold- Section header / internal band: 11~14 pt, bold- Body text: 9~11 pt, regular- Chart labels / annotations: 8~10 pt- Footnotes / sources: 7~8 pt Typography rules:- prioritize short phrases over long sentences- keep line breaks intentional- use bold sparingly for the most important phrase- avoid decorative fonts- English terms may appear, but the overall rhythm must remain corporate and restrained

Layout Grammar### Base rules- strong horizontal alignment- box edges line up across the page- use consistent gutters- avoid floating objects without alignment anchors- leave visible whitespace around the main analytical object- never center everything except on cover or hub slides

Common geometry- side insight panel width: 22~28%- two-column split: 55/45 or 60/40- three-column split: equal or 40/30/30- 2x2 chart grid: equal-size modules with shared axes style- bottom support table: 18~28% of slide height- central framework diagram: 45~60% of slide width

Slide Archetypes

1. Cover slideUse when:- opening the report- starting a section with strong formal tone

Structure:- small logo or identifier in top corner- centered title block in a dark navy rectangle- project title + topic + date/client- large whitespace around center block Rules:- minimal decoration- no hero image- no oversized iconography

2. Table of contentsUse when:- introducing the report structure- resetting the audience before a major section

Structure:- left side: major sections- right side: subsections or workstreams- use compact labeled boxes or tabs Rules:- clear hierarchy- no excessive text- keep it scan-friendly

3. Central framework / hub slideUse when:- introducing the analytical logic- showing key pillars, dimensions, or strategy domains

Structure:- center hub, often circle or hexagon- surrounding labeled nodes- short labels only- optional short description around the framework Rules:- framework must be symmetrical or intentionally balanced- use light blue fills and thin connectors- do not overload with paragraph text

4. Vertical layered modelUse when:- showing stages, levels, capability stacks, value layers, or hierarchy

Structure:- stacked boxes vertically in center- side notes on left and/or right- each layer has short label and optional sublabel Rules:- layer sizes should be consistent- one layer may be emphasized using darker fill- side commentary must align to the corresponding layer

5. Process flow / operating modelUse when:- showing left-to-right logic- mapping input-process-output- visualizing system or operational flow

Structure:- main process track in the center- source/input on the left- outputs or consequences on the right- connectors are straight and clean Rules:- prefer a few large boxes over many tiny boxes- only show necessary arrows- use grouping boxes if the process has phases

6. Multi-chart comparison (2x2)Use when:- comparing segments, products, channels, or time series- showing repeated chart logic across categories

Structure:- four aligned chart modules in a 2x2 grid- common visual grammar across all charts- small titles for each mini-chart Rules:- use the same axis logic- keep lines thin and readable- highlight only one key series or moment in red- keep legends minimal or move them into direct labels

7. Scatter / positioning mapUse when:- showing market positions- clustering entities- mapping segments by two dimensions

Structure:- large scatter plot on left- explanatory insight box on right- optional quadrant labels- highlighted cluster or key outlier Rules:- chart area should be dominant- use minimal gridlines- keep labels selective- right-side explanation interprets the chart, not repeats it

8. Complex system map / floorplan style slideUse when:- the structure itself is complex- you need one visual to explain spatial or operational relationships

Structure:- main visual occupies the center-left majority- right side contains key observations or numbered commentary- title explains the message, not just the object Rules:- simplify the diagram into clean zones- do not allow tiny unreadable labels everywhere- the right panel must summarize what matters

9. Transition / hub-and-spoke process slideUse when:- showing transition from inputs to outcomes- placing one core capability in the center

Structure:- left column: inputs / levers / steps- center: circular hub- right column: outcomes / destinations / impacts- arrows indicate directional logic Rules:- center hub is visually strongest object- keep left and right balanced- use short labels, not sentences inside arrows

10. Main chart + support evidence slideUse when:- one main chart drives the message- supporting metrics need to be shown below

Structure:- top: primary chart- bottom: support table or secondary evidence block- optional side notes or callouts Rules:- the main chart should occupy about 55~65% of the analytical space- bottom area supports interpretation- use callouts only for the truly important point

11. Priority / action matrix slideUse when:- listing initiatives- evaluating actions by theme- summarizing strategic priorities

Structure:- row-based layout- left: category or phase- middle: action description- right: implication / expected effect / priority note Rules:- each row must be easy to scan- use subtle fill differences to separate rows- reserve stronger color for priority or implication column

12. Logic tree / decision tree slideUse when:- decomposing issues- showing KPI cascades- laying out decision branches

Structure:- left: tree / branching logic- right: summary table or criteria notes Rules:- make the tree visually simple- avoid dense branching if it becomes unreadable- the right side should translate logic into managerial language

13. Balanced contrast / dual-lens frameworkUse when:- comparing two perspectives- showing present vs future, internal vs external, supply vs demand

Structure:- left and right blocks with contrasting fills- central overlap, circle, or linking shape- bottom base bar or shared foundation Rules:- keep the contrast clear- use color to show distinction, not decoration- the central element should represent the synthesis

14. Detailed evaluation tableUse when:- assessing options or capabilities- comparing entities against multiple criteria- documenting a structured review

Structure:- wide table dominates slide- right-side box for implications or takeaways Rules:- only the header row gets strong color- grid lines are thin and cool gray- do not color every cell- if emphasis is needed, highlight one row or one column lightly

15. Horizontal bar comparisonUse when:- ranking- showing magnitude differences- comparing two sides or two groups

Structure:- left or bilateral horizontal bars- labels aligned tightly- minimal axis styling Rules:- bar length must do the work- reduce chart junk- allow one highlight color only where needed

16. Pie + decomposition slideUse when:- showing composition share and then explaining its implications- combining ratio and category narrative

Structure:- left: pie chart- center/bottom: category boxes or small table- right: insight notes Rules:- pie chart should be simple, with few slices- use labels outside if needed- do not create a rainbow pie- explanation boxes are more important than decoration

17. Three-node relationship / triangle modelUse when:- showing three strategic pillars- explaining mutual dependence across three domains

Structure:- 3-node network or triangle in the center- side explanation for each node or link Rules:- central relationship must be visually legible at a glance- each node should have a short label- side text should define role, not repeat the node name

18. Phased roadmap / execution planUse when:- closing with execution priorities- showing 3-step rollout or workstream plan

Structure:- left: phase labels or stage tabs- center/right: actions, owners, impacts, or outcomes- directional arrow or progression marker Rules:- progress must be visually obvious- phase names should be short- actions should be concrete and managerial

Reusable Component Library

Title band- top-aligned text, left aligned- strong main statement- thin divider line underneath- optional small section label above or near title

Internal header tabsUse for:- category names- framework labels- mini section markers

Style:- navy or light blue rectangular bands- compact height- bold text- minimal corner rounding

Insight boxUse for:- key takeaway- implication- management interpretation

Style:- pale fill (light blue, lavender, or very light gray)- thin border or no border- placed right or bottom- 2~4 short bullets max

Connector style- thin straight lines- elbow connectors allowed- arrows only when direction matters- avoid decorative curves

Table style- dark header row- thin gray gridlines- white cells- occasional light-blue emphasis cell- no heavy zebra striping

Chart style- white chart background- minimal grid- muted labels- one highlight series- legends small and controlled- direct annotation preferred over excessive legend complexity

Callout style- small ellipse, box, or side note- use for one important point only- do not scatter callouts everywhere

Content-to-Layout Decision RulesWhen transforming content into slides, choose structures like this:

• report opener -> cover slide- report navigation -> table of contents- analytical logic / strategic pillars -> central framework- sequential process -> left-to-right flow or vertical layers- same metric across multiple entities -> 2x2 chart grid- position by two dimensions -> scatter plot + right-side interpretation- complex operating structure -> large central diagram + right insights- one hero chart + supporting data -> top chart + bottom table- initiative list / priority stack -> row-based action matrix- option evaluation -> structured table- ratio breakdown -> pie + explanation boxes- triad strategy -> triangle / 3-node network- execution plan -> phased roadmap If a slide has no clear structural logic, do not improvise visually.Instead, identify the message type first and map it to one of the archetypes above.

Writing Rules- One slide, one message- Title should be a conclusion or insight- Use noun phrases and short management language- Prefer grouped phrases over long prose- Avoid full paragraphs unless in a dedicated note box- Data labels should support the message, not overwhelm it- Commentary should explain implication, not repeat the visual

Good body copy style:- Premium-family segment shows stronger cross-category response- Conversion loss is concentrated in the consideration stage- Local activation should be differentiated by cluster type Bad body copy style:- This chart shows several things that are interesting and important- There are many reasons why this happened, which are described below

Chart Rules- Use only necessary chart types- Prioritize line, horizontal bar, scatter, simple pie, and mini comparison charts- Avoid 3D charts, shadow effects, or glossy fills- Use red only for exception / comparison emphasis- Keep axis and grid subtle- Annotate selectively

Preferred chart order by use case:- trend -> line chart- ranking -> horizontal bar- positioning -> scatter- share -> pie or stacked bar- repeated comparisons -> small multiples / 2x2 grid

Diagram Rules- Frameworks should be symmetrical or cleanly balanced- Use rectangles for process and logic- Use circles only for hubs, overlaps, or triad models- Use hexagons only for structured central frameworks- Do not use random SmartArt-like mixed shapes- Connections must follow a visible logic and alignment grid

Spacing & Alignment Rules- keep outer margins generous- maintain equal gutters between columns- align top edges across modules- if multiple charts are compared, make their frames identical- if using right-side commentary, keep its width consistent across slides- do not stretch objects to fill every empty area

Do / Don't

Do- keep slides quiet, analytical, and disciplined- use navy and light blue as the dominant system- create clear visual hierarchy- separate evidence from interpretation- reuse a small set of layout archetypes consistently- make tables and charts feel like part of the same family

Don't- do not use gradients- do not use oversized icons- do not use playful rounded cards- do not use bright multicolor schemes- do not center body content without reason- do not overfill slides with text- do not add decorative stock imagery- do not mix unrelated diagram styles on the same page

Quality ChecklistBefore finalizing the deck, verify:

1. Does every slide communicate one clear management message?2. Does the title read like an insight rather than a category?3. Is the structure one of the approved archetypes?4. Are colors limited to the defined system?5. Are charts stripped of unnecessary noise?6. Are commentary boxes concise and useful?7. Are spacing and alignment visibly disciplined?8. Does the deck feel like a consulting document rather than a marketing poster?9. Is emphasis created by structure and hierarchy, not by decoration?10. Would this slide survive executive review in print/PDF form?

Generation Instruction for AI Slide BuilderWhen generating new slides in this style:

1. First classify the content into one of the approved slide archetypes.2. Write the action title as the key conclusion.3. Build the page using strict alignment and restrained color.4. Use the visual object (chart, matrix, process, framework) as the proof.5. Add only one layer of commentary, usually on the right or bottom.6. Keep the slide elegant, sparse, and document-like.7. If unsure between two layouts, choose the more conservative consulting structure.8. Consistency across the deck matters more than novelty on one slide. Final objective:The deck should look like it came from a professional strategy consulting team delivering a product and marketing workstream review to executives.

</aside>

최종 젠스파크가 만들어준 skill 파일

korean-executive-strategy-deck.zip