> ## Documentation Index > Fetch the complete documentation index at: https://helloluciallc.com/llms.txt > Use this file to discover all available pages before exploring further. # Tips and guides > The six in-app tips that teach Fieldwork at its first real moments, how each one dismisses, and how to replay them. Fieldwork teaches itself in the app, one small tip at a time, instead of through a guide you read somewhere else. The founder set the shape on 2026-08-21: “a small batch of simple onboarding-flow fieldwork app suggestions (like all apps have), that are easily closed out.” ## The tip design On 2026-08-22 the founder ruled the design for every tip in the app, and likely the whole platform (Tooltip guides in Fieldwork App, FILD-100): > Tipkit iOS clone. That's what we use for our tooltips/design/guides throughout the entire app > (and probably the entire platform). Literally copy/mimic/steal the exact designs… Same > concept. Similar sizes. Use current structure. No spike. What that means on screen: * **A frosted-glass card** with Lucia's round headshot, a bold title over a grey body line, and a ✕ in the top-right corner. No numbering, no “Next”, no “Skip”. * **A small notch** that points at the words it teaches, not at the middle of a wide row. * **It floats; it never pushes.** The card is placed off the element it points at and never covers that element. Nothing underneath moves when it appears or leaves. * **One tip on screen at a time.** The turn goes to the first tip you have not seen whose anchor is actually visible. Opening the drawer over an undismissed composer tip retracts it and hands the turn to the drawer's tip; closing the drawer hands it back. * **The clean home stays clean.** No tip decorates the empty chat on launch, and no tip fights the cold-open Lucia Orbit. ## The six tips Read from the app's tip layer at `main@692a71c`. Titles and bodies are the app's own words. | Where it appears | Title | Body | | --------------------------------------------------------------------------- | -------------------------- | -------------------------------------------------------------------------------------------------- | | The composer, on the empty chat | **Lucia is here to help** | Tell her what’s going on and she will draft an issue for your review. | | The drawer's **Drafts** row | **Your drafts live here** | Pick up saved drafts and finish them when you’re ready. | | The drawer's **Log Issues Manually** row, after the Drafts tip is dismissed | **Log issues manually** | If you don’t want to chat with Lucia to log a maintenance issue, you can simply input it yourself. | | The **Log Issues Manually** page, on the first field | **File it yourself** | Fill in the details and submit — no chat needed. | | A draft card in the chat | **Review before it goes** | Check the details, add a photo, then submit. | | A submitted item | **Your manager can reply** | The item lights up when they do. Tap it to answer. | The composer tip is a small pulsing chip inside the composer that opens on tap, never on hover. The other five hang off the element they teach. The manual page's tip sits over the page header and points at “What's the issue?”; it only shows on a fresh, empty form that did not come from a chat. ## How a tip goes away * **Tap the ✕.** The tip collapses back toward its notch. It counts as seen and does not return on its own. * **Scroll the page.** On a scrollable page such as Log Issues Manually, a real finger scroll dismisses the tip quietly. The founder's ruling of 2026-08-28 (Tips dismiss on scroll, FILD-127): scrolling is engagement, the tip's job is done. Scrolls the app performs itself, such as following the transcript or making room for the keyboard, never dismiss a tip. * **Start using what it points at.** Focusing the field under a tip dismisses it the same way; the founder ratified engagement dismissal on the 2026-08-29 testing pass. Seen-state is kept per signed-in account on the device. A dismissed tip stays dismissed on that device; the app does not claim a dismissal it could not store. ## Replay the guides The drawer's **Replay the guides** row (“Show the Fieldwork tips again.”) forgets every tip's seen-state for the current account, so each tip presents again at its next first moment. It is a plain reset, not a tour: the tips come back one at a time, in the same order, at the same places. ## Learn about Lucia Fieldwork Beside it, the drawer's **Learn about Lucia Fieldwork** row (“A short tour of what the app does.”) opens a short in-app sheet that walks through what the app is for. It is separate from the tips and does not change tip state. ## Status The tip layer is on the served build with all six tips enabled. Its parent record (Tooltip guides in Fieldwork App, FILD-100) is **Finalizing**, and the manual page's tip closed as Completed on 2026-09-08 (Manual page gets a tip, FILD-108). Anything beyond these six, or any platform-wide adoption outside Fieldwork, is not claimed here. ## See also * [Log and track issues](/fieldwork/using-fieldwork/logging-and-tracking-issues) * [Log Issues Manually](/fieldwork/using-fieldwork/manual-logging) * [Messages and replies](/fieldwork/using-fieldwork/messages-and-replies) ## Verification basis Verified on **September 10, 2026** against the app source at `692a71c`, the build the served bundle carried on that date, and the founder's rulings on the cited records. Copy is quoted from the source; behavior claims are bounded to that build.