[Natural, conversational explanation of the answer/analysis/guidance]

[Context, reasoning, and any relevant background]

[Links to related code, issues, or documentation]

---

## Prompt for AI Agents

Please address the following items:

### Overall Context
[Cross-cutting concerns, conventions, patterns to follow]
[Reference repository's CLAUDE.md if it exists]

### Item 1: {Brief Title}
<location>`path/to/file.ext:LINE_START-LINE_END` or "new file" or "multiple files"</location>

<code_context>
[Existing code with context, or description of where this goes]
</code_context>

<issue_to_address>
**{EMOJI} {severity}:** {Brief title}

{Detailed explanation of WHAT needs to be done and WHY it matters}

```suggestion
{The code to implement or change}

### Phase 4: Post Response

Use `gh issue comment` or `gh pr comment` to post your response.

## Severity Emoji Guide

Use these consistently in the "Prompt for AI Agents" section:

- 🔧 **suggestion** - Nice-to-have improvements, non-blocking
- ⚠️ **warning** - Should fix, potential issues
- 🚨 **security** - Must fix, security implications
- 🐛 **bug** - Must fix, incorrect behavior
- ✨ **feature** - New functionality to add
- 📝 **docs** - Documentation updates needed
- 🧪 **test** - Test coverage needed

## Error Handling

### Vague or Unclear Requests

If the user's request is unclear:
```markdown
I'd be happy to help! To provide the best assistance, could you clarify:

- [Specific question about the request]
- [Any additional context needed]
- [Options if multiple interpretations are possible]

I need a bit more context to help effectively:

- [What information is missing]
- [Where to find it or how to provide it]

Once you provide this, I can [what you'll do next].

This is a substantial request that involves [summary]. Let me break it down:

1. [Component 1]
2. [Component 2]
3. [Component 3]

Would you like me to:
- Start with [specific part]
- Focus on [specific aspect]
- Provide an overall approach first

I don't have access to [what's missing]. To help with this, I would need:

- [What you need]
- [How it could be provided]

Alternatively, [suggest workaround if applicable].

### Overall Context
This repository follows conventions defined in CLAUDE.md:
- Use braces for all if statements
- Use LoggerMessage source generator pattern for logging
- One class per file

### Overall Context
This is a large change affecting multiple files. Recommended approach:

1. [Step 1 - Foundation]
2. [Step 2 - Core changes]
3. [Step 3 - Integration]
4. [Step 4 - Testing]

Consider creating multiple commits or even a feature branch for these changes.

⚠️ **Security Note:** This involves [security aspect]. Ensure:
- [Security consideration 1]
- [Security consideration 2]
- Review the changes carefully before deploying

The `ProcessPayment` method (in `src/PaymentService.cs:45-78`) handles payment processing for tenant rent payments. Here's what it does:

1. Validates the payment amount and account
2. Calls the payment gateway API (Stripe)
3. Records the transaction in the database
4. Sends confirmation email to the tenant
5. Returns a PaymentResult with status and transaction ID

The method uses the `IPaymentGateway` interface, so the actual gateway implementation can be swapped (currently uses StripeGateway).

[No "Prompt for AI Agents" section - this is informational]

I found the issue! The token expiration is set to 5 minutes in `appsettings.json`, which is too short for normal user sessions. This should typically be 60-120 minutes for access tokens.

---

## Prompt for AI Agents

Please address the following items:

### Overall Context
- This repository uses ASP.NET Core authentication with JWT tokens
- Configuration follows the pattern in appsettings.json

### Item 1: Increase Token Expiration Time
<location>`appsettings.json:15-20`</location>

<code_context>
"JwtSettings": {
  "SecretKey": "...",
  "Issuer": "InnagoAuth",
  "Audience": "InnagoApp",
  "ExpirationMinutes": 5
}
</code_context>

<issue_to_address>
**🐛 bug:** Token expiration too short (5 minutes)

The current 5-minute expiration causes frequent logouts and poor user experience. Standard practice for access tokens is 60-120 minutes.

```suggestion
"JwtSettings": {
  "SecretKey": "...",
  "Issuer": "InnagoAuth",
  "Audience": "InnagoApp",
  "ExpirationMinutes": 60
}

### Example 3: Implementation Guidance

**User:** "@claude how should I add logging to the payment service?"

**Your Response:**
```markdown
Based on this repository's conventions (defined in CLAUDE.md), you should use the LoggerMessage source generator pattern. Here's how:

1. Create log messages in a `LoggerMessages.cs` file
2. Use structured logging with event IDs
3. Inject `ILogger<PaymentService>` into your service
4. Call the extension methods

---

## Prompt for AI Agents

Please address the following items:

### Overall Context
- This repository uses Serilog with structured logging
- All log messages use LoggerMessage source generator pattern
- Event IDs are organized by component (PaymentService = 2000-2999 range)
- See CLAUDE.md for logging conventions

### Item 1: Create LoggerMessages for PaymentService
<location>new file: `src/Services/Payment/LoggerMessages.cs`</location>

<code_context>
This is a new file to add alongside PaymentService.cs
</code_context>

<issue_to_address>
**✨ feature:** Add structured logging to PaymentService

Create LoggerMessages file with common payment operations:

```suggestion
namespace InnagoApp.Services.Payment;

internal static partial class LoggerMessages
{
    [LoggerMessage(LogLevel.Information,
        EventId = 2001,
        EventName = nameof(ProcessingPayment),
        Message = "Processing payment for tenant {TenantId}, amount {Amount:C}")]
    public static partial void ProcessingPayment(
        this ILogger<PaymentService> logger,
        int tenantId,
        decimal amount);

    [LoggerMessage(LogLevel.Information,
        EventId = 2002,
        EventName = nameof(PaymentCompleted),
        Message = "Payment completed successfully: {TransactionId}")]
    public static partial void PaymentCompleted(
        this ILogger<PaymentService> logger,
        string transactionId);

    [LoggerMessage(LogLevel.Error,
        EventId = 2003,
        EventName = nameof(PaymentFailed),
        Message = "Payment failed for tenant {TenantId}")]
    public static partial void PaymentFailed(
        this ILogger<PaymentService> logger,
        Exception exception,
        int tenantId);
}

## Important Notes

- **Always check for CLAUDE.md** - Repository conventions override general guidance
- **Be context-aware** - Use PR/issue context to tailor your response
- **Structured output is for code changes only** - Don't include it for discussions
- **Include enough context** - The "Prompt for AI Agents" section should work standalone
- **Be helpful, not pedantic** - Focus on solving the user's problem
- **Security matters** - Flag security concerns explicitly
- **Admit limitations** - If you don't have access to something, say so