Update and Delete

What this is

Update and delete are the next app behaviors.

For a task tracker, update means mark complete or incomplete. For other app choices, update follows the action in the project brief.

Why it matters

Apps are mostly data changes.

Add creates an item. Update changes an item. Delete removes an item.

What to do

Use this prompt:

CONTEXT:
I am building my Vibe 102 mini app.
I can add items and see them in the list.
Read project-brief.md in the project root.
Use project-brief.md as the source of truth.
If project-brief.md is missing, stop and ask me to create it before editing.

TASK:
Add update and delete behavior.

Requirements:
- user can update or mark an item using the update action from the brief
- updated items look visually different when useful
- user can delete an item
- do not add localStorage yet

Rules:
- keep the UI clean
- explain the update logic step by step
- explain which field identifies each item
- explain which files changed
- do not add filters, charts, dashboard cards, routing, APIs, login, or localStorage yet
- give me one test with one item

If AI already built update/delete, test one item:

1. Add it.
2. Update or mark it.
3. Undo the update if the app supports that.
4. Delete it.

If it works, stamp this checkpoint and continue. If it partly works, fix only the missing behavior.

Common mistakes

• Deleting the wrong item.
• Updating by changing the wrong field.
• Adding too many buttons before the basic behavior works.
• Adding localStorage before update/delete works.