k2f-event-program

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

K2F Event Program — AI-Native Aesthetic Design

K2F 活动手册——AI 原生美学设计

Purpose

用途

Teach agents to author

content_and_design.md

for published attendee programs: content selection, wayfinding layers, and aesthetic intent (register, hierarchy, density, tracks)—not K2F packaging.

指导 Agent 编写

content_and_design.md

，用于已发布的参会者手册：内容选择、导览层级和美学意图（视觉调性、层级、密度、轨道）——而不是 K2F 打包。

Built on K2F

基于 K2F 构建

This skill produces event programs as

.K2F

packages. Follow the k2f skill for authoring: unpack or init a workspace, edit the semantic tree, pack/verify, and export. K2F keeps agents on meaning (days, slots, sessions, social occasions, sponsors)—not pixel coordinates—while the engine compiles layout, typography, and theme into consistent output.

Before you build, install the core skill:

npx skills add suzheng/k2f --skill k2f

该 skill 会将活动手册生成为

.K2F

包。请遵循 k2f skill 进行编写：解包或初始化工作区、编辑语义树、打包/验证并导出。K2F 让 Agent 专注于语义内容（日期、时段、场次、社交活动、赞助商），而不是像素坐标；同时由引擎将布局、排版和主题编译为一致的输出。

开始构建前，请安装核心 skill：

npx skills add suzheng/k2f --skill k2f

。

When to Use

使用场景

Conferences, festivals, galas, ceremonies, or performances where guests carry or scroll a schedule live.
Print booklets, folds, or digital PDFs—not posters, invitations, VIP playbooks, or slide exports.
When times, rooms, and official social occasions are decided or marked draft.

会议、音乐节、晚宴、典礼或演出，且嘉宾需要在现场手持或滚动浏览日程。
印刷册页、折页手册或数字 PDF——而不是海报、邀请函、VIP 接待手册或幻灯片导出稿。
时间、房间和官方社交活动已经确定或被标记为草稿时。

Workflow

工作流

Step 1. Generate the content_and_design.md

第 1 步：生成 content_and_design.md

One blueprint pairing publishable facts with design intent. Document the programme; do not re-decide hospitality, VIP qualification, or grid placement—only what badgeholders should see.

Sub-steps

Program lock — Identity, dates, venue, audience, channel (print fold, booklet, digital), and guest job: find the next room in seconds. Note draft vs final; label gaps.
Publish boundary — Classify user inputs:
- Main grid: keynotes, sessions, breaks, meals—clock spine only.
- Official social slate: occasions the event runs; each row needs slot, place, access line (open, ticketed, family-inclusive, alcohol-free—in user terms).
- Invitation-only: only if approved for publication—“invitation only,” no lists, door rules, or rank markers.
- Third-party events: off-program or “permitted,” not on the official slate unless the user says so.
Attendee layers — Four tiers:
- Glance: cover plus day opener—title, dates, venue, one-line day arc.
- Scan: primary grid—time, room/track, title, speaker names (not bios).
- Read: optional blurbs, panel order, thanks—user-supplied only.
- Reference: maps, index, one-line bios, conduct or access pointer, sponsor tiers—back matter.
Chronology spine — Time leads each day; parallel tracks share clocks with declared track keys. Breaks, meals, and social rows are grid lines, not prose. If two official social options share an hour, name which clears inclusion commitments beside the slate.
Social placement — Main grid stays authoritative. Social rows use named slots; avoid pairing a public reception with an invite-only room in overlapping hours unless the user documents that split. No separate published room → fold into the general social line.
Cut pass — Drop mission essays, duplicate timetables, full CVs, slide URLs, backstage detail, and unordered sponsor logos. One grid per day plus optional opener.
Design intent (no coordinates):
- Register: conference, community meetup, gala, or playbill—match stated culture without inventing tiers.
- Hierarchy: time column or band first; title second; speakers third; room/track as cue; sponsors recede.
- Density: arm’s-length scannable spacing; clear day dividers; no flyer walls.
- Tracks: naming plus column or color-key intent for concurrent sessions.
- Discretion: minimal invitation-only lines; no wristband legends or door lists.
- Palette: neutral wayfinding base plus one accent (tracks or “now”); gala or performance contrast only from user cues.

Rules & constraints

Times and rooms match the user grid; flag conflicts, do not silently fix.
Official slate only; satellites labeled separately.
Concurrent social options: identify which clears the user’s access set or narrow the slate.
Record non-overlap requirements as facts; do not reschedule here.
No invented speakers, rooms, sponsors, or invitation lists—mark placeholders.

Common failure modes

Failure	Fix
Flyer density	Glance/scan/read/reference; marketing on cover only.
Slide export	Grid rows, not slide titles; short blurbs optional.
Hidden tracks	Track keys; aligned clocks across columns.
Tier leak	Invitation-only without lists or badge legends.
Fake choice slate	Label access-clearing option per hour or drop slot.
Evening clash	Slots so public and invite-only do not read as tier vs consolation.

Quality checklist

Program lock and draft/final noted.
Publish boundary classified (grid, slate, invitation-only, third-party).
Layers and chronology spine per day; track keys if needed.
Inclusion label for concurrent social hours when applicable.
Cut pass; design intent complete; non-overlap recorded; no fabricated facts.

创建一份将可发布事实与设计意图配对的蓝图。记录活动手册内容；不要重新决定接待安排、VIP 资格或网格布局——只呈现持证者应看到的内容。

子步骤

手册锁定——活动名称与标识、日期、场地、受众、输出载体（印刷折页、册页、数字版），以及读者任务：在几秒内找到下一会场。注明草稿版或最终版；标记缺失项。
发布边界——对用户输入进行分类：
- 主网格：主旨演讲、分场活动、休息和用餐——仅以时间为骨架。
- 官方社交安排：活动实际举办的社交场合；每一行都需要时段、地点、准入说明（开放、需购票、适合家庭、无酒精——使用用户提供的表述）。
- 仅限受邀：仅在获准发布时使用——“仅限受邀”，不列出名单、门口规则或等级标识。
- 第三方活动：属于场外活动或“获准参加”，除非用户另有说明，否则不纳入官方安排。
参会者阅读层级——四个层级：
- 概览：封面和每日开篇——标题、日期、场地、一句话概括当日安排。
- 扫读：主网格——时间、房间/轨道、标题、讲者姓名（不含简介）。
- 阅读：可选简介、讨论顺序、致谢——仅使用用户提供的内容。
- 参考：地图、索引、一句话简介、行为准则或无障碍指引、赞助商层级——置于附录。
时间主轴——每天以时间开头；并行轨道共享时间刻度，并声明轨道标识。休息、用餐和社交活动应作为网格行，而不是连续文字。如果两个官方社交选项发生在同一小时，应在活动安排旁注明哪一个满足纳入要求。
社交活动布局——主网格始终是权威依据。社交活动行使用已命名时段；除非用户明确说明分流方案，否则不要让公开招待会与仅限受邀活动在重叠时段并列出现。不要单独发布房间信息 → 应并入通用社交活动行。
删减检查——删除使命宣言、重复课表、完整履历、幻灯片链接、后台细节和无序赞助商标识。每天保留一个网格，另加可选的每日开篇。
设计意图（不涉及坐标）：
- 视觉调性：会议、社区聚会、晚宴或演出节目单——匹配既定文化氛围，但不虚构层级。
- 层级：首先展示时间列或时间带；其次是标题；第三是讲者；房间/轨道作为提示；赞助商信息弱化。
- 密度：适合远距离扫读的间距；清晰的日期分隔；不要做成海报墙。
- 轨道：并发场次的命名，以及列布局或颜色图例的意图。
- 克制：仅使用最简的“仅限受邀”信息；不包含腕带图例或门口名单。
- 配色：中性导览底色加一个强调色（用于轨道或“正在进行”）；晚宴或演出的对比效果仅依据用户提示。

规则与限制

时间和房间须与用户网格一致；标出冲突，不得擅自修正。
仅收录官方安排；场外附带活动需单独标注。
对于同一时段的社交选项，标明符合用户准入条件的选项，或缩减活动安排。
将不可重叠要求记录为事实；不要在此重新排期。
不得捏造讲者、房间、赞助商或邀请名单——缺失内容应标记为占位符。

常见失败模式

失败模式	修复方式
海报式信息密度	使用概览/扫读/阅读/参考层级；营销信息仅放在封面。
幻灯片导出稿	使用网格行，而不是幻灯片标题；可选用简短简介。
轨道被隐藏	使用轨道标识；各列时间刻度保持对齐。
等级信息外泄	仅限受邀活动不列出名单或身份腕带说明。
虚假备选安排	每个时段标明符合准入条件的选项，或删除该时段。
晚间时段冲突	合理安排时段，避免公开活动与仅限受邀活动看起来像主次等级或“安慰奖”。

质量检查清单

手册锁定信息已完成，并注明草稿版或最终版。
发布边界已分类（网格、官方安排、仅限受邀、第三方活动）。
每天均有阅读层级和时间主轴；必要时提供轨道标识。
同一时段有多个社交选项时，标注满足纳入要求的选项。
已完成删减；设计意图完整；不可重叠要求已记录；没有捏造事实。

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

第 2 步：使用 content_and_design.md 和 k2f skill 生成 K2F 文件，并导出为适当的文件格式

Follow k2f to instantiate the program from the blueprint, map roles from design intent, verify, and export (typically PDF).

按照 k2f 从蓝图实例化活动手册，根据设计意图映射角色，进行验证并导出（通常为 PDF）。