AddThisFeature

Changelog

Tell people what you shipped.

simple Engagement

What it adds

A public changelog plus an in-app 'what's new' indicator.

What your agent is told to do

4
  1. 1

    Create a changelog page listing releases, newest first, each with a date and a plain-language summary.

  2. 2

    Write for users, not for git. 'Fixed a crash when exporting large reports' beats 'bump lib to 2.3.1'.

  3. 3

    Add an unobtrusive indicator when there's something new since the user last looked.

  4. 4

    Mark it seen per-user, server-side.

Edge cases it handles

4
  • The 'new' indicator must clear once the user actually views the changelog.
  • A brand-new user should not see every historical entry marked as new.
  • The indicator must not nag on every page load.
  • The page should be readable and indexable without an account.

Definition of done

6
  • Entries are written in user-facing language.
  • The 'new' badge is per-user and clears when read.
  • New users aren't shown the entire back catalogue as unread.
  • The changelog page is public and indexable.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.