> For the complete documentation index, see [llms.txt](https://rocketshiftstudio-assets.gitbook.io/clipper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rocketshiftstudio-assets.gitbook.io/clipper/introduction.md).

# Introduction

Clipper is a clipboard utility for organizing & easy access to clips while making copy/paste actions inside the Unity game engine's editor.

{% hint style="info" %}
"Clip" Definition:  A "Clip" refers to a piece/block of data containing serialized information from a copied object. This includes essential creation metadata like the source path, source type, creation date, main object data, etc. All of which is presented in the clipper window for visualization.
{% endhint %}

## Overview

In unity copying/pasting components or objects or their properties is a common practice. However, handling each copy/paste separately and tracking them is not possible. 

Not just that accidental multiple clicks on "copy" can replace recent copies, wasting time and making data reproduction extra hassle. Such as while spending hours tweaking something large such as a car controller to get perfect values in test play and then copying that value for applying it in the source component but somehow you click copy again instead of paste. In solution to these Clipper does a great job by keeping track of all clips and organizing them for the best use of it. It can handle things that Unity's default copy/paste can't.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://rocketshiftstudio-assets.gitbook.io/clipper/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.