기존 웹사이트 리디자인을 위한 AI 프롬프트

웹사이트 리디자인 요구사항

Audit this existing website before redesigning it.
Read its stack, routes, page copy, API calls, forms and shared components.
Protected: canonical URLs, navigation destinations, login/checkout behavior,
prices, analytics events and existing product facts.
Goal: make the offer and primary action easier to understand without new claims.

Record the current desktop and mobile layouts. Identify the three most useful
presentation changes, with section names and screenshot evidence.
Propose a small plan: hierarchy, typography, spacing and reusable component rules.
After approval, change one section first and show the result before expanding.
Retest the original links/forms, 1280/390/320 px layouts, keyboard focus and images.
Preserve headings, metadata, canonical/hreflang and internal links unless the
brief explicitly calls for an SEO change. Report actual checks, not assumed passes.

모바일 레이아웃 수정

Repair horizontal overflow at 320 px in the existing hero.
Find the element causing overflow before changing styles.
Preserve desktop layout, copy, image meaning, primary action and all destinations.
Use wrapping, responsive sizing or a stacked layout appropriate to this section;
do not hide meaningful content or disable horizontal scrolling on the whole page.
Check the same hero at 320, 390, 768 and 1280 px, including keyboard focus.
Return the changed files, before/after evidence and unresolved failures.

결함 하나 때문에 전체 사이트를 다시 생성해야 하나요?

보통 실제 원인을 해결하는 가장 작은 변경부터 시작하세요. 큰 리디자인은 검토된 계획과 공통 컨트롤·보호 동작의 회귀 검사가 필요합니다. 이전 버전을 보관하고 같은 화면으로 비교한 뒤 수락하세요.