Build your own tools and extensions
A browser extension, a plugin for a program you use, or a simplified version of a large program tailored to you.
Let's understand the idea
If you pay for an extension subscription for just one feature, use only a small part of a large program, or manually repeat an editing step every time, you can build that tool for yourself. Some people make simplified versions of large programs tailored to their needs, and video editors create plugins for their programs.
The easiest way to communicate what you have in mind is to record your screen while using a program you like or carrying out your workflow, then upload the video. If you have the Claude or ChatGPT app installed on your device, task mode (Cowork or Work) can access your device, build the tool, run it, and test it itself, while you review.
Tools for this workflow
Choose from what's available to you. You can use these prompts with several tools. What they can carry out depends on supported features and files.
See tool details and uses in the Tools library →Examples to expand the idea
A video editor repeats the same steps for every video: cutting silences, adding captions, and exporting in two sizes. He recorded his screen doing it once, uploaded the video, and asked for a tool to carry out those steps. Claude Cowork built it on his device and tested it on an old video, and he reviewed the result before relying on it.
Browser extension
Screen recording, downloading images you have the right to use, or a button that summarizes the page.
A plugin for a program you use
Turn a repeated step in your editing or design program into a button.
A version tailored to you
A large program or clinic system with only the parts you use.
Steps from start to delivery
Open any step by its heading. Each explains what to do, why, and what to check before continuing.
1Choose the toolOne clear function.Details
A tool you will use every day matters more than a big idea.
What should I do?
- Write down what you pay for or do manually.
- Specify exactly what the first version will do.
2Record your screenA written description of the screens and steps.Details
Video communicates what is hard to describe in words.
What should I do?
- Record the program you like or your workflow steps.
- Upload the video and ask for a description of the tool before any code.
3Build the first versionA working version you can open.Details
The first version shows you what is missing.
What should I do?
- Build it in Claude or Lovable in your browser.
- Or let Cowork or Work build it on your computer, run it, and test it itself.
Tools for this part: choose oneA guide for this stepHow do you build a website or app with AI?4Test it on your real workA tool that does what you need on your work.Details
The example it was built on is not enough.
What should I do?
- Use it on a real file or task.
- Send the exact text of any error, and change one thing at a time.
5Protect your computer and dataA safe tool you can use every day.Details
The tool accesses your files or the pages you open.
What should I do?
- Ask for only the permissions it needs.
- If it contains people’s data, read the privacy guide.
Prompts for your work
Open a prompt and fill in your details. Empty fields remain visible so you don't forget them.
Describe the tool from a screen recordingOpen it to copy or tailor the prompt
Prepare the listed inputs and start with the prompt in an available tool. Open the output and review it against your work.
Copy the prompt as it is, or tailor it with your details first.
Tailor the prompt to your workOptional: add your details and the prompt adjusts itself
View full prompt
Why is the prompt written this way?
Clarifying behavior and inputs helps us build something people can use, beyond just a page's appearance.
Build the tool and test itOpen it to copy or tailor the prompt
Copy the prompt as it is, or tailor it with your details first.
Tailor the prompt to your workOptional: add your details and the prompt adjusts itself
View full prompt
Did the result serve your original goal?
Return to the inputs and sources, and open the output where you'll use it. Check these points before relying on it.
- Does the tool perform one clear function?
- Has it been tested on your real work?
- Have the permissions and data been reviewed?
If there's a problem, name the unsuitable part, show an example, and request a specific edit.