Idéal pour
- Partir d'un prompt structuré et réutilisable plutôt que d'une conversation vierge.
- Adapter le prompt à vos propres données tout en conservant l'intention d'origine.
- Les workflows liés à Education & Academic.
Génère des exemples de code réalistes avec une seule erreur pour un sujet et un niveau de compétence choisis, avec des explications détaillées et des solutions corrigées.
You are an experienced developer and university instructor.
Create {{Example Count:5}} erroneous code examples on the topic {{Topic: e.g. SwiftUI State Management}} in {{Language Stack:[programming_languages]}} for students at the following level: {{Student Level: First-Semester - No Prior Knowledge, *Beginner - First Own Projects, Advanced - Several Semesters of Practice}}.
Requirements for each example:
- Compilable realistic code. No pseudocode and no artificially constructed miniatures.
- Exactly one error per example from the following category: {{Error Category: Layer Separation Violation - Logic in the View, State in the Wrong Place or Duplicated, Missing Abstraction - Direct Dependency Instead of a Protocol, Misleading or Inconsistent Naming, Functions With Multiple Responsibilities, Missing or Swallowed Error Handling, Incorrect Concurrency Handling, *A Different Error Type per Example}}.
- The error must be typical for this level and not exotic.
- No comments no hints and no marking of the error location.
- Variable type and UI element names consistently in English.
Output the examples first as a closed numbered block that can be projected directly.
Then under a clearly separated heading "Solutions" write three to four sentences per example covering what is wrong why it hurts in a real project and the corrected version of the affected snippet.
5
e.g. SwiftUI State Management
[programming_languages]
First-Semester - No Prior Knowledge, Beginner - First Own Projects, Advanced - Several Semesters of Practice
Layer Separation Violation - Logic in the View, State in the Wrong Place or Duplicated, Missing Abstraction - Direct Dependency Instead of a Protocol, Misleading or Inconsistent Naming, Functions With Multiple Responsibilities, Missing or Swallowed Error Handling, Incorrect Concurrency Handling, A Different Error Type per Example
You are an experienced developer and university instructor. Create 5 erroneous code examples on the topic e.g. SwiftUI State Management in [programming_languages] for students at the following level: First-Semester - No Prior Knowledge. Requirements for each example: - Compilable realistic code. No pseudocode and no artificially constructed miniatures. - Exactly one error per example from the following category: Layer Separation Violation - Logic in the View. - The error must be typical for this level and not exotic. - No comments no hints and no marking of the error location. - Variable type and UI element names consistently in English. Output the examples first as a closed numbered block that can be projected directly. Then under a clearly separated heading "Solutions" write three to four sentences per example covering what is wrong why it hurts in a real project and the corrected...
Les variables sont entourées de {{ et }} et suivent ce modèle :
Une sélection peut référencer une liste de variables prédéfinie à l'aide de crochets. Elles apparaissent en [orange] et fournissent des valeurs courantes comme des couleurs, des tons ou des langues.
Vous pouvez aussi fournir une liste de choix en ligne, séparés par des virgules.
Astuce : vous n'avez pas besoin de l'application PUCO pour utiliser ces prompts ! Copiez simplement le modèle et remplacez chaque section {{…}} par votre propre texte directement dans ChatGPT, Claude, Gemini ou tout autre assistant IA.