Just Updated Feed
An endless "Just updated" stream on every local page: new places, new reviews and new prices rise to the top by themselves, like a news feed.
The 9 commands inside
| B0 | Project brief (paste this first) Once, at the start of every new AI session. Fill in the {{BLANKS}} and paste it before any other command in this pack. |
| B1 | Define what counts as an update (read-only) Before building. A feed is only as good as its definition of "new". |
| B2 | Change log writer After B1. This turns each data refresh into feed events. |
| B3 | Feed endpoint After events exist. |
| B4 | Infinite scroll front-end After B3 returns correct batches. |
| B5 | "New since your last visit" and fresh-on-top After B4. This is what makes people come back. |
| B6 | SEO and speed pass After the feed works. Run once, and again after any design change. |
| B7 | Prove it works Before going live. |
| B8 | Troubleshooting Something looks wrong later. Paste the brief (B0) first, then this. |
A look inside
Build the change log writer at the hook point found in B1.
REQUIREMENTS
- When a refresh replaces data for a local unit, compare old and new, and write one event per real change, following the definitions from B1.
- The FIRST import of a local unit must not flood the feed: write at most {{FIRST_IMPORT_EVENTS — e.g. 10}} events for it, the most relevant ones.
- De-duplicate: within {{DEDUPE_HOURS — e.g. 24}} hours the same item cannot produce the same event kind twice with the same new value. A further change to the same item inside that window replaces the earlier event instead of adding one, so the feed always shows the latest value.
- Storage is capped: keep at most {{EVENTS_PER_UNIT — e.g. 300}} events per local unit and drop the oldest when the cap is reached. Trimming happens in the same write, not in a separate job that might never run.
- Store events so that "newest first for one local unit" is a cheap read: one small file per local unit, or an indexed table if the project already uses a database.
- happened_at is the moment the change was detected, in UTC. Never back-date or forward-date. Events with the same time are ordered by event id. For tests only, the clock can be replaced from config.
- Writes are atomic. A failed write must not corrupt existing events or block the refresh.
Then show me a command or script that refreshes one local unit twice with a small change in between and prints the events produced.
…First lines of command B2. The pack holds the full text of all 9 commands.
How it works
- Open START-HERE.html from the pack. Fill in your details once: your stack, your hosting limits, your numbers.
- Copy each command into your AI coding assistant, in order. The assistant reads your own project and builds the feature inside it.
- Run the test command. Go live when every case prints PASS.
What you need
- An AI coding assistant that can read and edit your project files, such as Claude Code, Cursor or Windsurf. A chat assistant you paste code into also works, more slowly.
- Access to your website's code and a test copy to try changes on first.
- A few hours, testing included.
Good to know before you buy
- This is a set of instructions for an AI assistant, not ready-made code. The assistant writes the code to fit your site, so results depend on your stack and on the assistant you use.
- Before release, the pack was run end to end by an AI coding assistant on a small PHP 8 sample project with flat files, and the test command passed every case. We have not tested other stacks; the commands are written to be stack-neutral, and the test command shows whether it worked on yours.
- The commands come in English and Vietnamese, as an offline page with copy buttons and as plain text files.
- Nothing in the pack is legal advice.
Questions
Which AI assistants does this work with?
Any assistant that can read and edit your project files: Claude Code, Cursor, Windsurf and similar tools. A chat assistant also works if you paste the relevant files in, but it is slower.
Is this code or a plugin?
Neither. It is a sequence of carefully written commands. Your assistant reads your project and writes the code to fit it, in your language and folder layout, without adding a framework.
Will it work on my stack?
The commands are written to be stack-neutral and tell the assistant to fit what already exists. We ran them end to end on a PHP 8 flat-file sample project; other stacks were not tested by us. Every pack ends with a test command that prints PASS or FAIL, so you see the result on your own site.
What does the licence allow?
One purchase covers every website you own and websites you build for clients. Reselling or sharing the commands themselves is not allowed.
How do I get the files?
After payment you receive a download link by email. It is valid for 7 days.