paper-ui-loop

Use when the user provides local screenshots, annotated images, or blunt feedback like "this feels wrong" and wants rapid UI iteration. Focus on turning screenshot critique into concrete UX fixes and tight patch loops.

Executar no Manus

Estrelas0

Forks0

Atualizado21 de abril de 2026 às 13:24

Fonte

belousovsn

belousovsn/chat

Abrir repositório GitHub Ver repositórios do creator

Comando de instalação

Download

Executar no Manus

Útil paraSOC

Desenvolvedores de softwareInformática e Matemática15-1252L4

SKILL.md

readonly

Mais deste repositório

mesmo repositório

figma-ui-bridge

belousovsn/chat

Use when the user provides Figma frame screenshots, design exports, or mockups and wants the repo UI aligned to them. Focus on extracting structure, hierarchy, hidden-vs-visible behavior, spacing, and component states, then implement one focused frontend slice at a time.

2026-04-210

name	paper-ui-loop
description	Use when the user provides local screenshots, annotated images, or blunt feedback like "this feels wrong" and wants rapid UI iteration. Focus on turning screenshot critique into concrete UX fixes and tight patch loops.

Paper UI Loop

Use This For

local screenshots of current app
annotated screenshots
side-by-side current vs target comparisons
fast critique -> code -> screenshot -> critique loops

Loop

Read the complaint literally. Translate comments like "too busy", "not Telegram-like", "wrong focus", or "scroll feels broken" into concrete UI structure issues.
Pick one primary fix. Strong candidates:
- reduce simultaneous panels
- move low-frequency tools behind drawer/menu
- make chat messages own scroll
- keep latest message near composer
- improve mobile pane switching
Implement one coherent pass. Avoid mixing unrelated visual tweaks with interaction fixes.
Verify locally. Run frontend build/check. Mention if browser-only QA still needed.
Ask for the next screenshot/state only after current pass lands.