# Issue Interaction Cards

Adds a new interaction card kind to the issue thread, end to end.

- Repository: https://github.com/paperclipai/paperclip (109885 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add paperclipai/paperclip --skill create-issue-interaction-ui -g -a claude-code -y`
Codex: `npx skills add paperclipai/paperclip --skill create-issue-interaction-ui -g -a codex -y`
Cursor: `npx skills add paperclipai/paperclip --skill create-issue-interaction-ui -g -a cursor -y`
Gemini CLI: `npx skills add paperclipai/paperclip --skill create-issue-interaction-ui -g -a gemini-cli -y`

## Description

Add a new Paperclip issue-thread interaction kind end-to-end. Use when repo work introduces or extends interaction cards like request_confirmation, checkbox confirmations, ask_user_questions, or suggest_tasks.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Create a new issue-thread interaction UI (Developer/maintainer skill)

Developer/maintainer skill. Do NOT install this on production Paperclip agents.

This skill walks a Paperclip contributor through introducing a new issue-thread
interaction kind from shared contract to issue-detail wiring, helpers, and
docs. It is intentionally a developer/maintainer skill: the audience is a
human or coding agent making code changes inside `paperclipai/paperclip`, not
the operational agents that run inside a deployed Paperclip company.

Do NOT install this on production Paperclip agents. This guide is for repository contributors changing Paperclip itself.

## When to use

- A new interaction kind is being introduced (compact picker, structured
  rating, in-thread approval card, etc.).
- An existing interaction needs a parallel variant with a distinct payload
  shape, validation, or resolution outcome (and `ask_user_questions` is the
  wrong fit because option count, target binding, or result shape differs).
- A reviewer asks for "the same audit, staleness, supersede, and continuation
  semantics as the other interactions" on a new card.

## When NOT to use

- Adding fields to an existing interaction kind that does not need a new
  payload schema. Patch the existing validators/UI in place instead.
- Changing how Paperclip agents *call* interactions. Update `skills/paperclip`
  or `references/api-reference.md`; that is agent guidance, not card work.
- Building a non-thread UI (issue detail sidebar, project board widget, etc.).
  Those have their own component conventions.

## Mental model

Every issue-thread interaction has five moving parts:

The rest: https://github.com/paperclipai/paperclip/blob/HEAD/.agents/skills/create-issue-interaction-ui/SKILL.md