event-print-deck-system

Create coordinated event, deck, print, stationery, and on-ground brand systems from design tokens.

2|Updated Jun 19, 2025
One-click install
npx skills add https://github.com/Prat05devs/dapper-city-threads --skill event-print-deck-system-prat05devs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: event-print-deck-system
Source: https://github.com/Prat05devs/dapper-city-threads/tree/main/.agent/skills/event-print-deck-system
Command: npx skills add https://github.com/Prat05devs/dapper-city-threads --skill event-print-deck-system-prat05devs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Producing event, conference, print, and deck assets often results in disconnected one-off creatives with inconsistent branding and unapproved claims. This Skill turns a project's design.md, tokens, and approval rules into a coordinated system of institutional, event, and print assets. ## Core Features & Use Cases - Event System Design: Define event motive, theme, audience, agenda structure, speaker and partner systems, venue treatment, and registration CTAs as one coherent identity. - Deck and Print Rules: Establish title slide, section divider, and data slide roles plus print rules covering bleed, safe areas, contrast, and approval zones for letterheads, certificates, invitations, backdrops, and signage. - Child Skill Routing: Route ID cards, badges, visitor passes, and credentials to the dedicated id-card child skill with a structured handoff. - Use Case: A team planning a summit provides their design.md and confirmed speaker list, then receives a full asset system covering hero graphics, agenda cards, partner strips, certificates, backdrops, and deck slides with correct approval status on every name and date. ## Quick Start Use the event-print-deck-system skill to create a coordinated event identity and print asset system from my project's design.md file.

Frequently Asked Questions about event-print-deck-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a consistent event branding system?▼

Provide a canonical design.md with tokens, brand architecture, and confirmed event details. The skill defines the event motive, theme, audience, speaker system, partner system, and CTA, then produces coordinated digital and on-ground assets rather than isolated creatives.

What print and stationery assets can this skill generate?▼

It covers letterheads, certificates, invitations, proposal covers, business cards, brochures, standees, banners, backdrops, signage, and report covers. Each asset follows rules for logo clarity, contrast, bleed, safe areas, and readable text at final print size.

How are ID cards and event badges handled?▼

ID cards, badges, visitor passes, and credentials are routed to the dedicated id-card child skill through a structured handoff. The handoff references design.md as canonical and generates all badge variations in one scrollable HTML file by default.

What inputs are required before starting event or deck work?▼

The skill prefers design.md, brand-architecture.md, department-use-cases.md, public-claim-rules.md, verbal and visual language files, token files, and confirmed event details. If design.md is missing or stale, work returns to the context architect first.

Does the skill prevent publishing unapproved event claims?▼

Yes. Approval status is tracked for speakers, partners, dates, and institutional references, and the output gate blocks unapproved claims from being published. Person data, QR payloads, and access levels are treated strictly as confirmed, inferred, or missing.