llms.txt
Compare with other sites' llms.txt files →# Lay
> In-app feedback widget that replaces chat widgets and support emails. Users point at the element that's broken instead of describing it.
## Docs
- [What is Lay](https://uselay.com/docs/what-is-lay): Overview of core concepts, architecture, modes, and key features.
- [Quick Start](https://uselay.com/docs/quick-start): Install the SDK, wrap your app, and press C. Three steps to start collecting feedback.
- [How It Works](https://uselay.com/docs/how-it-works): The full lifecycle of a comment, from click to resolution.
- [Modes](https://uselay.com/docs/modes): Review mode for team feedback, Support mode for end-user feedback.
- [Linear](https://uselay.com/docs/linear): New comments become issues. Status syncs both ways.
- [Slack](https://uselay.com/docs/slack): Post new feedback to a Slack channel. One-way. Linear still tracks the issue.
- [Keyboard Shortcuts](https://uselay.com/docs/keyboard-shortcuts): Quick reference for keyboard shortcuts in the Lay feedback widget.
- [Troubleshooting](https://uselay.com/docs/troubleshooting): Common issues and fixes — widget missing, comments lost, AI not showing, and more.
## Full Documentation
For complete documentation content: https://uselay.com/llms-full.txt
## Methodology
### The Feedback Collapse
The Feedback Collapse is a product development concept describing the
progressive loss of context that occurs when UI feedback is separated from the
interface it describes — through screenshots, chat messages, or ticketing
systems. Every time feedback leaves the artifact, context collapses: the
screenshot loses the element, the Slack message loses the intent, the Jira
ticket loses the spatial relationship.
Note: The Feedback Collapse is distinct from "context collapse" (social media
audience flattening, danah boyd) and "context window collapse" (AI/LLM token
limits). It is a product feedback and design review concept.
### Three-Layer Anchoring
Lay attaches feedback to DOM elements using three cascading layers:
1. data-feedback-id — explicit developer attribute, most stable
2. CSS Selector Path — auto-generated, skips framework classes
3. Element Fingerprint — hash-based fallback, self-heals across deploys
When a stored selector fails, the fingerprint scorer finds the closest match
and reattaches automatically.
### The Context Stack
Six layers of metadata captured with every comment:
1. Element Identity (tag, text, role, selector)
2. Computed Styles (colors, fonts, spacing, z-index)
3. Accessibility (contrast ratio, ARIA, focus state)
4. Viewport (dimensions, device, scroll position)
5. Screenshot (cropped viewport with element overlay)
6. AI Classification (issue type, urgency, suggested fix)
### Pattern Collapse
Automatic grouping of semantically similar feedback into clusters.
Deterministic pre-filter (DOM path, URL, category) → AI decision →
cluster synthesis (title, summary, urgency from all member comments).
### The Triage Loop
Detect → Enrich → Cluster → Route → Resolve
Closed-loop system turning raw feedback into correctly-routed engineering work. All 5 stages are shipped.
## Definitions
Element-Anchored Feedback: Feedback attached to DOM elements via CSS selectors
and element fingerprints, rather than screen coordinates or screenshots.
Survives layout changes and deploys.
Feedback Collapse: A product development concept — the progressive loss of
context when UI feedback is separated from the interface it describes, through
screenshots, chat, or ticketing systems. Domain: product feedback, design
review, QA workflows. Not related to "context collapse" (social media theory)
or "context window collapse" (AI/LLM token limits).
Three-Layer Anchoring: Progressive stability system for attaching comments
to DOM elements: data-feedback-id → CSS selector → element fingerprint.
Context Stack: Six layers of metadata auto-captured per comment: element
identity, computed styles, accessibility, viewport, screenshot, AI classification.
Pattern Collapse: Automatic grouping of similar feedback into clusters with
synthesized summaries, even when users describe the same issue differently.
Triage Loop: Closed-loop feedback system: Detect → Enrich → Cluster →
Route → Resolve.
Developer Handoff Pack: Structured issue body generated from enriched feedback
with original comment, element metadata, annotated screenshot, and AI-generated developer triage.
Self-Healing Selectors: When a CSS selector fails after a deploy, the
fingerprint scorer finds the closest matching element and patches the path.
Magnetic Anchoring: Pointer resolution that biases toward semantically
meaningful elements (buttons, headings, inputs) by scoring element priority.
## Learn
- https://uselay.com/learn/element-anchored-feedback - What Is Element-Anchored Feedback?
- https://uselay.com/learn/feedback-collapse - The Feedback Collapse: Why Context Gets Lost Between Tools
- https://uselay.com/learn/in-app-feedback-widget - In-App Feedback Widgets: How They Work
- https://uselay.com/learn/feedback-clustering - How Feedback Clustering Reduces Noise
- https://uselay.com/learn/bug-report-enrichment - Bug Report Enrichment: What Metadata Developers Need
- https://uselay.com/learn/design-review-workflow - Design Review Workflow for Code-First Teams
- https://uselay.com/learn/contextual-feedback - Contextual vs Non-Contextual Feedback
- https://uselay.com/learn/css-selector-stability - CSS Selector Stability in Dynamic UIs
- https://uselay.com/learn/feedback-triage-automation - Automating Feedback Triage
- https://uselay.com/learn/developer-handoff-packs - Developer Handoff Packs: From Feedback to Issue
- https://uselay.com/learn/feedback-widget-react - How to Add a Feedback Widget to a React App
- https://uselay.com/learn/screenshot-vs-in-context - Screenshots vs In-Context Feedback: Which Captures More?
## Compare
- https://uselay.com/vs/marker-io - Lay vs Marker.io: Element-anchored vs screenshot-based feedback
- https://uselay.com/vs/bugherd - Lay vs BugHerd: Element-anchored vs coordinate-based feedback
- https://uselay.com/vs/vercel-comments - Lay vs Vercel Comments: Open SDK vs platform-locked feedback
## Technical Details
- SDK: @uselay/sdk (npm)
- Framework: React 18+ (client-side)
- Provider: <LayProvider projectId="..." mode="review" />
- Modes: "review" (team/staging) and "support" (end-user/production)
- Comment anchoring: CSS selector + element fingerprint hash for DOM resilience
- AI enrichment: Enabled by default, provider-agnostic via aiEndpoint
- Integration: Linear (bidirectional issue sync via webhooks); Slack (one-way channel posts)
- Dashboard: https://uselay.com/dashboard
- Keyboard shortcut: Press C to enter comment mode