Build a strategic HTML deck with ak:slides

Use ak:slides to create a strategic HTML presentation from an approved topic, audience, and evidence set. The Skill combines slide strategies, layout patterns, design tokens, copywriting formulas, responsive HTML, and optional Chart.js data visualization. Its artifact is an HTML deck, not a native PowerPoint file.

Choose ak:slides for a reviewable HTML presentation

Use ak:slides when

• A marketing presentation or pitch needs a structured narrative and a browser- based deck.
• Approved metrics should appear as charts or dashboard-style slides.
• A product demo, sales pitch, case study, internal update, webinar, or workshop needs a consistent slide flow.
• You want a responsive artifact whose HTML, CSS, and JavaScript can be reviewed.

Choose another workflow when

• You only need one architecture or process image. Use ak:tech-graph or ak:mermaidjs-v11.
• The narrative or evidence is not approved. Research and review it before deck production.
• You require a .pptx, Keynote, Google Slides, PDF, or hosted presentation. Those formats and publishing steps are outside this Skill's stated output.

Prepare the brief and asset policy

Provide the audience, presentation goal, topic, preferred slide count, approved brand tokens, source material, claims, metrics, CTA, and desired output path. Mark unsupported numbers and testimonials for omission rather than invention.

The packaged HTML pattern can reference Chart.js from a CDN and can use remote background images. Those are optional external network dependencies. State whether the deck must work offline, whether third-party assets are approved, and whether local files may be written.

Create the deck

The first argument is the supported create subcommand. Remaining arguments describe the topic and slide count.

/ak:slides create Turn the approved customer-interview findings into a 7-slide sales deck for operations leaders. Use only cited evidence, write ./drafts/interview-findings.html, use no remote assets, and do not publish

/ak:slides create Turn the approved customer-interview findings into a 7-slide sales deck for operations leaders. Use only cited evidence, write ./drafts/interview-findings.html, use no remote assets, and do not publish

$ak:slides create Turn the approved customer-interview findings into a 7-slide sales deck for operations leaders. Use only cited evidence, write ./drafts/interview-findings.html, use no remote assets, and do not publish

If the output path or network policy is missing, clarify it before creating a file or loading an external dependency.

Follow the presentation stages

1. Confirm the brief. Establish audience, decision, narrative, evidence, slide count, CTA, brand constraints, and output path.
2. Select a strategy. Match the context to an available structure such as a product demo, sales pitch, case study, internal update, or workshop.
3. Build the narrative. Assign one job to each slide and use copy formulas only as framing, never as permission to manufacture urgency or proof.
4. Choose layouts. Map content to title, problem, solution, feature, comparison, timeline, metric, screenshot, or closing patterns.
5. Create responsive HTML. Use design tokens, a desktop 16:9 deck container, mobile breakpoints, navigation, progress, and bounded animation.
6. Add data visuals deliberately. Use Chart.js only for approved data and only when its dependency policy is acceptable.
7. Review the artifact. Open the HTML in an approved local preview, check every slide and viewport, and report the output path and remaining risks.

Keep claims, network access, and publishing separate

Ask before installing dependencies, loading CDN scripts, fetching remote images, or sending source material to an external provider. Keep credentials and private customer data out of the deck. A local HTML file does not authorize changing a campaign, spending budget, or contacting an audience.

Verify the HTML artifact and evidence

A complete run should provide:

• the exact .html output path;
• the slide count, audience, narrative, and CTA used;
• a mapping from each claim, quote, chart, and image to approved source material;
• evidence that desktop and responsive layouts were inspected;
• disclosure of remote dependencies or confirmation that none were used; and
• publication, hosting, or distribution steps still awaiting approval.

Inspect keyboard navigation, slide counter, progress, content overflow, chart labels, color contrast, and mobile layout. If the deck was not opened in a browser, record that visual verification is incomplete.

Troubleshoot and understand limits

The Skill does not guarantee persuasion, funding, sales, conversion, platform compatibility, or a native slide format. Continue with ak:tech-graph for a publish-grade technical visual or ak:docs for durable project context.

See the Marketing Kit overview and Marketing Kit Hooks.