K2F Conference Handout — AI-Native Aesthetic Design

Purpose

content_and_design.md

Built on K2F

.K2F

npx skills add suzheng/k2f --skill k2f

When to Use

• After a talk is outlined or accepted; before or after slides exist.
• When the user wants something attendees keep, not a CFP, not full slide export, not presenter notes.
• Print or PDF distribution at workshops, meetups, or conference sessions.

Workflow

Step 1. Generate the content_and_design.md

1. Session lock — Event, session title, slot length, audience job and situation (not “developers”), vendor-neutral vs vendor-run tone, and whether product names are allowed. State what the handout must do: follow-up reference, not marketing.
2. Source spine — List the talk in running order with minute estimates (two levels). Mark each beat Keep, Compress, or Drop. Handouts mirror the arc, not the slide count.
3. Attendee layers — Structure content in four tiers:
   • Glance (10 s): title, speaker, event/date, optional QR or URL.
   • Scan (1 min): 2–4 verb-first takeaways scoped to slot length (lightning: one idea, one takeaway; standard: one problem, two or three actions).
   • Read (5–10 min): condensed sections aligned to the spine—hooks, diagrams, tables, code the room could not absorb live.
   • Later: links, repos, reading, prerequisites, contact—short, sourced from the user.
4. Progressive beats — Where the live talk used reveals or demos, specify the static equivalent in the design doc (numbered steps, before/after pair, screenshot description, final code state). Never leave a section that only made sense animated.
5. Cut pass — Remove pitch-first openings, book-sized scope, speaker-journey framing, and “understand/appreciate” bullets. Replace with attendee-side sentences and actions they can perform Monday.
6. Design intent — Document tone, hierarchy, density, and palette for the engine (no JSON):
   • Tone: attendee-facing; problem → approach → payoff; evidence and numbers the speaker can source.
   • Hierarchy: takeaways and section titles carry the story; body supports; footnotes and links recede.
   • Density: tighter than slides, looser than a paper—bullets and callouts over long paragraphs; cap ~800–1,200 words unless the user sets a limit.
   • Palette: calm professional base, one accent for takeaways and warnings; high contrast for print; code and figures called out as full-width or inline.

• One angle per handout: one problem and one through-line; split multi-topic talks into separate handouts.
• Takeaway test: every takeaway starts with an action verb and fits the slot; eight takeaways in twenty-five minutes fails the test.
• Attendee voice: rewrite “I’ll show our journey” into what the reader gains.
• Honesty gate: no invented benchmarks, customers, or citations; mark gaps the talk skipped.
• Static-only assets: video, iframe, or live demo → screenshot, steps, or repo link in the blueprint.

• Session lock and audience are explicit; tone matches event type.
• Spine mapped with Keep/Compress/Drop; one clear angle.
• 2–4 verb-first takeaways match slot length.
• Every live-only beat has a static substitute described.
• No pitch-first or speaker-centric openings; at least one sourced number or concrete system.
• Word budget stated; links and prerequisites in the Later layer.
• Design intent covers tone, hierarchy, density, and palette.
• All claims traceable to user-supplied material.

Step 2. Use the content_and_design.md and k2f skill to generate a K2F file and export to an appropriate file format.