k2f-invitation
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.
- Installs
- 2.7K
- Last 24h
- +141
- Trending rank
- #1542
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/suzheng/k2f --skill k2f-invitation- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads k2f-invitation automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
-
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.
-
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.
-
Content tiers — Hero (names or occasion + emotional hook), Ceremony (when/where stack), Courtesy (host parents, religious wording, bilingual lines), Footer (website, registry note, map cue). Drop backstory, long bios, and duplicate URLs. Save-the-dates omit full ceremony copy; RSVP cards omit decorative essays.
-
Formality fit — Match copy shape to style:
- Formal/traditional: spelled-out dates and times, full legal names, third-person host lines.
- Modern/casual: first names, numeric dates, conversational invite line.
- Multi-event/cultural: ordered sub-events with date-time-venue triplets; note symbols, language, and color symbolism in design intent—not as unexplained decoration.
-
Suite alignment — If multiple pieces: one shared palette, motif, and type roles; per-piece content only what that piece must carry. Save-the-date leads with date/location tease; main invite completes the story; RSVP is field-focused.
-
Cut pass — Remove marketing slogans, full agendas, three fonts worth of quotes, and every extra CTA. One RSVP path; registry and website in footer cluster.
-
Design intent — Document for the engine (no coordinates):
- Tone: one style family (classic elegant, modern minimal, floral romantic, rustic organic, destination relaxed, ornate cultural)—aligned to venue and dress code.
- Hierarchy: display names or occasion largest; date/venue as second band; supporting lines smallest; never three competing display lines.
- Density: invitations breathe—generous margins; cap to essential lines; motif frames content, not competes with it.
- Palette & motif: 2–4 harmonious colors; botanical, geometric, cultural, or typographic motif—stated as intent, not stock-keyword lists.
- Typography roles: at most three roles (e.g. script display, serif ceremony, sans detail).
- Channel: print texture or foil intent vs digital legibility at phone scale (bold date band, high contrast).
Rules & constraints
- One piece, one job: do not merge RSVP fields onto a save-the-date unless the user asks.
- When/where stack: date, time, and place appear as a scannable block—never buried in flowing prose.
- Honesty gate: no invented venues, times, hosts, or traditions; label placeholders.
- Cultural respect: symbols and bilingual text only when user supplies or requests; do not invent ritual language.
- Suite consistency: repeating pieces share motif and palette notes in a Suite style subsection.
Common failure modes
| Failure | Fix |
|---|---|
| Poster/flyer density | Enforce Hero/Ceremony/Footer; move maps and schedules to details card. |
| Cluttered ornament | Motif at edges or watermark; center field for type. |
| Flat hierarchy | One display line for names; structured date band below. |
| Format clash | Formal spelled-out date with ultra-casual body—pick one lane. |
| Missing RSVP clarity | Dedicated action line with deadline and method. |
| Generic wedding template | Anchor palette and motif to user venue, season, or culture. |
| Digital unreadable | Promote date/venue; simplify script at small sizes in intent. |
Quality checklist
- Invitation lock: occasion, piece type, channel, formality, guest takeaway.
- Opening / core / support / action layers populated; tiers assigned.
- Formality-appropriate date, time, and name treatment.
- Design intent covers tone, hierarchy, density, palette, type roles, channel.
- One primary RSVP or attendance path; footer for secondary links.
- Suite style noted if multiple pieces; cut pass applied.
- No fabricated facts; placeholders labeled.
Step 2. Use the content_and_design.md and k2f skill to generate a K2F file and export to an appropriate file format.
Follow k2f skill to instantiate the invitation from the blueprint, map roles from design intent, verify, and export (typically PDF for print or PNG for digital sharing).
FAQ
What does the k2f-invitation skill do?
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.
How do I install k2f-invitation?
Run npx skills add https://github.com/suzheng/k2f --skill k2f-invitation in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/k2f-invitation/ (personal) or .claude/skills/k2f-invitation/ (project).
Which AI agents can use k2f-invitation?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is k2f-invitation safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains k2f-invitation?
It is published by suzheng in suzheng/k2f. It has 2,659 recorded installs.
More from suzheng/k2f
k2f-worksheet
suzheng/k2f
Design printable, fill-in-ready worksheets—practice sets, graphic organizers, lab records, reflections, or gap-closure forms—from learning goals and source material. Use when the user asks for a worksheet, handout with answer spaces, practice problems, graphic organizer, or structured questions students complete in class or at home. Create worksheets 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-quotation
suzheng/k2f
Create client-ready sales quotations from scope notes, line items, rates, and terms—structured so buyers can compare options, accept, or convert to an invoice without rework. Use when the user asks for a quotation, quote, estimate, proposal pricing, or RFQ response. Create quotations 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-idml
suzheng/k2f
Blueprint multi-page print publications—brochures, magazines, catalogs, annual reports, lookbooks—for designer handoff with spread-aware story flow, typed editorial blocks, and art direction before layout. Use when the user asks for InDesign, IDML, editorial layout, print collateral, or an editable package for a production designer. Create idmls 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-sales-deck
suzheng/k2f
Turn discovery notes, proposals, and product proof into buyer-ready sales decks with a prospect-centered story, one objective per meeting, and evidence-backed slides. Use when the user asks for a sales deck, demo presentation, proposal deck, executive briefing, or sales slides (not a fundraising pitch deck or generic company overview). Create sales decks 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-flyer
suzheng/k2f
Turn event details, offers, or brand notes into a single-page flyer with a scannable headline, one primary call to action, and mood-matched visual intent—not a brochure, slide deck, or poster wall. Use when the user asks for a flyer, leaflet, handout, promo sheet, open-house sheet, or print/digital one-pager for events, sales, restaurants, fitness, real estate, hiring, or community campaigns. Create flyers 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-resume
suzheng/k2f
Turn career history, notes, or an existing CV into a tailored, achievement-led resume with clear hierarchy and scannable proof—not a generic duty list or keyword-stuffed template. Use when the user asks for a resume, CV, job application document, or role-targeted career summary (including refresh for a specific job posting). Create resumes 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.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.