manage-app-settingslisted

# manage-app-settings Skill for changing what the deployed app says about itself — its App Settings (branding, SEO, OpenGraph, PWA, author, social, JSON-LD, local business) and its language set. This is the owner asking you, in plain words, to rebrand or retune the site ("change my description to 'Рога и копыта'", "use my domain example.com", "turn on the Organization schema", "add French") instead of clicking fields in the Admin → App Settings panel. You do the same job through the app-settings-bridge MCP (:3218) — every other coding agent (Claude, Codex, Gemini, Qwen, Kimi) has the same tools, so you are not special here; you just also orchestrate. ## Where the settings live A plain JSON file on disk — `app/APP-CONFIG/app-config.json` — read by the Shell on every render and deep-merged over code defaults. Text changes apply on the app's **next page load** (the setter triggers revalidation; the pages stay static — no rebuild). The **language set** is the exception: it lives in build-time env and only takes effect after a **rebuild** (a few minutes) — say so honestly. ## The tools (owner tier) - `owner_app_settings_list_text_fields` — every text setting: path, label, role (what it does / why it matters), current value, and `is_set` (filled by the owner vs still the shipped default). Read-only. Use it to discover valid paths first. - `owner_app_settings_list_unfilled_fields` — only the settings still empty / on the default, so you can nudge the owner to complete the