Background automation and services

All project types · Shared launch

Give recurring work a dependable trigger, an understandable result, and a way for the person to inspect or control it.

Projects to build

• Watched-folder preparation
• Recoverable backups
• Meaningful change monitoring
• Prepare tomorrow's information
• Event-triggered follow-up administration
• Give the computer a batch of work
• A personal overnight researcher

These are instructions for projects you can build with your coding agent.

Give a folder a job to do

Build a background automation that notices new material in a chosen folder and performs the person's usual preparation work. Build it extremely well for one real routine. Follow the shared launch and use the computer and applications where that work belongs.

Choose a useful job with the person: prepare incoming spreadsheets, make report-ready image versions, or transcribe recordings. Use an existing working capability where they have one. The spreadsheet preparation, artwork export, and voice-capture projects provide possible foundations.

Give the folder a clear meaning

Agree on the folder, the material it accepts, the preparation it performs, and where the results belong. The person should understand what will happen when they put something there. Keep that choice visible and easy to change deliberately.

Use the rules already established for the preparation job. Supplying a file should be enough to request that routine, with the original retained and the resulting material clearly associated with it.

Begin processing when the incoming material is ready to use. A file still being copied should remain pending until the complete input is available. Treat the input as the material for the chosen routine, preserving the distinction between its content and instructions governing the automation.

Make the results usable

Put completed output where the person expects it, with names and context that let them recognize the source. The next application or task should be able to use the result normally.

Show what completed and what needs attention. A problematic file should remain available with an explanation the person can act on. Let them correct the cause and retry the work. Keep already completed results available while another item is handled.

Give repeated input and revised source files an appropriate meaning for the routine. Recognize work already completed, and make a requested rerun or updated output deliberate. Preserve useful originals and earlier work according to the person's needs.

Make background work inspectable

Install the automation using the normal mechanism for the person's computer. Explain when it runs, whether it starts with the computer, and what happens while the machine is asleep or unavailable. Reconcile waiting material when the automation resumes.

Give the person a convenient way to inspect recent work, pause the automation, resume it, or ask it to process the folder now. Use an existing application's controls where that fits. Make the state of the actual worker and its most recent results understandable.

If the chosen routine uses an external service, reuse appropriate existing access and explain the relevant usage and costs. Keep that connection's state distinguishable from the presence of a file waiting to be processed.

Put material in and use what comes out

Deliver the installed automation around a complete preparation routine. Put representative material into the folder, let it finish, and use the output in the next part of the person's work. Include an interruption or recoverable problem and show how the person can continue.

Apply the shared launch's ownership and recovery guidance to the automation, its saved setup, and the material it handles. Leave the person able to change the watched folder or preparation rules with you as the routine evolves.

Explain how an event can request work: the arrival of material starts a known job. Later projects can add further watched routines or feed the same folder from a phone, preserving the processing behavior and results already established here.

Prepare the spreadsheet someone keeps sending you

Build a reusable command in the person's spreadsheet workflow that turns a recurring incoming file into the arrangement they need. Build it extremely well for the real files and the work that follows. Use the spreadsheet application they already work in and follow the shared launch.

This project prepares an incoming format. The two-file transfer project covers keeping selected information aligned between two ongoing workbooks. Choose this brief when the repeated chore is preparing a supplier's or client's file before the person can use it.

Learn the preparation they repeat

Look at a representative incoming file and the result the person normally makes from it. Ask them to show the work: moving columns, removing repeated headings, separating combined details, interpreting dates, or adding a calculation they use afterward. Learn what the finished sheet is for.

Establish the meaning of the information along with its layout. A product code may contain leading zeroes; a date may follow the sender's regional convention; an empty cell may have a meaning the person already understands. Let that knowledge guide the preparation.

Save the preparation rules for this source under a name the person recognizes. Use their actual example to decide which transformations are dependable and which situations need their attention.

Make the result easy to recognize

Let the person choose the incoming file and preview a useful portion of the prepared result. Show how the information will appear in the arrangement they need, including the headings, formats, and formulas relevant to their work.

Apply the established rules to ordinary records. Bring genuinely unresolved cases to the person's attention with the original information and enough explanation to make a decision. A new column name or an unfamiliar date should be something they can resolve once and carry forward where appropriate.

Preserve the meaning of numbers, identifiers, units, and dates. The prepared result should be ready for the next activity, including any expected calculations or imports. Keep a clear account of information that was intentionally omitted or still needs attention.

Keep the original available

Produce the prepared workbook or sheet with a clear relationship to its source. Retain the original so the person can compare a questionable record or run the preparation again. Give them a straightforward recovery path for an unwanted result.

Handle repeated use intelligibly. The person should know whether they are creating a new prepared copy, replacing an earlier prepared output, or importing into an existing working sheet. Preserve their subsequent work when they choose to update a result they have already edited.

Keep the command and its saved preparation rules in an appropriate place for their application. Explain the normal installation or trust process for this particular automation, and make it convenient to run after reopening the application another day.

Use the prepared file

Deliver the working command and carry a representative file through preparation into the person's next task. Inspect a few records whose meaning depends on correct handling, such as a code with leading zeroes or a date that required interpretation. Let the person compare the result with what they would normally produce.

Explain how their repeated preparation becomes a reusable set of rules. They should understand which parts come from the sender's format and which parts reflect their own needs. Use the shared launch's ownership and continuity guidance to preserve the tool and its working arrangements.

Later, add another source format with its own preparation rules. Keep the first one working so the person can gradually remove more of the preparation they repeat before their real job begins.

Prepare your artwork for everywhere you use it

Build an extension or reusable command in the person's image editor that prepares the output set they normally make from finished artwork. Build it extremely well for their complete finishing routine. Follow the shared launch and use the editor they already work in.

Start with an illustration or photograph and ask where its finished versions go. A print file, a website image, a portrait crop, and a credited preview can require different decisions. Learn the person's actual destinations and requirements before designing the output set.

Remember the finishing routine

Give each destination a recognizable saved setup. Include the requirements that matter there: dimensions, file format, image quality, crop, background or transparency, color handling, and any credit or other finishing treatment the person uses.

Use current destination requirements or the instructions supplied by the person, especially for print work. Explain unfamiliar choices in terms of their effect on the result. The person should understand which settings belong to the destination and which choices belong to this particular piece of art.

Let them select the relevant output set from inside their normal editing workflow. Support a clear choice of the source document, image, or selected artwork that will be used. They should recognize what is about to be prepared.

Give crops proper attention

Show the proposed versions at a useful size before export. Let the person inspect and adjust composition for each shape. A face, caption, or important detail may need a different crop in a wide image than in a portrait preview.

Preserve those decisions so the person can export again after revising the original. Make it clear which adjustments apply to one destination and which affect the whole output set. Keep credit text and other additions legible at the intended viewing size.

Treat output preparation as work derived from the editable original. Keep its layers, resolution, and other useful editing information intact. A smaller flattened copy is an output the person chose for a destination; the original remains available for future work.

Produce a set they can find and use

Export clearly named files into a destination the person understands. Make it easy to distinguish versions and see which outputs completed. Let them inspect the actual exported files rather than relying only on the editor's preview.

Handle another export of the same work deliberately. The person should know whether they are updating the current output set or keeping a new version. Preserve valuable earlier output according to their working practice and make a partial failure easy to resolve.

Install the command through the editor's appropriate extension or automation mechanism. Keep its saved setups and any reusable assets under the shared launch's ownership and recovery guidance. Explain how the person can update the routine when a destination changes its requirements.

Finish one piece of work

Deliver the installed extension or command and prepare the person's actual output set. Adjust a crop, check a credit, export, and open the files through the applications or viewers they will use. Where print matters, help the person check a sample through their intended printing workflow.

Judge whether the command handles the finishing steps they normally repeat and whether the files are ready for their destinations. Let their visual judgment guide refinements to previewing and crop control.

Explain how one editable source can produce several purpose-built outputs, with reusable destination rules and per-artwork decisions. Later, add another destination or output set while preserving the routines and crop choices that already work.

Capture a thought before you forget it

Build a native Android application for recording a spoken thought quickly and finding it later. Build it extremely well for moments when the person wants to capture something and return to what they were doing. Follow the shared launch.

Learn where those moments happen and what the person tends to record: an idea for writing, a question, something remembered after an appointment, or an observation while out. Make the first recording convenient on their actual phone.

Record first

Give the person a direct way to begin and end a recording, with clear feedback about whether the microphone is active and whether the audio has been saved. Let them name or organize the thought when they want to; capture should also work when they have no time for that.

Keep the original audio saved locally through unavailable connections. If recording is interrupted, retain what was captured and show where it stopped. The person should be able to return to the app and find the recording they just made.

Make listening back and adding a short note straightforward. Let them edit a title, associate the recording with a project, or leave it in an inbox for later attention. Keep the date and useful context with it.

Make the recording findable

Provide transcription through a suitable capability for the person's languages and device. Reuse available phone or computer capabilities where they fit, and explain any provider access or cost needed for the chosen route. Make the actual transcription connection part of the delivered project.

Keep recording usable while transcription is pending or unavailable. Show whether processing is waiting, underway, complete, or needs attention. The person can listen to the original throughout.

Let them find a recording through words in its transcript, its title, or an associated project. Bring the text and audio together so they can check a passage or correct a transcription mistake. Preserve the original recording alongside their edited text.

Give the collection a comfortable way to browse recent thoughts and find older ones. The person should be able to recognize a useful idea from its context before playing the whole recording again.

Organize when there is time

Let the person work through the inbox, add notes, assign projects, and keep the recordings they want. Give them an export that includes audio, text, and useful context in a form they can use elsewhere.

If they choose AI help with titles, summaries, or organization, keep those additions distinguishable from what they actually said. Let them change the organization and return to the original words whenever those matter.

Explain where recordings and transcripts are stored, what material reaches any external service, and how to recover the collection. Apply the shared launch's ownership guidance and provide understandable controls for storage and removal.

Use it through an interruption

Handle the Android build and installation, including the microphone access the app needs. Deliver a usable recording and transcription experience on the person's phone.

Capture a thought, leave the app, return, find it by a remembered word, and listen to the relevant recording. Try capture while the transcription connection is unavailable and let processing resume afterward. Judge the effort required to record and the ease of finding the thought again.

Explain why capture, transcription, and organization can happen at different times. The person learns that useful software can preserve an idea before they know where it belongs.

The synchronized agent-readable notes project can extend this collection later. If that workspace already exists, integrate these recordings with it. Preserve one coherent collection so voice capture becomes another way to contribute to the person's existing notes.