Maintenance work orders with parts stock, built by Claude Code on Elements
Work orders on a live status board, preventive schedules that open jobs when due, phone timers for technicians, parts stock with a reorder list and a downtime dashboard.
How it's built
Wrenchloft needed three kinds of accounts, a board and technician timers that update on every screen, stock that drops as parts are used, and preventive work that opens itself on schedule. Each of those is a part of Elements, so the agent spent its 23 minutes on the maintenance shop itself.
- A live board and timers. Work orders, notes, photos, part uses and parts are LiveTables. A manager drags a card to On hold and the technician's phone shows it at once; a technician presses Start and the card on the manager's board starts its clock.
- Stock that stays right. Using a part is an
@rpccall that locks the part's row, lowers its stock and records the use in one transaction, so the count stays exact when two technicians reach for the same part. The parts page and its reorder list update as the count changes. - Preventive work on a schedule. A one-line cron schedule runs a job every 15 minutes that opens a work order a week before each schedule comes due, then rolls the schedule forward.
- Photos from the floor. Technicians and requesters attach photos straight from a phone camera through a server call, stored in Postgres and served by the app's own route.
- Roles and sessions. One guard on the signed-in user's role sends managers, technicians and requesters to their own pages and keeps every server call to the right people.
- Data from SQL files. Migrations define the plant and seed six accounts, twelve assets across two buildings, nine preventive schedules, fourteen parts and thirty-six work orders with their parts and notes. The project server applied each one as soon as it was saved.
Why Elements
Elements is an integrated full-stack app framework and a project server. The project server checks the agent's work as it builds: it type-checks the server and browser code, analyzes the program, applies migrations and runs the tests, then reports the results to the agent. A security mistake, such as calling a server-only function from the browser, is a compile error. The agent reads the report and fixes its own mistakes before it tells you a feature is done. The same checks run on every feature you ask for next.
Run it yourself
- 1 Sign up
Already have an account? Sign in
- 2 Install and run the demo One prompt to paste into your agent.
The prompt
What Claude was given to build this app.
Build a maintenance work order app named wrenchloft for a manufacturing plant. Three kinds of accounts: manager, technician and requester. Requesters report problems, technicians do the work, and managers plan and assign it. - Assets: name, building, production line, category, and a full work history. - Work orders: asset, title, description, priority, status (requested, scheduled, in progress, on hold, done), assigned technician, due date, photos, parts used and time spent. - Preventive maintenance: a schedule per asset, every so many days or weeks, that creates work orders automatically when they come due. - A board with a column per status that managers drag work orders across, and a week calendar of scheduled work. - Technician view for a phone: today's work orders, start and finish with a timer, and notes, photos and parts added on the spot. - Parts inventory with stock counts. Using a part lowers its stock, and a low stock list shows what to reorder. - Dashboard: open work orders by priority, overdue count, preventive work done on time this month, and downtime by asset. Seed one manager, three technicians, two requesters, twelve assets across two buildings, preventive schedules and twenty work orders. Show the seeded logins on the sign-in page. The board, technician timers and stock counts update in real time.