From 79186b8f3a25c591db4f9e829845c5de7b62fcd6 Mon Sep 17 00:00:00 2001
From: promptadmin <your@email.com>
Date: Sat, 6 Jun 2026 20:38:42 +0000
Subject: [PATCH] =?UTF-8?q?Automated=20ingestion=20of=20prompt:=20Claude?=
 =?UTF-8?q?=20-=20Proje=20=C3=A7al=C4=B1=C5=9Fma=20promptu?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 .../coding/claude_proje_alma_promptu_1442.md  | 35 +++++++++++++++++++
 1 file changed, 35 insertions(+)
 create mode 100644 prompts/coding/claude_proje_alma_promptu_1442.md

diff --git a/prompts/coding/claude_proje_alma_promptu_1442.md b/prompts/coding/claude_proje_alma_promptu_1442.md
new file mode 100644
index 0000000..d7884c9
--- /dev/null
+++ b/prompts/coding/claude_proje_alma_promptu_1442.md
@@ -0,0 +1,35 @@
+---
+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