2 min read#agents#prompts#writing
Ten prompts that get a good page out of an assistant
The assistant knows the API. It does not know you. Every one of these prompts gives it the thing it cannot look up.
For the first build
- “Build me a page on tapmy.link. Ask me for everything you need before you create anything.” — the default, and the one the button on the home page copies for you.
- “Here is my current Linktree: <url>. Import the links, then ask me which to keep.” — for moving house.
- “I am a wedding photographer in Kraków. Use the photographer recipe from the docs and adapt it with my links.” — the recipes exist so you do not start from a blank list.
- “Use my exact words for every label. Do not rephrase.” — assistants love to polish; a page in your voice converts better.
- “Mark anything that goes to OnlyFans or similar as 18+.” — it should do this unprompted; saying it costs nothing.
For changes later
- “Add a link at the top: ‘Autumn mini-sessions’, <url>, hide it after 30 November.” — a dated block removes itself.
- “Switch the template to Whisper and centre the header. Show me page.md afterwards.” — reading it back is how you both check.
- “Give the shop link the short path /shop.” — a link you can say out loud.
- “How did the page do this week? Views, uniques, most-tapped link. One paragraph.” — statistics are an API call away.
- “Issue me a new claim link.” — if the first one expired.
The rule behind them
Every good prompt hands over a fact — a URL, a date, a sentence in your voice — and every bad one hands over a wish (“make it look professional”). The assistant can turn facts into a page in one request; it cannot turn a wish into anything but guesses. When a result disappoints, the fix is usually one more fact.