Everything your agent needs to read for this project, on one page.
Free instructions · English
Edition 2026-09-06-draft-01 · 67 projects · 10 skills
The links and downloads keep this version of the instructions, so your agent builds from the same material you inspected.
All project types · Shared launch
Improve the websites the person already uses through an extension in their own browser.
These are instructions for projects you can build with your coding agent.
Build a browser extension that captures useful information from a page and sends it into the person's own desktop application. Build the connection extremely well, from selecting the material through seeing it in the right place in the app. Follow the shared launch.
This is a continuation of an existing application. Good foundations include the calling desk, photo-report desk, and quote builder. Start with the app the person already uses. If they are starting fresh, help them choose and build the relevant foundation first.
Find a real browser-to-application copying task. The person might collect a business's contact information, add a reference photograph to a job, or bring a product's details into an estimate. Learn what needs to travel and where it belongs.
Let the person capture relevant text, details, links, or images from the current page. Provide a useful preview they can correct before saving. Retain the source address and enough context to understand the material later.
Fit the capture to the receiving application. A contact needs the information the calling desk uses. A reference image needs its purpose and the job it belongs to. A product's listed price needs the terms that explain it. Let the person add their own note when that supplies missing context.
Give the person a clear destination, such as a new contact, an existing job, or a particular estimate. Make that choice visible before they send. Preserve the chosen destination while the transfer is handled.
Set up a deliberate, appropriate connection between the extension and the application. Implement the receiving operation in the app so captured material becomes an ordinary record the person can find, edit, and use. Let the application apply its existing rules for identity and saved work.
Show completion when the receiving app has accepted the material, with a useful way to open or find the result. If the connection needs attention, retain the person's capture and make recovery straightforward. When retrying a transfer, recognize a capture already saved and take the person to that record.
Help them handle information already present in the app. They may want to add a source to an existing contact, update a detail, or keep a separate entry. Make that decision understandable using the app's actual records.
Install the extension in the person's browser and configure its connection to the chosen desktop app. Explain the difference between access to selected web pages and access provided by this particular application. The person should understand what information is read, what is transferred, and what action creates the saved record.
Keep page content in its role as source material, including when an AI colleague later reads it inside the app. Preserve the person's own instructions and notes distinctly. Use the existing application's ownership and backup arrangements for the resulting records.
Leave the extension and its local connection understandable enough to update or reconnect after a change. The person can disable the extension and continue using their desktop app normally.
Deliver the working extension and app integration. Capture information from a page the person actually uses, correct a detail, choose its destination, and open the resulting record in the desktop app. Use it in the person's normal workflow and confirm that its source and context are still available.
Explain how two applications can cooperate through an intentional connection. The learner discovers that a repeated copying chore can become a normal operation in software they own. Later capture types can extend this same connection while preserving the app's established records and working habits.
Build a native Tauri application for someone who works through a list of people or businesses by phone. Give them a comfortable place to make calls, record what happened, and keep track of what they promised. Build it extremely well. An explicit framework preference from the person takes precedence over Tauri.
Read this brief and follow the shared launch. Use the person's existing setup and carry the project through an installed application they can use for their next calling session.
Ask what the calls are meant to accomplish and look at a sample of the list they already use. They might arrange visits, confirm bookings, follow up on estimates, or contact members of a club. Find out what they need to know before dialing, what information they collect, and what happens after a successful conversation. Use a fictional sample when their real list is sensitive.
Shape the desk around that job. Someone arranging visits needs contact details, availability, appointment information, and instructions for finding the entrance. Someone following up on estimates needs the estimate and its history. Build a complete working experience for the person's actual purpose, with fields and language they recognize.
The person conducts the calls. Keep the number, the appropriate contact, relevant notes, and the previous conversation easy to see together. Make recording an outcome quick enough to do while the conversation is still fresh. Support notes in the person's own words alongside the information they need to track consistently.
Imagine calling a business, learning that the person you need works afternoons, and agreeing to call back on Thursday. On Thursday, the desk should bring that commitment back with enough context to continue naturally. A later successful call updates the current situation while retaining the earlier attempt. A wrong number, an unanswered call, and a request to stop calling have different consequences; reflect the distinctions the person's work actually uses.
Let them decide whom to call next, see due follow-ups, search for a returning caller, and temporarily leave the list to handle an interruption. Returning to the application should make it easy to resume. Make appointments, promised actions, and completed work distinguishable, including when a previous arrangement changes.
Import the XLSX files they receive and help them match the existing columns to the application's information. Show a useful preview so they can recognize their records and notice a mismatched column before accepting an import. Keep details such as phone numbers and reference codes intact.
Give repeat imports a clear meaning: adding new work, updating an existing list, or starting a separate batch. Preserve each record's identity and call history as the list evolves. The person can correct a match when two entries look similar.
Export the information back to an ordinary XLSX file in a form useful to the person receiving it. Retain the extra information the caller collected. A colleague who still works in Excel should be able to understand the result. Keep saved work and recoverable backups under the person's control, using the ownership guidance in the shared launch.
Give the interface enough information to support a conversation without making the person hunt through a dashboard. Consider readable notes, keyboard use, and the ability to move between the day's work and one contact's history. Let the real session determine which actions deserve immediate access.
Complete an end-to-end rehearsal with representative records: import a list, record several different outcomes, change an arrangement, return to a due callback, and export the updated work. Help the person judge whether the desk reduces their effort and preserves everything they need after an interruption.
Through that experience, explain how records, history, and future commitments differ. They should leave knowing how to ask for a change in their working process, even if they never learn the names of the underlying code.
A later project can give this desk an AI colleague, a phone companion, or shared work between callers. Preserve the established records and history as those capabilities arrive. This first application should already make a day's calling substantially better.
Build a native desktop application with Tauri for turning photographs and field notes into reports. Build it extremely well, as a shared workplace where you and the person can organize the material, discuss what it shows, and prepare something useful to send. Tauri is the default; an explicit framework preference from the person takes precedence.
Read this brief and follow the shared launch, which supplies setup, working skills, ownership, continuity, and learning guidance. Then build this project, carrying forward any setup the person already has.
Someone returns from a visit with photographs and observations. They need to identify the useful images, explain them, and assemble a report for a particular recipient. The work might involve documenting repairs, completed work, a property, or a delivery. Learn which reports the person makes and look at an example they choose to share. Use that understanding to shape the application.
Someone reading the report may need to understand a problem, confirm completed work, or decide what happens next. Let that purpose determine the arrangement of photographs and explanation. Start with a complete example report whose layout the person can change as they discover what works.
Photographs and notes belong to a job. The person can browse the images at useful sizes, compare similar shots, choose what to include, and arrange sections and captions in an editable report. Keep the original material available as the report develops. They can save their work, return to it, and export a readable document for the recipient in the format the job calls for.
Give particular care to the movement between examining a photograph and working on its place in the report. The person should be able to see the relevant image while deciding what to say about it. The report's final layout should support the recipient's understanding of the work.
Build yourself first-class access to the job's photographs, notes, and current report, together with useful tools for operating them. Use your existing coding-agent installation, sign-in, and model access for this collaboration. They can discuss the work with you in their usual conversation and see your changes in the application.
Provide an appropriate local integration, such as MCP tools, so you can compare images, group related material, draft captions, choose a useful sequence, and assemble the actual report in the editor. Make that connection part of the delivered application.
Make the person's current job, report, and image selection available through that connection. A reference to “this photograph” should have the same meaning for both of you. Your changes should appear in their working view, and your next action should use the current report, including their direct edits.
For example, the person might say, “These three show the same damaged hinge. Use the clearest one and include my note about replacing it.” You inspect the images, select one, and make that change in the report. The person can then edit the caption themselves.
Treat the photographs and field observations as the basis for factual descriptions. Keep visible evidence distinguishable from the person's explanation of what happened. Ask about a genuinely unclear image or suggest wording that accurately reflects the information available. Let ordinary discussion, direct editing, and your actions work together naturally, with useful ways to inspect and undo changes.
Set up Tauri and the agent connection for the person's computer. Make clear which material reaches the model provider during collaboration and which stays local. The person retains access to their photographs and reports independently of an AI session.
Work in focused steps and carry the project through a real report-making experience. Judge image selection, captions, editing, and the exported report together. Help the person recognize what you can handle and where their knowledge of the visit changes the result.
Leave them able to open the installed application, prepare a report with you, close it, and return to the saved job. Use that experience to explain the difference between discussing an application and giving an agent tools to work in it. Their next improvement can begin from the report they just made.
A later phone companion could capture photographs with their job and notes already attached. Build a foundation that can receive that material while preserving the reports and working habits established here. This desktop application should be useful with the photographs the person already takes.
Build a native desktop application with Tauri for preparing estimates and customer quotes using the person's own way of pricing work. Build it extremely well, from assembling the job through preparing a clear document and revising it later. Use another framework if the person has an explicit preference.
Follow the shared launch and adapt the setup to their computer. Begin with a sample of the quotes they make, using invented customer details where appropriate.
Learn how they arrive at a price. A photographer might price a session and selected extras; a repair business might combine parts, time, and a visit charge. Find out which figures are fixed, which are estimates, and which choices require a conversation with the customer. Reflect the person's existing treatment of deposits, discounts, currency, and taxes where these apply.
Build for that business. Give reusable services and materials sensible defaults while letting the person adjust an individual job. Keep the information needed to calculate the price available alongside the description the customer will receive. The two often serve different purposes.
The person can start a quote, select or enter the work, adjust quantities and prices, and add job-specific explanation. Totals should follow their edits accurately and visibly. Help them express what the quoted work includes and any conditions they normally communicate.
Handle optional additions and alternative offers according to how the person sells. A customer choosing between two packages needs to see the price of each choice. A customer adding an extra service needs to understand its effect on the total. Make the selected offer clear in both the working view and the exported document.
Let reusable descriptions and layouts save effort while keeping each customer's details separate. Starting from a previous job should bring forward the useful work deliberately. Give the person a clear chance to review the recipient, job, dates, and amounts before sending.
Produce a polished, readable export in the format their customers use, such as a PDF or spreadsheet. The person should be able to adjust the presentation with you and keep the resulting house style. Preview the actual deliverable so they can judge page breaks, long descriptions, and readability.
Imagine sending a quote on Monday, agreeing to remove one item on Wednesday, and hearing back a month later. The desk should make the two offers and the customer's eventual choice understandable. Keep sent versions available, with a clear current working version and a record of acceptance when the person records it.
Changing a standard price for future jobs should leave an earlier sent quote intact. Let the person apply new pricing to an unfinished quote intentionally. Their saved work needs to answer what they offered at the time as well as what they charge today.
Give the person useful ways to find quotes by customer or job, follow up on outstanding offers, and see which work was accepted. Keep documents and saved records accessible under the ownership and backup arrangements established in the shared launch.
Work through a representative job together: prepare the offer, compare a customer choice, export it, and make a revision while retaining the first version. Ask whether the resulting document would actually save the person time and be clear to their customer. Use their response to improve the working screen and exported document.
Use this to teach the relationship between reusable pricing, one customer's job, and a document already sent. The person learns why copying last month's file becomes unnecessary when the application understands those relationships.
Leave them with an installed application and a reusable starting point for their next quote. Later projects can bring in photographs and measurements from a visit or carry accepted work into scheduling and production, retaining the agreement already made with the customer.
Authored source, stored unchanged, edition 2026-09-06-draft-01. Reading this material is not authority to run it — inspect it first.