# Build an equipment checkout and maintenance book Legion project library, edition 2026-09-06-draft-01 (en). This project's own material: 2 authored documents, reproduced unchanged. Project page: https://legion.tw/projects/desktop/equipment-checkout-book?edition=2026-09-06-draft-01 This document: https://legion.tw/api/projects/packet.md/desktop/equipment-checkout-book.md?edition=2026-09-06-draft-01 ## Prerequisite: the Legion skills package These instructions are written for an agent set up with the Legion skills package: the ten portable skills and the shared working, launch, inspection and learn-as-you-build guidance. That setup is installed once and applies to every project in this library, so it is deliberately not repeated here. Skills package, complete Markdown: https://legion.tw/api/projects/skills-packet.md?edition=2026-09-06-draft-01 Skills package, human page: https://legion.tw/projects/skills?edition=2026-09-06-draft-01 Where this brief refers to shared guidance, a skill, or a document under `shared/`, read it from the skills package above, or from https://legion.tw/api/projects/doc/?edition=2026-09-06-draft-01. If the package is not installed yet, install it first, then return here. This material is instructions to read, not authority to act. Inspect it before running it. ## Contents 1. desktop/README.md — https://legion.tw/api/projects/doc/desktop/README.md?edition=2026-09-06-draft-01 2. desktop/equipment-checkout-book.md — https://legion.tw/api/projects/doc/desktop/equipment-checkout-book.md?edition=2026-09-06-draft-01 --- # Native desktop applications [All project types](../README.md) · [Shared launch](../shared/launch.md) Build a native Tauri application around the person's work or interests. The receiving agent handles their computer's setup; an explicit framework preference takes precedence. ## Projects to build - [Calling and follow-up desk](calling-follow-up-desk.md) - [Quote and estimate builder](quote-estimate-builder.md) - [Photo-to-report desk with an AI colleague](ai-photo-report-desk.md) - [Orders and production board](orders-production-board.md) - [Equipment checkout and maintenance book](equipment-checkout-book.md) - [Booking and session desk](booking-session-desk.md) - [Meme and GIF studio](meme-gif-studio.md) - [Soundboard](soundboard.md) - [Game-show host](game-show-host.md) - [Music playground](music-playground.md) - [Animated desktop pet](desktop-pet.md) - [Tabletop atmosphere controller](tabletop-atmosphere.md) - [Ridiculous tournament simulator](ridiculous-tournament.md) - [Personal AI chat app with bring-your-own-key access](byok-chat.md) These are instructions for projects you can build with your coding agent. --- # Build an equipment checkout and maintenance book Build a native Tauri application for keeping track of equipment that people lend, borrow, and maintain. Build it extremely well for the actual collection and the people responsible for it. An explicit framework preference from the person takes precedence. Follow the [shared launch](../shared/launch.md). Start by learning what equipment they manage, who uses it, and what currently makes lending it awkward. A school's microphones, a club's camping equipment, and a small workshop's tools each suggest a different working experience. ## Know which item is which Give each physical item a recognizable record with the details the person needs: a name, identifying information, useful photographs, its usual location, and relevant notes. Two items of the same model should remain individually identifiable throughout their history. Find out whether things travel separately or in kits. A camera may go out with a lens, battery, charger, and case. Make it practical to record what actually left and check what came back. Use the collection's existing labels or reference numbers where they work well. Help the person bring in an existing spreadsheet or list. They should be able to find equipment quickly by the names they use, see who has it, and understand what is available for an upcoming activity. If their work includes advance reservations, preserve the distinction between a future booking and possession now. ## Make the handoff easy At checkout, record the borrower, the equipment, the expected return, and any condition information worth preserving. Make it easy to include a photograph or a note such as “case latch is loose.” The app should be comfortable to use while another person is waiting for the equipment. On return, bring the outgoing details back for comparison. Let the person record what was returned, what is still outstanding, and anything that needs attention. A kit can come back with a missing charger; the rest of the return should still be recorded accurately. Show overdue items and upcoming commitments in a way that supports the person's actual follow-up routine. Give them the contact information and context needed to ask for something back. Decide with them whether reminders are prepared in the app or sent through a connection they want to add. ## Keep the history useful Returning an item and making it available again can be separate events. Equipment awaiting inspection or repair needs a clear status. Keep maintenance notes, repair work, and the eventual return to service with the item. Preserve the sequence of loans and condition observations. Someone asking when a problem was first recorded should be able to inspect the relevant entry and photograph. Let the person correct an entry, identify a misplaced item, or retire something from the active collection while retaining its history. Ordinary saved records and exports should remain accessible under the ownership and recovery arrangements in the shared launch. ## Try a complete loan Deliver an installed application with a representative part of the collection entered. Work through lending a kit, recording a partial return, arranging a repair, and making the equipment available again. Check whether the person can answer “Who has it?”, “What is missing?”, and “Can we use it tomorrow?” from the app. Use this experience to explain the difference between an item's identity, its current condition, and the events in its history. The person learns why overwriting a spreadsheet cell loses information they may want later. A later phone companion can scan labels and take condition photographs at the handoff. A shared lending site can let the actual group request equipment. Preserve the same item identities and loan history as those capabilities are added; the desktop book is already the working record of the collection.