Step 18: Apply Changes

Phase: iterate

Context

You have user_feedback with requested changes, and app_files with the current code. Modify the app accordingly.

What to do

For each piece of feedback, determine what type of change is needed:

UI/styling changes

Modify CSS or HTML in app_files. Examples: colors, fonts, sizes, layout, visibility.

Feature additions

Add new JavaScript functionality and UI elements. If the feature needs new data storage:

  1. Add new columns or tables via SQL migration: 
    POST https://run402.com/admin/v1/projects/{project_id}/sql
Authorization: Bearer {service_key}

ALTER TABLE todos ADD COLUMN priority text DEFAULT 'normal';
  2. Update RLS if needed (new tables need RLS configuration)
  3. Update the frontend code to use the new schema

Bug fixes

Debug the issue in the code. Common problems:

  • Wrong API endpoint or filter syntax
  • Missing auth headers on authenticated requests
  • RLS blocking access (check table permissions)
  • JavaScript errors (missing null checks, wrong event handlers)

Content changes

Update text, labels, placeholder content, or seed data in the database.

After making changes

Re-run the verification checklist from Step 14 on the modified code. Ensure nothing broke.

What to tell the user

"I've made those changes! Let me put the updated version online for you."

Expected output

  • updated_app_files — The modified app files, ready for redeployment

Memory directive