# Build a booking and session desk 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/booking-session-desk?edition=2026-09-06-draft-01 This document: https://legion.tw/api/projects/packet.md/desktop/booking-session-desk.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/booking-session-desk.md — https://legion.tw/api/projects/doc/desktop/booking-session-desk.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 a booking and session desk Build a native Tauri application that brings appointments, preparation, session notes, and payment records together. Build it extremely well around the person's actual sessions. Use another framework if they have an explicit preference, and follow the [shared launch](../shared/launch.md) for setup and working practice. ## Start with what happens at the appointment Find out whom the person meets and what the meeting involves. A tutor prepares teaching material and follows a learner's progress. A repair technician needs the item's problem, access arrangements, parts, and work completed. Choose the person's real activity and give it an appropriate application. For someone trying the project without an existing practice, use a private tutor as the example. The tutor should be able to open tomorrow's lesson, see what happened last time, prepare material, and know what to bring. After the lesson, they can record what the student understood and what deserves another look. Learn which people belong to the work. The student attending a lesson, the parent arranging it, and the person paying can be different people. Make those relationships clear when they matter to the actual practice. ## Make preparation and notes useful Give appointments a calendar view and enough room for the work associated with them. Support substantial editable notes and relevant files or links. A tutor may want a full lesson plan, a passage to discuss, and notes about particular mistakes. Let them work with that material comfortably while preparing or teaching. Keep planned work distinguishable from what actually happened. A lesson may spend forty minutes on an unexpected difficulty and leave most of the plan unused. The tutor should be able to record that outcome and carry suitable material into the next session. Make the participant's history easy to consult from the current appointment. The person should find the relevant previous notes without searching through unrelated meetings. Reusable material can save preparation time while each session retains its own plan and record. ## Let appointments change Support creating, rescheduling, cancelling, and recording the outcome of appointments. Changing the time should retain the associated preparation and contact information. If there is a recurring series, make the difference between changing one appointment and changing the series understandable. Show conflicts in the terms that matter to the person, including travel or preparation time when their activity requires it. Give them a practical way to decide what fits. An appointment whose time has passed still needs an accurate outcome: held, cancelled, missed, or another status their practice uses. Keep payment records connected to the appropriate work. Find out whether the person charges per session, takes a deposit, or sells a block of sessions. Apply their rules for cancellations and credits, and make any remaining balance understandable. Record actual payments separately from amounts expected. ## Use it before and after a session Deliver an installed application with persistent records and the ownership and recovery arrangements from the shared launch. Give the person useful exports when they need to share a schedule, session summary, or payment statement, choosing the relevant information for that recipient. Work through a representative sequence together: book a session, prepare it, move its time, record what happened, and arrange the next one. Include a payment example that matches their practice. Judge whether the application makes preparation easier and whether the next session begins with the information they need. Explain how an appointment, a plan, an actual meeting, and a payment relate. The person should understand why changing the calendar need not scatter their notes or lose track of money already paid. A later phone companion can show the next appointment and accept notes immediately afterward. Shared scheduling can be added where it helps the people involved. Preserve the session history and teaching or working material as the application grows.