# Framework Slide Designer

> Designs a clean framework slide (2x2, value chain, process flow, pyramid, matrix) that communicates a structured idea without clutter or false precision.

- Skill: `andreworia/framework-slide-designer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add andreworia/framework-slide-designer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/andreworia/framework-slide-designer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: andreworia (https://skillmd.com/u/andreworia)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/andreworia/framework-slide-designer

---


# Framework Slide Designer

## When to use
Use this when the point is a structure rather than a number: a positioning 2x2, a value chain, a maturity model, an operating model, a phased roadmap. Use it when a framework slide is overloaded with boxes and arrows. Use it when a partner wants "the classic layout" for a concept.

## What it does
It lays out a conceptual framework so the structure reads instantly: the right archetype, balanced spacing, a clear reading path, and just enough labelling. It avoids the common failure of a framework that looks busy and says little.

## Method
A framework slide communicates a relationship between ideas. Pick the archetype that matches the relationship, then design it with restraint.

1. Name the relationship. Two crossing dimensions implies a 2x2 matrix. A linear sequence implies a process flow or value chain. A hierarchy implies a pyramid or tree. A set of parallel components implies columns or a wheel. Maturity over levels implies a stairway. Choose the one that fits.

2. Define the axes or stages precisely. For a 2x2, label both axes with a clear low-to-high meaning and name all four quadrants. For a flow, name each stage with a verb and keep stages MECE. Ambiguous axes are the top reason a 2x2 fails.

3. Place real content, not just labels. Each quadrant, stage, or box should carry one short line of substance, what it means or what goes there, so the framework informs rather than decorates.

4. Establish one reading path. The eye should know where to start and where to end. Left to right for flows, bottom to top for pyramids, a marked starting quadrant for matrices. Use position and a single accent to set the path.

5. Highlight the conclusion. The framework exists to make a point. Mark the quadrant you are in, the stage that is broken, or the layer that matters, with the accent color. The rest stays neutral.

6. Balance the geometry. Equal box sizes for parallel items. Even gaps. Consistent corner style. Align everything to a grid. A lopsided framework reads as careless thinking.

7. Limit arrows and connectors. Use arrows only for genuine flow or causation. Remove decorative connectors. Every line should mean something.

8. Add the so-what. The action title states the conclusion; the framework proves it. If the framework is generic, add a short callout that says what it implies for this client.

## Inputs
- The concept or relationship to show.
- The dimensions, stages, or layers involved.
- The conclusion the framework should drive to.

## Output format
Return the chosen archetype, the labelled axes or stages with one line of content each, the reading path, the element to highlight, and the geometry rules (sizes, gaps, alignment). Note where the framework risks being generic and how to make it client-specific.

## Example
Concept: which segments to invest in, by growth and profitability.
Archetype: 2x2, x-axis profitability low to high, y-axis growth low to high.
Quadrants: Invest (high/high), Nurture (high growth/low profit), Harvest (low growth/high profit), Exit (low/low).
Highlight: the two segments sitting in Invest, marked in accent; others gray. Callout: "Concentrate 70 percent of spend in the two Invest segments."