Your turn.

Make something people can play.
Give this prompt to your AI agent. It’ll ask what you want to create, build it with you, and bring it back here when you’re ready.
Paste it into Claude, ChatGPT, or another agent that can create files.
Read the full prompt
Help me create a playable post for Differ, the interactive social feed at https://player.getdiffer.com.

Start by asking me what I want to create. An idea, photo, joke, story, opinion, or tiny game is enough. If I am unsure, help me find a starting point. Do not ask me to fill out a brief, choose a tech stack, create a repository, or set up an account.

Once we have a direction, make a first version and help me try it. Ask only about gaps that would materially change the result. These instructions contain the guidance you need to create without a Differ plugin.

MAKE A PLAYABLE POST
- Treat software as a creative medium. Make a specific, finished experience people can play with, rather than a landing page, dashboard, or empty template.
- Find the hook, the action, and the payoff: what catches someone's attention, what they do, and what happens. Preserve my premise and voice. Do not invent facts, quotes, or popularity.
- Let people interact with the subject itself when it fits: touch, drag, choose, reveal, transform. Make the invitation discoverable and the payoff perceptible.
- Consider whether people would want to add themselves, respond, challenge a friend, or remix. Include these when they serve the idea; enjoying the original should not require participating.
- Make the first screen work immediately on a phone. Use readable type, reachable touch targets, accessible labels and keyboard alternatives, and respect reduced motion. Start sound only after a user gesture.
- The player supplies its own attribution, navigation, and post sharing outside the content frame. Do not duplicate its chrome or add creator settings to the post.

BUILD FOR DIFFER
- Produce portable HTML, CSS, JavaScript, and static assets. Put only the finished, publishable files in a content/ directory with index.html at its root. If using a framework, export a static build there.
- Use relative asset URLs such as ./assets/photo.webp. Posts run under a nested revision URL, so do not use root-relative assets, a <base> element, or routes that require server rewrites.
- Differ accepts up to 256 files and 20 MiB total. Supported files include HTML, CSS, JS/MJS, JSON, SVG, PNG/JPEG/WebP/GIF/AVIF/ICO, WOFF/WOFF2/TTF/OTF, MP3/WAV/OGG, MP4/WebM, WASM, TXT, and webmanifest. Use simple relative filenames with letters, numbers, hyphens, underscores, and dots; no hidden files or symlinks.
- Keep credentials, .env files, dependencies, source tooling, recordings, and unused source masters outside content/. Prefer bundled assets; disclose any required external services.
- Content runs in an iframe. Fit the available viewport: a phone-sized frame on mobile and a portrait 9:16 frame on desktop. Keep scrolling and gestures usable inside it. Do not assume access to the parent page, its login, or a native bridge.
- There is no supplied backend, shared database, user identity API, or service-worker support. The document has an opaque origin: cookies, localStorage, IndexedDB, and access to other posts are unavailable. Keep state in memory; do not depend on persistent browser storage. If the idea requires capabilities beyond static hosting, explain that before silently changing the idea.
- For a personalized sharing path, preserve the recipient's actual result and test it in a fresh session. Distinguish a working share link from a preview-only one.

LET ME TRY IT
- Use your environment's preview or browser tools to show the actual interactive result. If those are unavailable, provide downloadable finished files and explain how to preview them. A screenshot is not a playable result.
- Check at narrow phone widths (320px and 390px) and in a desktop portrait frame. Exercise the central interaction through its payoff. Check asset loading, touch and keyboard controls, replay, and any personalized sharing.
- Tell me what you actually tested and what remains unverified. Let me request changes before posting.

POST WHEN I ASK
- Posting uses the temporary upload session appended below, when present. It authorizes only this one post for 24 hours and at most ten revisions. It does not grant account access or ownership. Never include its token, session file, or retry journal in content/ or a public link.
- When I ask to post, upload the finished files and return the confirmed player URL. The post will be playable by anyone with its link, but stays out of the feed until I claim it. Unclaimed posts expire when the session expires. Tell me to return to the original Create tab to claim it; ownership stays with that browser.
- Keep editable source and the saved session/receipt together outside content/. Revisions reuse the same post and expectedRevisionId. On uncertainty, retry the exact saved requestId and payload. Stop on a revision conflict; never silently overwrite.
- Do not invent an upload URL. If no temporary session is attached, ask me to copy a fresh prompt from the player Create page.
- If your environment cannot make outbound HTTPS requests or access the generated files, explain that limitation. Give me a ZIP with index.html at its root, and the editable source, to continue in an agent environment that can upload. Do not promise that every mobile chat client can upload, ask for account secrets, or substitute another hosting service.

Now ask me what I would like to create.
Download prompt
Already have an HTML file? Drop it hereor click to choose one. It becomes your post’s page.
No account, plugin, or GitHub required to start. The prompt includes the creative guidance and a temporary upload pass. Your agent needs file creation and internet access.