Bagian dari AI Prototype KitKomentar ini satu langkah dari alurnya: AI bikin prototype, lo bagiin link-nya, orang komentar, AI revisi.Lihat kit-nya

    artifact-comments

    Halaman buatan AI lo sekarang bisa dikomentarin kayak di Figma.

    Link-nya udah bagus, tapi orang bingung mau komentar di mana. Sekarang tinggal klik bagian mana pun, terus tulis.

    Satu pembaca naruh komentar, pembaca kedua bales, dan daftar komentar lompat ke komentar di tab lain
    Satu orang naruh komentar, orang lain bales, terus daftar komentarnya langsung lompat ke bagian di tab lain. Gak ada yang perlu nebak.

    Gratis kok. Tinggal verifikasi nomor WhatsApp, isi email, nanti gw kirim link-nya ke email lo.

    GratisBaruVersi 1.0.3Apa yang baru

    Kabar baiknya

    Bikin penjelasan visual udah gampang pakai AI.

    • Contoh halaman penjelasan: alur lima langkah dan tabel sebelum dan sesudah

      /artifact

      Halaman penjelasan

      Sistem, proposal, atau laporan dalam satu halaman.

    • Contoh prototype pesan kopi: layar pilih ukuran dan susu

      /mockup

      Prototype yang bisa diklik

      Alur fitur buat demo ke klien atau investor.

    Masalahnya

    Tapi pas dibagiin, orang bingung komentarnya gimana.

    • Abis kirim link

      Balasannya screenshot WhatsApp dengan lingkaran merah. Tiga orang, tiga chat, tiga versi coretan.

    • Pas revisi

      "Yang kiri atas itu lho." Kiri atas yang mana? Di slide berapa? Versi yang mana?

    • Dari atasan

      "Bagus kok." Terus diem, karena ngasih komentar beneran itu ribet.

    Solusinya

    Sekarang tiap bagian halaman bisa dikomentarin.

    Klik bagian mana pun, tulis komentar, bales. Gak perlu akun. Semua komentar ada di tempatnya masing-masing.

    Bedanya

    Sebelum dan sesudah.

    Sebelum

    • Feedback dateng berupa screenshot di banyak chat.
    • Nebak "yang ini" maksudnya bagian mana.
    • Reviewer harus bikin akun dulu.
    • Balasan lo nyasar ke chat yang lain.

    Sesudah

    • Semua komentar ada di halaman itu sendiri.
    • Tiap komentar ada persis di bagian yang diklik.
    • Reviewer cukup ngetik nama.
    • Balasan ada di bawah komentarnya, kebaca semua orang.

    Cara kerjanya

    Cukup tiga langkah.

    1. Reviewer klik Comment

      Tombolnya ada di pojok kanan bawah halaman yang lo kirim.

    2. Klik bagian yang mau dikomentarin

      Tulis nama dan komentarnya. Gak perlu daftar apa pun.

    3. Lo buka link yang sama

      Semua komentar ada di tempatnya. Tinggal lo bales satu-satu.

    Yang lo dapet

    Yang beda di kerjaan harian lo.

    • 01

      Reviewer gak perlu akun

      Cukup ngetik nama sekali, browser-nya yang nginget.

    • 02

      Tepat sasaran

      Tiap komentar jadi pin bernomor di titik yang diklik.

    • 03

      Komentar dan balasannya kumpul di satu tempat

      Semua feedback dan jawabannya kumpul di satu daftar.

    • 04

      Langsung lompat ke bagiannya

      Klik satu komentar, halamannya langsung pindah ke bagian itu, walaupun ada di slide atau layar lain.

    Dulu feedback klien buat mockup gw dateng berupa screenshot di lima chat. Sekarang komentarnya langsung ada di halamannya, pas di bagian yang dimaksud.
    Brian Arfi FaridhiBrian Arfi FaridhiProduct Director di Merit · AI Builder · Yang bikin alat ini

    Lihat langsung

    Thread komentar lengkap dengan balasan, di satu bagian halaman
    Daftar komentar, dengan lokasi tiap komentar dan jumlah balasannya
    Semua thread dan balasan di satu daftar: siapa, kapan, dan di bagian mana. Klik satu, halamannya langsung ke situ.

    Yang suka bikin ragu

    Yang biasanya ditanyain duluan.

    Reviewer perlu daftar?
    Gak. Cukup ngetik nama sekali. Nama itu gak diverifikasi, jadi jangan dipakai buat hal yang butuh identitas asli.
    Perlu bisa coding?
    Sedikit. Ada satu baris yang perlu ditambahin ke halaman lo. Kalau halamannya dibikin pakai AI, suruh AI-nya aja yang nambahin. Tempat nyimpen komentarnya cukup disiapin sekali, langkahnya ada di bagian teknis.
    Komentarnya disimpan di mana?
    Di tempat lo sendiri, entah akun Cloudflare atau server lo. Bukan di server gw.
    Beneran gratis?
    Iya. Lisensinya Apache-2.0, boleh dipakai buat kerjaan kantor. Di Cloudflare, paket gratisnya cukup buat kira-kira 500 komentar sehari.
    Halaman gw jadi berantakan gak?
    Gak. Tampilan komentarnya dipisah dari halaman lo, jadi desain lo tetap apa adanya.

    artifact-comments

    Minta feedback berikutnya langsung di halamannya.

    Pasang sekali, terus tiap halaman yang lo kirim bisa dikomentarin tanpa akun.

    Ambil gratis

    Gw kirim link skill-nya ke email lo.

    Cuma dua langkah. Verifikasi nomor WhatsApp lo, terus isi email. Link skill-nya masuk ke email itu. Akun member gratis brianarfi.com juga gw bikinin sekalian.

    Langkah 1 dari 2

    Gw kasih kode, lo kirim kodenya ke WhatsApp gw dari nomor ini. Biar kebukti nomornya beneran punya lo.

    Udah member AI Circle? Link semua skill ada di area member.

    Bagikan

    Kenal orang yang butuh ini? Kirim ke dia.

    Teks yang ikut dikirim

    Feedback langsung ada di bagian halaman yang dimaksud. Gak ada lagi screenshot dicoret-coret. Gratis.

    brianarfi.com/skills/artifact-comments

    Buat yang teknisCara pasang, kebutuhan, lisensi, dan changelog lengkap.

    Kebutuhan

    • Halaman HTML statis apa pun: explainer, mockup, prototype, deck, laporan.
    • Tempat nyimpen komentar: akun Cloudflare dengan Pages dan Workers KV, atau satu server Node yang lo host sendiri (SQLite).
    • Docker opsional, kalau mau jalanin server-nya di container.

    Lisensi

    Apache-2.0

    Versi, lisensi, dan changelog dicek ulang ke sumbernya 2026-10-01

    Changelog

    Apa aja yang berubah, dari versi ke versi.

    Disalin dari CHANGELOG produknya, dicek 2026-10-01. Versi yang belum rilis gak ditampilin.

    Versi 1.0.3Terbaru1 Okt 2026

    Changed

    • README visuals only. The hero gives the page screenshot more room and uses the shared family eyebrow and plain paper. The demo GIF is recorded inside the same browser frame as the hero, with a larger cursor. It shows a reply under a different name and a jump from the list to a comment on another tab (docs/src/sample.html now has tabs and an adapter). The client's version constant moves to 1.0.3. No behaviour changes.
    Versi 1.0.21 Okt 2026

    Changed

    • README rewritten to open with the problem; reference moved to docs/. No code changes.
    • The README top follows the shape of popular open-source READMEs: one line on the problem and who it is for, the demo GIF, Why, What it does, Quick start and a screenshot example. The reference sections move into docs/ (how-it-works.md, backends.md, adapter.md, owner-cli.md, api.md, comparison.md, testing.md), linked from a Documentation list. The stars badge is dropped.
    Versi 1.0.11 Okt 2026

    Changed

    • The README is rewritten around the problem it solves: the shift, the gap, the fix, the loop and a capability table come first. Every technical section is kept. No code changes.
    Versi 1.0.030 Sep 2026

    Added

    • A self-hosted backend, server/node/server.mjs. It needs Node 22.13 or later and no npm packages: storage is one SQLite file through the built-in node:sqlite. It serves the same /api/comments contract and validation as the Cloudflare function, runs every POST in one transaction, and can serve a folder of pages with clean URLs (--static).
    • Owner endpoints on the node server, protected by a token (--token or ARTIFACT_COMMENTS_TOKEN): list every page, soft delete a comment with its replies, and restore it.
    • server/node/package.json (engines node >=22.13) and a Dockerfile.
    • Opt-in CORS on both backends: ALLOWED_ORIGINS (a comma list, or *) on Cloudflare, --allow-origin on the node server. Preflight requests from an allowed origin are answered, and any other origin gets no CORS headers.
    • comments_cli.py --backend cloudflare|node. On node, list, delete and restore go through the owner endpoints with --base and --token. repair and setup stay Cloudflare only and refuse clearly on node.
    • A version line in the Comments panel ("artifact-comments v1.0.0 · What's new") that links to this changelog. data-changelog points it somewhere else.
    • tests/e2e_test.py --backend wrangler|node|both runs the one browser suite against either backend, plus checks for CORS, byte-accurate size limits, and the owner CLI round trip (post, list, delete, restore) on the node server.
    • LICENSE (Apache-2.0) and NOTICE, so the skill can ship as a standalone repository.

    Changed

    • The backend is swappable. The browser client still talks to one URL (GET ?slug=, POST JSON), set with data-api, and both backends implement that contract.

    Fixed

    • Cross-origin pages could not use a comments endpoint on another origin: the server answered the preflight with a bare 204 and no CORS headers, although the README said it could.
    • The 8 KB request limit counted characters, not bytes, so a body of multi-byte text sent without a Content-Length could pass it. It now counts UTF-8 bytes.
    Versi 0.2.030 Sep 2026

    Added

    • Figma-style pins: each thread is a numbered pin at the exact point that was clicked, and clicking a pin opens its thread.
    • A Comments list where every row jumps to its part: it restores the page state, scrolls to the part, flashes it and opens the thread.
    • Replies, one level deep. A reply to a reply joins the top thread.
    • The adapter API (window.ArtifactComments: state, restore, isCurrent, search, label, pause) for pages with tabs, slides or walkthroughs.
    • Hide pins, "Not sent" with Retry for failed or offline posts, Ctrl + Enter to post and Esc to close.
    • Storage of one key per comment plus a rebuilt per-page summary, so simultaneous posts are never lost and a page view costs one read.
    • comments_cli.py with list, delete (to a trash), restore, repair and setup.
    • tests/e2e_test.py, 65 browser checks against wrangler pages dev.
    • The first standalone packaging as a skill, with a README and a demo page.
    • The UI lives in a Shadow DOM attached to <html>, so page CSS cannot restyle it.

    Fixed

    • The space bar and arrow keys no longer reach the page while a comment is typed or while comment mode is on.
    • A jump to a comment whose recorded page state was wrong now searches the other states until the part is found.
    • The comment form flips above the part when opening below it would push the Save button off screen.
    Versi 0.1.029 Sep 2026

    Added

    • An inline click-to-comment layer on one published page: comment mode pauses playback, a click on any element places a numbered marker and asks for a name and a comment.
    • Comments were first kept in the reader's browser, with a Copy all button to send them back.
    • The same day, shared storage replaced that: a Cloudflare Pages Function (/api/comments) on Workers KV, so everyone who opens the page sees every comment, and a command to read them back.