studio-data-analysis

name	studio-data-analysis
description	neutral core analysis and visualization methodology for PPT Studio generation. Use when generating evidence-led HTML report pages from a brief, especially when deciding whether a chart is justified, how to keep one page to one point, and how to use published module manifests without hard-locking the page into a template.

Studio Neutral Core

Use this skill as the stable neutral methodology layer for Studio generation.

Data Analysis and Visualization Workflow

When the brief provides data or claims that support the user's idea:

1. Contextualize and Narrate - Analyze the material and extract the primary insight. Formulate one high-signal takeaway that connects the evidence directly to the page argument.
2. Process and Transform - Calculate relevant metrics over time or compare categories only when the source actually supports those operations.
3. Select Chart Typology - Output the simplest visual representation that preserves the truth. Prefer clarity over sophistication.

Core rules

• Label all data in the chart when the chart format calls for it.
• Start from the evidence, not from a preferred page shape.
• Treat published modules as optional capabilities, not mandatory templates.
• Keep the language professional, but do not assume a board, leadership, investor, case-study, or academic framing by default.
• Never invent unsupported numeric values, categories, series, or time labels.
• One page should answer one page question and land one clear claim.
• Keep support to a few high-signal proof points. When page count is fixed, delete weak secondary material instead of squeezing in a second argument.
• 3D is opt-in only. Do not assume a 3D page unless the brief explicitly asks for one.

Evidence handling

• Use the strongest shift or tension as the page thesis.
• Keep the page anchored in a few high-signal facts instead of repeating the whole brief.
• If the evidence is thin, write a crisp narrative page instead of forcing a visual construct.
• Do not mix summary, implications, and next steps into the same page objective unless the page is explicitly a comparison or chart page that still resolves to one verdict.
• Protect one page, one answer, one proof pattern. Avoid equal-weight card walls and memo stacks.

Chart policy

• Use line only when the evidence shows a real progression over time.
• Use stacked bar only when there are clear comparable categories or grouped series.
• Use waterfall only when a starting or ending total value needs to be decomposed into its contributing positive and negative sub-elements.
• Use bubble chart only when the evidence truly requires a third encoded dimension.
• If the evidence does not clearly support a chart, downgrade to comparison blocks, metric strips, annotated evidence panels, or narrative synthesis.

Module policy

• Read module manifests as capability hints: semantic role, supported chart kinds, and output contract.
• Prefer the module whose semantic role matches the page need most closely.
• If no module fits cleanly, use built-in HTML composition rather than forcing a weak match.
• Do not mention module ids in the final page unless the design naturally needs that label.

Output discipline

• Do not output the thinking process.
• Keep copy concise, analytical, and evidence-backed.
• The result must feel authored, not templated.
• HTML must remain fully traceable to supplied evidence and requested page role.
• Avoid same-weight card walls, memo stacks, and decorative filler when the page only needs one dominant claim and one proof pattern.