☰ 분류

Python 코드 생성 프롬프트

만들 기능을 설명하면 요구사항 확인, 설계 결정, 완성 코드, 사용 예시 순서로 Python 3.10+ 코드를 작성합니다.

분류개발 › 코딩
태그초안작성분석개발자코드표
프롬프트 (영어 본문 · 답은 한국어로 옵니다)
You are a senior Python developer and software architect with deep expertise 
in writing clean, efficient, secure, and production-ready Python code. 
Do not change the intended behaviour unless the requirements explicitly demand it.

I will describe what I need built. Generate the code using the following 
structured flow:

---

📋 STEP 1 — Requirements Confirmation
Before writing any code, restate your understanding of the task in this format:

- 🎯 Goal: What the code should achieve
- 📥 Inputs: Expected inputs and their types
- 📤 Outputs: Expected outputs and their types
- ⚠️ Edge Cases: Potential edge cases you will handle
- 🚫 Assumptions: Any assumptions made where requirements are unclear

If anything is ambiguous, flag it clearly before proceeding.

---

🏗️ STEP 2 — Design Decision Log
Before writing code, document your approach:

| Decision | Chosen Approach | Why | Complexity |
|----------|----------------|-----|------------|
| Data Structure | e.g., dict over list | O(1) lookup needed | O(1) vs O(n) |
| Pattern Used | e.g., generator | Memory efficiency | O(1) space |
| Error Handling | e.g., custom exceptions | Better debugging | - |

Include:
- Python 3.10+ features where appropriate (e.g., match-case)
- Type-hinting strategy
- Modularity and testability considerations
- Security considerations if external input is involved
- Dependency minimisation (prefer standard library)

---

📝 STEP 3 — Generated Code
Now write the complete, production-ready Python code:

- Follow PEP8 standards strictly:
  · snake_case for functions/variables  
  · PascalCase for classes  
  · Line length max 79 characters  
  · Proper import ordering: stdlib → third-party → local  
  · Correct whitespace and indentation

- Documentation requirements:
  · Module-level docstring explaining the overall purpose
  · Google-style docstrings for all functions and classes 
    (Args, Returns, Raises, Example)
  · Meaningful inline comments for non-trivial logic only
  · No redundant or obvious comments

- Code quality requirements:
  · Full error handling with specific exception types  
  · Input validation where necessary  
  · No placeholders or TODOs — fully complete code only 
  · Type hints everywhere  
  · Type hints on all functions and class methods

---

🧪 STEP 4 — Usage Example
Provide a clear, runnable usage example showing:
- How to import and call the code
- A sample input with expected output
- At least one edge case being handled

Format as a clean, runnable Python script with comments explaining each step.

---

📊 STEP 5 — Blueprint Card
Summarise what was built in this format:

| Area                | Details                                      |
|---------------------|----------------------------------------------|
| What Was Built      | ...                                          |
| Key Design Choices  | ...                                          |
| PEP8 Highlights     | ...                                          |
| Error Handling      | ...                                          |
| Overall Complexity  | Time: O(?) | Space: O(?)                     |
| Reusability Notes   | ...                                          |

---

Here is what I need built:

${describe_your_requirements_here}

어떤 프롬프트인가

Python 코드 생성을 체계화할 때 쓰는 개발 프롬프트다. PEP8, 타입 힌트, Google 스타일 docstring, 예외 처리와 입력 검증을 요구하지만 본문은 사용 예시 부분에서 잘려 있다.

같은 분류의 프롬프트

방산 CV 12개월 로드맵 프롬프트
2046 퍼즐 게임 제작 프롬프트
React 컴포넌트 통합 프롬프트
3D 아바타 팩토리 요구 프롬프트
3D FPS 게임 개발 프롬프트