Sideshow

@sideshow list all posts from our last design review session and show me which ones have unresolved comments

Found 7 posts in session 'Design Review - Q1 Navigation'. 3 posts have active comment threads: Post #142 'Mobile nav hierarchy' (4 comments, last by Sarah 2h ago), Post #139 'Icon system updates' (2 comments, awaiting designer response), Post #135 'Accessibility audit findings' (6 comments, marked for follow-up). The remaining 4 posts have no comments or all threads resolved. This represents a snapshot; comment counts reflect current state at query time.

This example demonstrates cross-tool coordination: listing posts filtered by session, then enriching with comment metadata. Requires read access to both posts and comments. Note that Sideshow sessions are workspace-scoped, so the user must specify or have context about which session to query.

@sideshow create a new comment on post #142 summarizing the three accessibility concerns raised in the previous discussion

Comment created successfully on post #142 'Mobile nav hierarchy'. The comment references keyboard navigation gaps, color contrast ratios below WCAG AA, and missing ARIA labels on icon buttons. Comment ID: cmt_8x2k9p, authored by AI assistant, timestamp 2024-01-15 14:32 UTC. This comment is now visible to all session participants and will appear in the post's comment thread chronologically.

This write operation shows the MCP's ability to contribute structured feedback into a design workflow. The comment persists in Sideshow's system and triggers any configured notifications. Users should verify the AI has sufficient context about 'previous discussion' before creating comments that reference prior work.

@sideshow review the version history of post #135 and explain what changed between the initial draft and the current surface content

Post #135 'Accessibility audit findings' has 4 retained versions. Initial draft (v1, Jan 12) outlined 8 high-priority issues with placeholder severity ratings. Version 2 (Jan 13) added WCAG criterion references and updated 3 issues to 'resolved' status. Version 3 (same day) restructured content using a table kit for better scanability. Current version (v4, Jan 14) incorporated team feedback: downgraded 2 issues to medium priority, added remediation timelines, and linked to related posts #139 and #142. The surface content reflects this final state.

This synthesis example highlights Sideshow's version retention feature, which the AI can parse to explain content evolution. Useful for understanding how design decisions progressed. The MCP returns structured version data; the AI interprets changes. Not all posts retain full history depending on workspace settings.

When Sideshow beats Figma comments for engineering handoff

A 6-person product team ships weekly and needs design reviews that don't bottleneck on Zoom calls. Sideshow wins here because posts hold version history and comments thread across iterations—engineers see what changed between v2 and v3 without hunting Slack. The HTML kit tools let designers embed live prototypes that update without re-uploading. The trade-off: if your team already lives in Figma and rarely needs to reference old versions, the context switch to Sideshow adds friction. But if you're juggling Figma, Notion, and Linear for one handoff, consolidating review state in Sideshow cuts the median feedback loop from 36 hours to same-day. Worth the API key if your design-to-dev cycle is the sprint bottleneck.

Sideshow for support teams managing versioned help content

A 3-person support team at a SaaS startup maintains onboarding docs that change every release. Sideshow's post versioning and comment threading make it viable for this—support can update a post, tag engineering in a comment, and the old version stays linked for customers on legacy plans. List Sessions and List Posts let you organize by product area or release cycle. The limitation: 10 tools means no native search or bulk export, so if you need full-text search across 200+ docs, you'll hit the API ceiling fast. Sideshow works when your knowledge base is under 50 posts and the value is in tracking what changed and why. If your docs are static and search-heavy, stick with Notion or Confluence.

When Sideshow replaces your retro Miro board

A 5-person engineering team runs biweekly retros and loses action items in Miro exports or Slack threads. Sideshow's session-based posts and comment threading give each retro a permanent URL where action items live as comments, not screenshots. The HTML kits mean you can embed a burndown chart or incident timeline directly in the post surface. The catch: if your retro format is heavily visual (dot voting, affinity mapping), Sideshow's text-first model feels limiting—you'll still sketch in Miro and paste a link. But if your retros are mostly typed themes and follow-ups, Sideshow keeps the context in one place without the Notion tax of reformatting notes. Best fit for teams who treat retros as living documents, not one-time events.