Prompt field, context
Prompt field, context is a Text Areas block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
A prompt where you can see everything the model will read, and how full its window is
Anatomy
The strip lists the context as white chips with their weight (“DOCX · 6K”) and a ring at its end · “9% of 200K” that drains when a bigger model is picked and turns amber past 80% · removing a chip gives its weight back · the prompt set large in the white box
In the Orvain Library
Get Prompt field, context for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Text Areas
What’s inside
05parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- The strip lists the contextas white chips with their weight (“DOCX
- 6K”) and a ring at its end
- “9% of 200K”that drains when a bigger model is picked and turns amber past 80%
- Removing a chip gives its weight back
- The prompt set largein the white box
Responsive behaviour
780 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Text Areas earns its place
Reach for Text Areas
- Input that might be one line or twenty: comments, replies, messages
- Composers that carry attachment, model or mode controls beneath the field
- Issue and task editors that need light formatting and nothing more
- Anywhere people paste several paragraphs at once
Reach for something else
- A short single value like a name or a subject: a one-line input keeps the form's rhythm
- Documents with headings, tables and images. That is a rich editor's job
- Several values typed into one box: a tag input keeps them separable afterwards
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Prompt field, context” block to this page: the strip lists the context as white chips with their weight (“DOCX, 6K”) and a ring at its end, “9% of 200K” that drains when a bigger model is picked and turns amber past 80%, removing a chip gives its weight back, the prompt set large in the white box.
Questions about Prompt field, context.
What is the Prompt field, context block?
Prompt field, context is a Text Areas block from Orvain UI, built for React and Vue with a matching Figma frame. Best for a prompt where you can see everything the model will read, and how full its window is.
What is the Prompt field, context block made of?
5 parts: the strip lists the context as white chips with their weight (“DOCX; 6K”) and a ring at its end; “9% of 200K” that drains when a bigger model is picked and turns amber past 80%; removing a chip gives its weight back; and the prompt set large in the white box. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Prompt field, context block responsive?
Yes. It is drawn at 780px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Prompt field, context block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Prompt field, context block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Prompt field, context block to this page.”
When should I not use a Text Areas block?
A short single value like a name or a subject: a one-line input keeps the form's rhythm.
More Text Areas blocks
All Text AreasPremium components,
free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Orvain MCPPrompt field, context
Prompt field, context is a Text Areas block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
A prompt where you can see everything the model will read, and how full its window is
Anatomy
The strip lists the context as white chips with their weight (“DOCX · 6K”) and a ring at its end · “9% of 200K” that drains when a bigger model is picked and turns amber past 80% · removing a chip gives its weight back · the prompt set large in the white box
In the Orvain Library
Get Prompt field, context for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Text Areas
What’s inside
05parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- The strip lists the contextas white chips with their weight (“DOCX
- 6K”) and a ring at its end
- “9% of 200K”that drains when a bigger model is picked and turns amber past 80%
- Removing a chip gives its weight back
- The prompt set largein the white box
Responsive behaviour
780 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Text Areas earns its place
Reach for Text Areas
- Input that might be one line or twenty: comments, replies, messages
- Composers that carry attachment, model or mode controls beneath the field
- Issue and task editors that need light formatting and nothing more
- Anywhere people paste several paragraphs at once
Reach for something else
- A short single value like a name or a subject: a one-line input keeps the form's rhythm
- Documents with headings, tables and images. That is a rich editor's job
- Several values typed into one box: a tag input keeps them separable afterwards
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Prompt field, context” block to this page: the strip lists the context as white chips with their weight (“DOCX, 6K”) and a ring at its end, “9% of 200K” that drains when a bigger model is picked and turns amber past 80%, removing a chip gives its weight back, the prompt set large in the white box.
Questions about Prompt field, context.
What is the Prompt field, context block?
Prompt field, context is a Text Areas block from Orvain UI, built for React and Vue with a matching Figma frame. Best for a prompt where you can see everything the model will read, and how full its window is.
What is the Prompt field, context block made of?
5 parts: the strip lists the context as white chips with their weight (“DOCX; 6K”) and a ring at its end; “9% of 200K” that drains when a bigger model is picked and turns amber past 80%; removing a chip gives its weight back; and the prompt set large in the white box. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Prompt field, context block responsive?
Yes. It is drawn at 780px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Prompt field, context block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Prompt field, context block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Prompt field, context block to this page.”
When should I not use a Text Areas block?
A short single value like a name or a subject: a one-line input keeps the form's rhythm.
More Text Areas blocks
All Text AreasPremium components, free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
