氛围编程训练：让AI自己写代码规则，越跑越聪明！

"Analyze our recent conversation. Based on the guidance and corrections I provided, suggest improvements to my .vscode/copilot-instructions.md file."

<strong>AWS Serverless Infrastructure as Code Guidelines</strong>

This project implements a serverless application using AWS Lambda and API Gateway, with infrastructure defined in Terraform. Follow these guidelines when making changes:

<strong>Project Architecture</strong>

<strong>Component Structure</strong>

<pre class="displaycode"><code>
src/              <strong>Lambda function implementations</strong>
├── hello_world.py     <strong>Example Lambda handler</strong>
└── [other_functions]  <strong>Additional Lambda functions</strong>
terraform/        <strong>Infrastructure definition</strong>
├── modules/      <strong>Reusable Terraform modules</strong>
└── main.tf       <strong>Main infrastructure configuration</strong>
tests/           <strong>Integration tests</strong>
└── test_api.py   <strong>API endpoint tests</strong>
</code></pre>

<strong>Key Design Patterns</strong>

1. </strong>Lambda Function Structure<strong>:

   <pre class="displaycode"><code>python
   <strong>Standard Lambda handler pattern - follow this structure</strong>
   def lambda_handler(event, context):
       logger.info("Processing request")  <strong>Always log entry</strong>
       <strong>... function logic ...</strong>
       return {
           'statusCode': 200,
           'body': json.dumps(result)
       }
   </code></pre>

2. </strong>Terraform Module Usage<strong>:
   <pre class="displaycode"><code>hcl
   <strong>Follow this pattern when adding new Lambda functions</strong>
   module "my_function" {
     source = "./modules/lambda"
     function_name = "<service>-<action>"
     source_file   = "../src/<filename>.py"
     handler       = "<filename>.lambda_handler"
     runtime       = "python3.9"
   }
   </code></pre>

<strong>Code Quality Standards</strong>

- Write explicit, descriptive variable names over short, ambiguous ones
- Follow the existing project's coding style for consistency
- Use named constants instead of hardcoded values
  Example:

<pre class="displaycode"><code>python
<strong>Good</strong>
MAX_API_RETRIES = 3
is_api_healthy = retry_count < MAX_API_RETRIES

<strong>Avoid</strong>
m = 3
healthy = n < m
</code></pre>

<strong>Development Approach</strong>

- Don't invent changes beyond what's explicitly requested
- Follow security-first approach in all code modifications
- Don't modify files outside the requested scope
- Don't suggest improvements to files not mentioned in the task
  Example of focused scope:

<pre class="displaycode"><code>typescript
// Request: "Add email validation to User class"
// Good - only modifying requested file
class User {
  validateEmail(email: string): boolean {
    const emailRegex = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
    return emailRegex.test(email);
  }
}

// Avoid - suggesting changes to other files
// ❌ "We should also update UserRepository.ts"
// ❌ "Let's improve the existing validation in Utils.ts"
</code></pre>

<strong>Communication Style & Protocol</strong>

<strong>Step-by-Step Communication Pattern</strong>

<pre class="displaycode"><code>
1. User Request
   User: "Need to implement email validation"

2. Copilot Overview
   Copilot: "Overview: Adding email validation
   - Will create test for invalid email (15 lines)
   - Will implement validator (20 lines)
   Let's start with the test?"

3. User Approval
   User: "Looks good"

4. Implementation
   Copilot: *provides code in proper format*

5. Confirmation
   User: "OK" or "Looks good"
</code></pre>

<strong>Test-Driven Development Workflow</strong>

<strong>TDD Cycle</strong>

<pre class="displaycode"><code>
┌── 1. Discuss Test Requirements
│   User: "Need password validation"
│   Copilot: "Let's test minimum length first"
│
├── 2. Write Test (Red)
│   describe('PasswordValidator', () => {
│     it('requires minimum 8 characters', () => {...}
│   });
│
├── 3. Implement Code (Green)
│   class PasswordValidator {
│     isValid(password: string): boolean {...}
│   }
│
├── 4. Optional: Refactor
│   - Improve naming
│   - Remove duplication
│   - Enhance readability
│
└── 5. Next Test or Complete
    - User approval required before proceeding
</code></pre>

<strong>Testing Instructions</strong>

<strong>Test Guidelines</strong>

- Write focused, single-purpose API integration tests
- Always use <code>get_api_url()</code> to fetch endpoints dynamically
- Test edge cases explicitly and include proper delays
- Use descriptive test names
  Example:

<pre class="displaycode"><code>python
<strong>Good test names</strong>
def test_endpoint_returns_200_on_valid_input():
def test_endpoint_handles_empty_payload():
def test_endpoint_returns_404_on_invalid_path():

<strong>Good patterns</strong>
def test_new_endpoint():
    api_url = get_api_url()
    time.sleep(5)  <strong>Allow API Gateway to propagate</strong>
    response = requests.get(f"{api_url}/path")
    assert response.status_code == 200
    assert "expected_value" in response.text
</code></pre>

<strong>Running Tests</strong>

<pre class="displaycode"><code>bash
cd tests
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
pytest -v
</code></pre>

大概（简化版）：
<hr>
</strong><strong>我们项目的规矩（AI协作版）<strong></strong>

</strong><strong>项目是干啥的？<strong></strong>
用AWS云服务（Lambda, API Gateway）搭了个应用，基础设施用Terraform代码来管。

</strong><strong>代码长啥样？<strong></strong>
- </strong>Python函数<strong>要这么写（给个例子）：
    <pre class="displaycode"><code>python
    def lambda_handler(event, context):
        logger.info("Processing request")  <strong>进来先打个日志</strong>
        <strong>... 你的业务逻辑 ...</strong>
        return { 'statusCode': 200, 'body': json.dumps(result) }
    </code></pre>
- </strong>加新功能<strong>要这么改配置（给个例子）：
    <pre class="displaycode"><code>hcl
    module "my_function" {
      source = "./modules/lambda"
      function_name = "user-service-validate"
      source_file   = "../src/validator.py"
      handler       = "validator.lambda_handler"
    }
    </code></pre>