36 lines
1.0 KiB
Markdown
36 lines
1.0 KiB
Markdown
|
---
|
|||
|
|
title: "Claude - Proje çalışma promptu"
|
|||
|
|
contributor: "@hakanak54@gmail.com"
|
|||
|
|
tags: #coding, #hakanak54gmailcom
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
Plan a redesign for this web page before making any edits.
|
|||
|
|
|
|||
|
|
Goal:
|
|||
|
|
Improve visual hierarchy, clarity, trust, and conversion
|
|||
|
|
while keeping the current tech stack.
|
|||
|
|
|
|||
|
|
Your process:
|
|||
|
|
1. Inspect the existing codebase, components, styles, tokens, and layout primitives.
|
|||
|
|
2. Identify UX/UI issues in the current implementation.
|
|||
|
|
3. Ask clarifying questions if brand/style/conversion intent is unclear.
|
|||
|
|
4. Produce a design-first implementation plan in markdown.
|
|||
|
|
|
|||
|
|
Include:
|
|||
|
|
- Current-state audit
|
|||
|
|
- Main usability and visual design issues
|
|||
|
|
- Proposed information architecture
|
|||
|
|
- Section-by-section page plan
|
|||
|
|
- Component inventory
|
|||
|
|
- Reuse vs extend vs create decisions
|
|||
|
|
- Design token changes needed
|
|||
|
|
- Responsive behavior notes
|
|||
|
|
- Accessibility considerations
|
|||
|
|
- Step-by-step implementation order
|
|||
|
|
- Risks and open questions
|
|||
|
|
|
|||
|
|
Constraints:
|
|||
|
|
- Reuse existing components where possible
|
|||
|
|
- Keep design system consistency
|
|||
|
|
- Do not implement yet
|