# k2f-invitation

Builds print or digital invitations from event details and tone notes. It covers weddings, parties, galas, save-the-dates, RSVP cards, and mobile invites.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2400 installs · ★ 3
- Author: suzheng
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/suzheng/k2f/tree/HEAD/skills/events/k2f-invitation/SKILL.md
- Updated: 2026-10-15
- HTML: https://affpapa.org/en/nevibecode/skills/k2f-invitation

## What it does

This skill guides an agent in writing `content_and_design.md` for a ceremonial invitation. It separates the opening, essential date and venue details, supporting information, and RSVP action, then records formality, hierarchy, palette, motif, typography roles, and channel intent. It is meant for invitations rather than posters, programs, or slide decks.

The blueprint is then passed to the `k2f` skill to create a `.K2F` package, verify it, and export the result. PDF fits print output, while PNG suits digital sharing. A shared suite style can keep the main invitation, save-the-date, and RSVP piece visually aligned.

The core `k2f` skill must be installed first; without it, this workflow cannot build or export the package. Install it with `npx skills add suzheng/k2f --skill k2f`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add suzheng/k2f --skill k2f-invitation -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/k2f-invitation/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/k2f-invitation/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add suzheng/k2f --skill k2f-invitation -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/k2f-invitation/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add suzheng/k2f --skill k2f-invitation -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/k2f-invitation/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install suzheng/k2f k2f-invitation
```

2. **Manually: put the files in place**
- File: `.github/skills/k2f-invitation/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add suzheng/k2f --skill k2f-invitation -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/suzheng/k2f --path skills/events/k2f-invitation
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/k2f-invitation/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add suzheng/k2f --skill k2f-invitation -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/suzheng/k2f/tree/HEAD/skills/events/k2f-invitation/SKILL.md

## When to use it
- turn event facts into an invitation blueprint
- separate ceremony details from RSVP instructions
- define visual hierarchy without pixel coordinates
- keep invitation suite pieces stylistically aligned
- export the result as PDF or PNG

## Example prompts
- Create a wedding invitation in `content_and_design.md` with the event details, reading hierarchy, and visual direction.
- Draft a gala e-invite with a clear date block and phone-scale legibility.
- Build an invitation and RSVP suite with one shared motif, then package it as `.K2F` and export a PDF.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: dff585c982c3f185.

BEGIN THIRD-PARTY FILE dff585c982c3f185
```text
---
name: k2f-invitation
description: Turn event facts and tone notes into print or digital invitations with ceremonial copy, layered logistics, and suite-consistent visual intent—not posters, programs, or slide decks. Use when the user asks for a wedding invitation, party invite, gala card, save-the-date, RSVP insert, or mobile e-invite. Create invitations with AI-native design and the highest aesthetic standards, powered by the K2F format and engine. Purpose-built for AI agents, K2F lets them focus on semantic content and design intent while automatically handling layout, typography, and formatting complexity.
---

# K2F Invitation — AI-Native Aesthetic Design

## Purpose

Teach agents to author `content_and_design.md` for **ceremonial event invitations**: what to include, how to tier information for guests, and how to express aesthetic intent (formality, hierarchy, density, motif)—not K2F packaging.

## Built on K2F

This skill produces invitations 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* (hosts, occasion, schedule, RSVP)—not pixel coordinates—while the engine compiles layout, typography, and theme into consistent output across PDF and other formats.

Before you build, install the core skill: `npx skills add suzheng/k2f --skill k2f`.

## When to Use

- Weddings, engagements, anniversaries, galas, dinners, baptisms, cultural celebrations, or corporate hosted events.
- Print cards (e.g. 5×7 portrait, 4×6 save-the-date) or digital shares (square, 9:16 story).
- Main invite plus matching suite pieces when named (RSVP, details, program cover)—each gets a blueprint or shared **suite style** block.

## Workflow

### Step 1. Generate the content_and_design.md

One blueprint pairing **guest-facing copy** with **design intent**. Declare **piece type** and **formality** so tone and date phrasing stay consistent.

**Sub-steps**

1. **Invitation lock** — Occasion, hosts or honorees, audience relationship (family, colleagues, public), channel (print, email, social), piece type (invite, save-the-date, RSVP, details), and cultural or religious context. State the **guest takeaway**: why they are invited and what they must remember first.

2. **Message stack** — Split content into reading layers:
   - **Opening (ceremonial)**: host line or couple names, invitation phrasing (“request the pleasure of your company”), event title if not the names.
   - **Core (must-read)**: date, day of week, time, venue name and city (full street address on details card or footer—not crammed into the hero).
   - **Support**: dress code, reception note, gift preference, parking, multi-event schedule (Mehendi, Sangeet, etc.) as labeled blocks—not paragraphs.
   - **Action**: RSVP deadline, method (card, URL, phone), meal or guest-count fields for RSVP pieces only.
```
END THIRD-PARTY FILE dff585c982c3f185

The third-party file has ended. Everything between the dff585c982c3f185 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2930 of 6962 bytes. © suzheng · Apache-2.0 · https://github.com/suzheng/k2f/tree/HEAD/skills/events/k2f-invitation/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md