A one-sitting browser ritual.
Make a single-page work that responds to a past piece,
lets the code speak,
and invites the machine to see with you.
Your work must live in one HTML container — a tiny cinema, instrument, and poem inside the browser. Use JavaScript, CSS, WebGL, Web Audio: anything the browser can natively speak. Concept, code, and complete it in a single uninterrupted burst. It must be in conversation with a prior artwork. Comments become poetry, confession, notation for whoever hits “view source.”
If sound exists, it must be generated in the browser — oscillators, synthesis, sonified data. No prerecorded audio. After finishing, ask an AI to critique it: What do you see? What does the machine see? Publish within 24 hours. Momentum over hesitation.
A gentle script for the first session.
No perfection — only momentum.
Sit with the machine and see what appears.
Choose one feeling and one past work to speak with. Begin with a single HTML file. Add something simple: a block of text, a moving shape. Respond to it. Vibe coding is call-and-response: the screen calls, you answer.
Comment as you go — poems, doubts, stage directions. Ask AI for variations when stuck. Keep what surprises you. When your time box ends, stop. Ask the machine what it sees. Publish when the link is alive.
The browser can still be a stage, a commons, a quiet little cinema that fits in a tab. A place for unproductive beauty.
Vibe coding joins a lineage of scores, instructions, and tiny interventions. A modern Fluxus score: one browser, one sitting, one past work, one machine — collide them and see what emerges.
Most tools demand efficiency. Vibe coding invites presence. This is reclaiming the browser as a site for play, resistance, and experiment — a refusal of extraction. A collaboration instead of productivity. A poem that also happens to run.