How do file and database mentions target an edit?

A direct answer, the limits that matter, and a practical way to check the workflow.

Direct answer

Typing @ in Uvilno's builder opens page, file and collection suggestions. Choose references such as @index.html or @db:tasks, or use an inspector-provided @selected-element. These references guide private source retrieval for a focused edit; they do not expose locked code or guarantee a fixed completion time.

45-word answer · Reviewed 2026-10-27

Use a mention when the location matters: a tasks filter belongs to the tasks controller, while a shared navigation change may affect several pages. The menu supports keyboard navigation and selected references remain removable pills, so review them before submitting.

The server validates each reference against the current owned version. An arbitrary path pasted into the message is not authority to load private storage or another customer's project. Preserve an explicit description of the desired behavior alongside the reference; a filename alone is not an edit specification.

What to verify.

Compare products
Documented behavior and checks the reader can perform
AreaDocumented behaviorYour verification
SelectionThe composer suggests real owned metadata.Type @ and use arrow keys, Enter and Escape.
PrivacyLocked projects receive paths and labels, not source text.Review available context without opening a raw source bundle.
ScopeReferences guide affected-file retrieval and checks.Inspect the saved change summary for unrelated modifications.

Drag the slider, use the arrows, or scroll within the table.

Try the workflow yourself.

Use this checklist in your own disposable project. These marks record your review; they do not run tests or certify an application.

0 of 3 review steps marked by you.

Read the editable test brief

In @db:tasks, refine the status filter so it preserves the current search query and updates the list and count together. Use the relevant page/controller context, retain all saved records and unrelated routes, handle loading and errors, and verify the requested behavior rather than rewriting the application.

Preparing a brief does not start generation. Review and send it explicitly; builds use the normal allowance, and source access requires entitlement.

Sources and scope.

Published by the Uvilno editorial team on . This is product documentation and editorial guidance, not an independent ranking or a promise that every application will pass. Vendor plans can change; official sources establish their own terms.

Does opening this test use my allowance?

Preparing the test brief does not invoke a model or create a billable build. Review the draft and explicitly send it to generate; normal usage and source entitlement rules apply.

Check the architecture. Compare the tradeoffs.

Follow the data model, account boundary and source handoff before choosing a builder.

Compare builders

Plan a full-stack app

Review the evidence

Read the public Markdown reference