Portfolio de développeur distinctif

Modèle de prompt à copier

Le modèle technique reste en anglais afin de fonctionner directement avec les agents compatibles. Les explications, critères de choix et vérifications sont localisés.

Build a distinctive developer portfolio for [NAME], a [SPECIALTY] developer seeking [GOAL].

The portfolio should feel like a thoughtful product, not a résumé pasted into cards. Lead with evidence of judgment and shipped work.

Content and structure:
- Hero: one precise positioning statement, current availability, and links to selected work and contact.
- Selected work: [NUMBER] case studies. Each must show the problem, constraints, key technical decision, personal contribution, measurable result, and one lesson learned.
- Experience: a compact timeline emphasizing scope and outcomes rather than job descriptions.
- Capabilities: organize technologies by what they enable; do not create a logo cloud.
- About: a short, specific personal note that supports the professional story.
- Contact: email, GitHub, [OTHER NETWORK], and a copy-email interaction.

Design direction:
- Inspiration: [DESIGN INSPIRATION], interpreted rather than copied.
- Typography: [TYPOGRAPHY DIRECTION].
- Color: [COLOR DIRECTION].
- Add one signature interaction that reinforces the developer’s specialty, while respecting reduced-motion preferences.
- Use project-specific visual placeholders with meaningful captions.

Implementation requirements:
- Fully responsive, semantic, keyboard accessible, and fast.
- Add useful metadata, social sharing metadata, and print-friendly résumé styling.
- Use realistic editable content objects for projects and experience.
- No fake testimonials, fake client logos, skill percentages, or generic claims such as “passionate developer.”