update-screen-design

Update selected responsive screen-design contracts while preserving approved content and Notion identity.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill update-screen-design-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-screen-design
Source: https://github.com/alvis/.agents/tree/main/plugins/client/skills/update-screen-design
Command: npx skills add https://github.com/alvis/.agents --skill update-screen-design-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Updating existing screen-design documentation risks losing approved content, breaking stable Notion page identity, or mixing temporary work reasoning with durable design records. This Skill updates only explicitly selected screen contracts while preserving approved content, relations, and responsive/accessibility decisions. ## Core Features & Use Cases - Bounded Selection: Requires an explicit selector or --all flag, routing missing pages to create-screen-design instead of silently creating them. - Content Preservation: Builds a section-preservation map so requested changes integrate without losing approved alternatives, relations, attachments, or accessibility decisions. - Notion Transport Separation: Keeps Notion body authoring opaque, requiring an explicit body-author capability and transport profile for any remote sync via specification:sync-notion. - Use Case: A product team revises the responsive breakpoints of three checkout screens; the Skill pulls the selected pages, applies only the requested changes, verifies no unselected page changed, and regenerates the durable docs/design derivation with stable Notion ids. ## Quick Start Ask the agent to update the checkout and profile screen designs with the new responsive breakpoint changes using the update-screen-design skill with an explicit screens selector.

Frequently Asked Questions about update-screen-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update existing screen design documentation without losing approved content?

Provide an explicit screen selector and change request; the Skill builds a section-preservation map and integrates only requested changes while retaining approved alternatives, relations, and accessibility decisions. Unselected pages are verified unchanged at completion.

How does the skill sync screen designs with Notion?

Remote sync goes through the specification:sync-notion capability in notion-to-local or push modes, requiring an explicit transport profile and an external body-author plugin for any semantic body change. The identical selector is passed through every nested sync operation.

What happens if a selected screen design page does not exist?

Missing pages are routed to the create-screen-design skill rather than being silently created during an update. The update workflow blocks on missing or duplicate identity until selection is resolved.

Can a delegated subagent write the updated design files directly?

No. Only the main agent writes work state, durable documents, or the external design authority. A delegated run returns proposed content and evidence, then stops before any mutation.

Where do temporary versus durable design documents live?

Temporary work reasoning belongs under the active work's design/ directory with a main-agent-owned design.md, while durable versioned design lives under docs/design/. The Skill never creates a root design artifact or edits the canonical template.