# Prompt input

> Ask Kwark to find, measure or carry something in the project, with chips that show exactly what it will look at.

Source: https://kwark.space/designSystem/components/prompt-input

## Usage

### What it is
A box for asking Kwark to work on the project’s own material: find (*every scene where the ZIPPO appears*), measure (*how long does Act 2 run*), carry (*put Scene 12’s cast on the Day 3 call sheet*) or convert. Chips above it show what it will look at, by Kwark’s names; it starts with only what is on screen. The foot says where it runs and that nothing changes.

### What it answers, and what it declines
Results come back as found items or proposals ([Suggestion panel](https://kwark.space/designSystem/components/suggestion-panel.md), [AI result review](https://kwark.space/designSystem/components/ai-review.md)), never as edits. A request to write, rewrite or judge the story (*make Mira’s line punchier*, *is Act 2 too slow?*) gets one calm sentence: *Kwark does not write or judge the story. It can find, measure, move or convert your own words.* (Decision 0002.)

### When to use
- Inside a module, about that module’s material and what it draws on.

### When not to use
- As a chat about anything, or a writing partner.
- To look at the whole screenplay or another person’s private research by default: those are chips the person adds.

### Writing
- Placeholder: *Find, measure or carry something in Blank Pages…*
- The primary names the action the box will take: **Find**, **Measure**, **Carry**.

## Style

### Anatomy

1. **Box**: `--k-surface`, 1px `--k-line`, 10px corners, 8px 12px padding; focus shows on the box with `--k-accent-soft`.
2. **Looks at row**: 12px `--k-text-2` label, then 24px chips: 1px `--k-line`, `--k-raise`, 12px Poppins 500, 14px glyph, a 20px remove button.
3. **Text**: 14px Poppins, two lines growing to eight.
4. **Foot**: 12px `--k-text-2` sentence and the primary.

### Tokens

| Token | Light | Dark |
|---|---|---|
| `--k-surface` | #ffffff | #1a1a1a |
| `--k-raise` | #f1f5f9 | #252525 |
| `--k-line` | #e2e8f0 | rgba(255, 255, 255, .1) |
| `--k-text` | #0f172a | #e3e3e3 |
| `--k-text-2` | #5b6779 | #9ca3af |
| `--k-accent-soft` | #e8b58b | #e8b58b |
| `--k-radius-card` | 10px |  |
| `--k-radius-pill` | 999px |  |
| `--k-fs-body` | 14px |  |
| `--k-fs-meta` | 12px |  |

## Code

### React

Use the HTML below with `kwark.css`. The example shows the markup and styling. Supply any application behavior described on this page.

### HTML and CSS

Works anywhere with `kwark.css`.

```html
<form class="kw-prompt" aria-label="Ask Kwark to find, measure or carry">
  <div class="kw-prompt__context" role="group" aria-label="What it will look at">
    <span class="kw-prompt__label">Looks at</span>
    <span class="kw-prompt__chip"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M15 2H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h12a2 2 0 0 0 2-2V7Z"/><path d="M14 2v4a2 2 0 0 0 2 2h4M10 9H8M16 13H8M16 17H8"/></svg>Act 2<button type="button" aria-label="Stop looking at Act 2"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M18 6 6 18M6 6l12 12"/></svg></button></span>
    <span class="kw-prompt__chip"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M12.6 2.6A2 2 0 0 0 11.2 2H4a2 2 0 0 0-2 2v7.2a2 2 0 0 0 .6 1.4l8.7 8.7a2.4 2.4 0 0 0 3.4 0l6.6-6.6a2.4 2.4 0 0 0 0-3.4z"/><circle cx="7.5" cy="7.5" r=".5"/></svg>Breakdown<button type="button" aria-label="Stop looking at the Breakdown"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M18 6 6 18M6 6l12 12"/></svg></button></span>
    <button class="kw-prompt__add" type="button"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M5 12h14M12 5v14"/></svg>Add</button>
  </div>
  <textarea class="kw-prompt__text" rows="2" aria-label="What to find, measure or carry">Every scene where the ZIPPO appears</textarea>
  <div class="kw-prompt__foot"><span>Runs on this device. Results arrive as a list to check; nothing in the work changes.</span><button class="kw-button kw-button--primary kw-button--sm" type="submit"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M14.5 21.7a.5.5 0 0 0 .9 0l6.5-19a.5.5 0 0 0-.6-.6l-19 6.5a.5.5 0 0 0 0 .9l7.9 3.2a2 2 0 0 1 1.1 1.1z"/><path d="m21.9 2.1-11 11"/></svg> Find</button></div>
</form>
```

## Accessibility

### Keyboard
| Key | Does |
|---|---|
| Enter | Runs it. |
| Shift + Enter | New line. |
| Tab | Chip remove buttons, Add, the text, the primary. |
| Backspace in an empty box | Never removes a chip; removing scope is an explicit button. |

### ARIA
- The chip row is a `role="group"` named *What it will look at*; each remove button names its object.
- Announce the result count politely: *Found in 4 scenes.*

## For agents

### Rules

- **Must** show everything it will look at as named chips before it runs.
- **Never** write, rewrite or judge story in answer; decline in one sentence and say what it can do (Decision 0002).
- **Must** return results as lists or proposals, never as edits.
- **Must** say where it runs, and ask for consent first if anything would leave the device.

### AI readiness test

**Task:** A writer types "rewrite Scene 12 so it's tenser" into the prompt input.

**Give the agent:** This page, Decision 0002, Foundations › AI and authorship.

**Constraint:** Scene 12 is in scope.

**A reliable answer:**
- Declines in one calm sentence without judging the scene
- Offers what it can do (find, measure, move, convert)
- Changes nothing
- Does not send the scene anywhere
