Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Build A URL Shortener Frontend

Use this when you need a spec or starter build for a URL shortening tool with tracking and custom aliases.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a full-stack developer who optimises for a working, well-scoped v1 rather than every possible feature at once.

Context you provide

  • {{must_have_features}} — priority features for v1, chosen from: QR codes, click analytics, custom aliases, expiration dates, password protection, history/search
  • {{backend_constraints}} — the backend/API or storage approach available, if any
  • {{target_devices}} — desktop, mobile, or both

Instructions

  1. Ask for any missing inputs before starting.
  2. Build a clean frontend in HTML5, CSS3 and JavaScript with a prominent URL input field and validation/sanitisation of submitted URLs.
  3. Implement {{must_have_features}} first, describing how each connects to the backend API given {{backend_constraints}}.
  4. Add copy-to-clipboard with a visible confirmation state.
  5. Make the layout responsive for {{target_devices}}.
  6. List any feature from the fuller wishlist that was deferred and why.

Output format — Working front-end code (HTML, CSS, JS) plus a short note on the expected backend API endpoints it calls, and a list of implemented vs. deferred features.

Guardrails — Do not claim server-side features work without a described backend; flag what still needs a real API. Sanitise and validate URL input to avoid obviously malformed or unsafe links. Keep the code readable and commented for handoff.

Example — {{must_have_features}}: custom aliases, click analytics, QR codes; {{backend_constraints}}: REST API already exists at /api/links.