skills.rest
paperclipai
paperclipaiOFFICIAL
Explore all skills by this author →
Website𝕏@paperclipingGitHub

create-issue-interaction-ui

Implement new issue-thread interaction types within the Paperclip codebase using standardized patterns.

79.8k|14.6k|Updated Mar 2, 2026
Search Tags:#zod#typeScript# orchestration#UI-development#reAct#Paperclip
One-click install
npx skills add https://github.com/paperclipai/paperclip --skill create-issue-interaction-ui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-issue-interaction-ui
Source: https://github.com/paperclipai/paperclip/tree/main/.agents/skills/create-issue-interaction-ui
Command: npx skills add https://github.com/paperclipai/paperclip --skill create-issue-interaction-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of extending Paperclip's issue-thread interaction system, ensuring that new UI components and backend logic maintain consistency with existing interaction kinds.

Core Features & Use Cases

  • Standardized Implementation: Provides a structured roadmap for adding new interaction kinds (e.g., custom cards, structured forms) across the shared, server, and UI layers.
  • Contract Enforcement: Guides the developer through Zod schema validation, type definitions, and idempotency requirements to prevent system drift.
  • Use Case: A developer needs to add a new 'structured rating' card to issue threads; this Skill ensures the card integrates correctly with existing staleness, supersede, and continuation logic.

Quick Start

Follow the step-by-step guide in the SKILL.md file to implement your new interaction kind starting with the shared contract layer.

Frequently Asked Questions about create-issue-interaction-ui

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

FAQPage Schema
How do I add a new interaction kind to Paperclip?▼

Follow the four-layer implementation process: define the shared contract, implement server-side services and routes, wire the UI card components, and update CLI/SDK helpers.

When should I use this skill instead of patching existing interactions?▼

Use this skill when introducing a new interaction kind with a distinct payload shape or resolution outcome. If you are only adding fields to an existing interaction, patch the existing validators and UI instead.

Does this skill support non-thread UI components?▼

No, this skill is specifically for issue-thread interactions. Non-thread UI components like issue detail sidebars or project board widgets follow different component conventions.

Why must I use the existing staleness and supersede logic?▼

Reusing existing helpers ensures consistent behavior across all interaction kinds. Implementing bespoke logic for these features leads to silent behavioral drift and maintenance debt.

What is the purpose of the shared contract layer?▼

The shared contract layer defines the kind constant, payload interfaces, and Zod validators. It is the foundation that all subsequent server and UI layers rely on for type safety.

Related Skills

Explore More Software Engineering Skills→
discord-phpdiscord-php
1.1k

interaction-flow-keeper

Maintain typed Discord interaction pipelines with cached routing and response builders.

Official
Advanced
jangirsamarthjangirsamarth

paperclip

Manage business tasks and delegate work via the Paperclip control plane API.

Community
Advanced
vinhnguyenn020325-cmdvinhnguyenn020325-cmd

benchmark-e2e

Run end-to-end benchmark tests for Vercel plugins and generate performance reports.

Community
Advanced
1k-off1k-off
1

cue-kind-definition

Build valid grafana-app-sdk CUE kind definitions with three-layer anatomy.

Community
Advanced