post-acceptance
This skill should be used when the user asks to "prepare conference presentation", "create presentation slides", "design poster", "make academic poster", "write promotion content", "create Twitter thread", or mentions post-acceptance conference preparation. Provides comprehensive workflow for presentation, poster, and promotion content creation.
What this skill does
# Post-Acceptance Conference Preparation A post-acceptance conference preparation workflow that helps researchers efficiently complete presentations, posters, and promotional content. ## Core Features ### 1. Presentation Slide Creation Guidance for creating conference presentation slides: **Time Control** - 15-minute talk: 10-15 slides - 20-minute talk: 15-20 slides - 30-minute talk: 20-30 slides - Average 1-1.5 minutes per slide **Content Structure** - Title slide (1) - Motivation/Problem (2-3) - Method overview (3-5) - Key results (3-5) - Conclusion (1-2) - Q&A/Thank you (1) **Visual Design Principles** - One key message per slide - Use figures and diagrams over text - Consistent color scheme and fonts - Minimum font size: 24pt for body, 32pt for titles - High-contrast colors for readability **Presentation Tips** - Practice timing with a stopwatch - Prepare backup slides for anticipated questions - Use animations sparingly and purposefully - Include slide numbers for Q&A reference ### 2. Academic Poster Design Guidance for creating conference posters: **Standard Sizes** - Portrait: 24x36 inches or A0 (841x1189mm) - Landscape: 36x24 inches or A0 landscape - Check conference requirements for specific size **Layout Structure** - Title bar (top): Title, authors, affiliations, logos - Introduction (left): Problem statement, motivation - Method (center): Key approach, architecture diagram - Results (right): Main findings, tables, figures - Conclusion (bottom): Summary, future work, QR code **Design Guidelines** - Readable from 4-6 feet distance - Title font: 72-96pt - Section headers: 36-48pt - Body text: 24-32pt - Use bullet points, not paragraphs - Include QR code linking to paper/code ### 3. Promotion Content Creation Guidance for creating promotional content after paper acceptance: **Twitter/X Thread** - Thread structure: Hook -> Problem -> Method -> Key Result -> Link - First tweet: Attention-grabbing summary with emoji - Include 1-2 key figures - End with paper link and relevant hashtags - Tag co-authors and relevant accounts **LinkedIn Post** - Professional tone, 3-5 paragraphs - Highlight practical implications - Include key figure or diagram - Add relevant hashtags **Blog Post** - 800-1500 words - Non-technical summary for broader audience - Include figures with explanations - Link to paper, code, and demo ## When to Use Use this skill in the following scenarios: - **After paper acceptance** - Prepare presentation materials for the conference - **Poster session preparation** - Design and create academic poster - **Research promotion** - Create social media and blog content - **Conference talk preparation** - Structure and practice presentation ## Workflow ### Presentation Workflow ``` Paper accepted -> Identify key messages -> Create slide outline -> Design slides -> Practice timing -> Prepare Q&A backup slides ``` ### Poster Workflow ``` Paper accepted -> Choose layout template -> Extract key content -> Design poster -> Print test at reduced size -> Final print ``` ### Promotion Workflow ``` Paper accepted -> Write Twitter thread -> Create LinkedIn post -> Draft blog post -> Schedule posts around conference dates ``` ## Best Practices ### Presentation - Start with the "so what" - why should the audience care - Tell a story: problem -> insight -> solution -> impact - Use concrete examples and demos when possible - Anticipate questions and prepare answers - Arrive early to test equipment ### Poster - Design for scanning, not reading - Use visual hierarchy to guide the eye - Include a "elevator pitch" summary - Bring business cards or QR codes - Practice a 2-minute and 5-minute explanation ### Promotion - Post within 1-2 weeks of acceptance notification - Coordinate timing with co-authors - Engage with comments and questions - Share across multiple platforms - Include accessible descriptions for figures ## Summary This skill provides a comprehensive post-acceptance workflow covering three key areas: presentation slides, academic posters, and promotional content. Following these guidelines helps researchers effectively communicate their work at conferences and to the broader community. ## Reference Files Load only what is needed: - `references/design-guidelines.md` - visual design guidance - `references/deliverable-checklists.md` - slide/poster/promo-specific checklists - `examples/post-acceptance-plan.md` - compact delivery plan example
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.