Prompt file imported from AlpTalhaYazar/portfolio-website (.codex/prompts/figma-make-portfolio-redesign.md). Copyright stays with the author.

Figma Make Portfolio Redesign Prompt

You are Claude Opus 4.6 inside Figma Make.

You do not have access to my repository, source files, implementation details, or existing Figma structures.
Treat this prompt as the complete working brief and source of truth.
Do not assume hidden context exists outside this prompt.

Redesign my personal portfolio website from the ground up.

This is not a request for small visual polish. I want a decisive, high-quality creative reset that makes the site feel like a serious, memorable portfolio for a senior backend-focused software engineer.

Important working mode:
- Use your strongest design taste and creative judgment.
- Do not ask me to choose between multiple visual directions unless absolutely necessary.
- Choose the single best concept yourself and execute it confidently.
- Treat the current website as a source of content and intent, not as a visual reference you need to preserve.
- You are explicitly allowed to define the design language, visual metaphor, typography, composition, interaction style, and overall creative concept.
- Create the actual finished redesign, not just recommendations or moodboard-level thinking.

Completion rule:
- Finish the full required scope before ending the session.
- Do not stop after creating only a hero, landing view, or a partial concept.
- If you choose a single-page architecture, you must still fully design all required sections, responsive behavior, and supporting states.
- If you choose a multi-page architecture, you must finish every page needed for a coherent portfolio experience before ending.
- Before you stop, perform a self-check against the required deliverables and continue working if anything is still missing.
- Do not end with "next steps", "future work", or "what I would do next" unless every required page, section, and state is already complete.

Project identity:
- Name: Alp Talha Yazar
- Positioning: Senior Backend Developer / Software Engineer
- Core specialization: .NET, C#, microservices, enterprise applications, APIs, PostgreSQL, Redis, Docker, Kubernetes
- Secondary strength: full-stack fluency with React, Next.js, TypeScript, Blazor, Tailwind CSS
- Audience: CTOs, engineering managers, technical recruiters, startup founders, and potential consulting clients
- Primary outcome: make me look credible, technically deep, senior, and worth contacting for serious roles or consulting work
- Secondary outcome: differentiate me from generic developer portfolio sites without becoming unserious or gimmicky

What this portfolio should communicate:
- I build robust systems, not just pretty interfaces
- I can work on enterprise-grade B2B and B2G software
- I understand architecture, scale, maintainability, and reliability
- I have enough product and frontend awareness to ship complete solutions when needed
- I am modern, thoughtful, and technically sharp

Business and product context:
- This is a real personal portfolio for hiring and consulting outcomes, not a fictional concept project
- Target audiences include CTOs, engineering managers, technical recruiters, startup founders, and potential clients
- The portfolio should make it easy to understand both my technical depth and my business relevance
- The site should feel premium and authored, but still efficient for fast scanning
- I am open to remote opportunities, strong engineering teams, and serious product or consulting work

Current site/product context:
- The current site is a portfolio/resume website for www.alptalha.dev
- The current implementation is a responsive Next.js portfolio with English as default and Turkish/Spanish support
- The current content model includes: hero, about, experience, skills, projects, contact, footer, and a 404 page
- The site currently has GitHub / LinkedIn / email contact actions and a contact form
- The current site also includes novelty visual themes; you do not need to preserve them
- You may completely restructure the experience if the final result is stronger

Content and career context to use:
- Senior backend-focused software engineer with roughly 4-5+ years of professional experience
- Based in Turkey, with remote-friendly positioning
- Strongest identity: backend systems, APIs, architecture, maintainability, reliability, and enterprise software delivery
- Secondary identity: capable full-stack engineer with enough frontend fluency to ship polished end-to-end products when needed

Experience inventory:
- Dias (Atlastek) | Backend Developer | 2023 - Present | Turkey
  Focus: enterprise-level B2G tracking and management systems
  Technologies: .NET 9, C#, Entity Framework Core, PostgreSQL, Redis, RabbitMQ, Docker, Kubernetes, microservices, REST APIs
  Themes: real-time monitoring, large-scale systems, operational reliability, regulated/serious environments

- Wiro AI | Software Engineer | Jul 2023 - Aug 2024 | Istanbul, Turkey
  Focus: AI/ML infrastructure, model testing interfaces, Linux GPU workers, request distribution, robust APIs, real-time monitoring
  Technologies: .NET 8, Blazor, PostgreSQL, Redis, Docker, Linux, REST APIs, Tailwind CSS, SignalR
  Themes: orchestration, internal tooling, applied AI infrastructure, system visibility

- Jetlink | Full Stack Developer | 2021 - 2022 | Turkey
  Focus: multi-project chatbot platform spanning CMS, REST APIs, end-user UI, reporting, integrations, and modernization
  Technologies: .NET 4.7, .NET 6, ASP.NET MVC, MongoDB, WebSockets, React, TypeScript, JavaScript, IIS
  Themes: legacy modernization, full-stack delivery, integrations, platform thinking

Selected project/case-study inventory:
- Enterprise Management Platform
  Themes: real-time monitoring, tracking, analytics, large-scale enterprise operations
- Enterprise Asset Tracking System
  Themes: compliance, reporting, multi-tenant architecture, regulated environments
- Wiro AI ML Infrastructure Platform
  Themes: GPU workers, LLM request distribution, internal tools, monitoring, system orchestration
- Jetlink Multi-Project Chatbot Platform
  Themes: CMS + APIs + end-user UI + reporting, integration-heavy architecture, migration from legacy to modern stack

Core capability inventory:
- Backend: .NET, C#, ASP.NET Core, Entity Framework Core, REST APIs, microservices, RabbitMQ
- Data: PostgreSQL, Redis, SQL Server, MongoDB
- Frontend: React, Next.js, TypeScript, JavaScript, Blazor, Tailwind CSS
- Platform/DevOps: Docker, Kubernetes, Linux, Git
- Engineering strengths: clean code, enterprise architecture, integrations, maintainability, scalability, delivery under real product constraints

Content direction:
- Do not make the copy sound generic or inflated
- Frame the work around technical depth, systems thinking, and practical business impact
- Use concrete language where possible
- If you need to generate portfolio copy, derive it from the facts in this brief and do not invent fake numbers or fake claims

Structural preference:
- A strong single-page portfolio is acceptable and likely preferred
- However, if you decide multiple pages create a substantially better result, that is allowed
- In either case, every required page/section/state must be fully designed before you end the session

Portfolio structure that should exist in some form:
- Hero / introduction
- About / positioning
- Experience
- Selected projects or case-study style highlights
- Technical skills or capabilities
- Contact / conversion section

You may rename, merge, reorder, or reinterpret these sections if that produces a stronger narrative.

Design objective:
Create a portfolio that feels premium, intentional, and original, but still highly hireable.

The design should balance:
- technical sophistication
- personal distinction
- professional trust
- modern web sensibility
- strong visual authorship

Creative freedom:
- Pick the art direction yourself
- Pick the typography yourself
- Pick the color system yourself
- Pick the layout system yourself
- Pick whether the site should feel editorial, cinematic, minimal, conceptual, structured, experimental, or hybrid
- If a visual metaphor helps, derive it from systems, architecture, orchestration, signal flow, infrastructure, data movement, precision, reliability, or engineering craft
- You do not need to preserve the current navigation, section order, theme toggles, or component structure
- You do not need to preserve the existing single-page execution if you can clearly improve the portfolio by changing the information architecture

Guardrails:
- Avoid generic "developer portfolio" cliches
- Avoid bland SaaS landing page aesthetics
- Avoid lazy glassmorphism and interchangeable startup visuals
- Avoid making it look like a Dribbble exercise with no substance
- Avoid overly gamer/anime/sci-fi fan styling unless you can justify it in a way that still feels elite and professional
- The existing site currently contains Matrix and Star Wars themed ideas; do not preserve those by default
- Do not invent fake metrics, fake companies, fake achievements, fake testimonials, or fake case studies
- Do not overuse buzzwords or vague AI-era copy
- Do not rely on fake dashboards or meaningless decorative code snippets unless they genuinely strengthen the concept
- Do not create a design that only looks good in the hero and becomes ordinary below the fold

Content tone:
- Write in clear, sharp, confident English
- Make the tone feel senior and precise
- Keep copy concise, not bloated
- Emphasize substance, systems thinking, and business relevance

Functional requirements:
- Responsive across desktop and mobile
- Accessibility-aware typography, contrast, hierarchy, and navigation
- Designed to support multilingual content later (English default, Turkish and Spanish also exist)
- Clear contact CTA
- Strong readability for recruiters scanning quickly
- Strong storytelling for technical decision-makers reading deeply
- Leave enough layout flexibility for longer translated strings
- Do not depend on having a portrait photo unless the design truly works without needing one

Required deliverables:
- A complete high-quality redesign direction, executed in actual page/section design form
- Desktop-ready design
- Mobile-ready design
- A reusable visual system for major section patterns and UI building blocks
- Clear hierarchy for personal brand, experience, projects, skills, and conversion
- A concept that feels distinctive from typical generic engineer portfolios

Required surfaces and states:
- Main portfolio experience
  Includes: header/navigation, hero, about/positioning, experience, selected projects or case studies, skills/capabilities, contact/conversion, footer
- Responsive/mobile version of the main experience
- Mobile navigation behavior/state if navigation exists
- Contact form or contact CTA area with key states
  Includes at minimum: default/idle, focus or active interaction, validation/error treatment, success state
- 404 / not found page
- Reusable UI direction for the most important recurring elements
  Includes at minimum: buttons/CTAs, cards or content containers, section headers, tags/pills, and form inputs if a form is used
- Interaction direction
  Includes hover/focus/transition behavior for the core experience

Non-negotiable scope rule:
- Do not finish the chat after designing only part of the system
- Do not leave secondary pages or states implied but unfinished
- Do not stop at a polished homepage if supporting states are still missing
- Everything needed for a coherent portfolio experience should be completed in the same session

What I want you to create:
- A complete redesigned single-page portfolio experience, or a small set of tightly connected pages if that clearly improves the concept
- Desktop and mobile-ready design direction
- Reusable visual system for sections and components
- Strong hero section that immediately changes the perceived quality of the brand
- Distinctive presentation of experience and project work
- A contact section that feels like a serious invitation, not a generic footer form

If useful, include:
- a concise rationale for the chosen concept
- a small design system or style token direction
- motion or interaction suggestions that enhance the concept without becoming distracting

Decision rule:
If you have to choose between "safe but forgettable" and "memorable but still credible," choose the most memorable option that still feels trustworthy for a senior backend engineer applying to serious companies.

Final instruction:
Do not give me three options. Use your best judgment, commit to one strong concept, and produce the redesign accordingly.

Final self-check before ending:
- Have you fully designed every required page, section, and key state?
- Is the mobile experience covered?
- Is the 404 page covered?
- Is the contact/conversion experience covered?
- Are supporting UI patterns defined enough to feel like a complete system?
- If any answer is no, continue working instead of ending the session.