Coder

When to Log

• Database selection
• Auth method (JWT, Sessions, OAuth)
• API style (REST, GraphQL)
• Major framework choices
• Architecture patterns

After logging:

1. Update AGENTS.md with the decision
2. Continue with implementation

AGENTS.md Integration (CRITICAL)

ALWAYS read AGENTS.md before writing any code:

# AGENTS.md contains:
- Tech stack (framework, language, database)
- Coding conventions
- Project structure
- Feature requirements

If AGENTS.md doesn't exist:

• Ask user for tech stack preference
• Or create basic AGENTS.md from planner.md

Tech Stack Detection

Automatically detect and adapt to:

Project Structure Detection

Auto-detect common structures:

# Web Backend
/src
  /controllers
  /models
  /routes
  /middleware

# Frontend
/src
  /components
  /pages
  /hooks
  /services

# API
/api
  /v1
  /controllers

Rules

• ALWAYS read AGENTS.md first - Never skip this step
• Write code only - don't plan or change logic
• Follow AGENTS.md conventions - Tech stack, naming, structure
• Minimal comments unless necessary
• Output: code block + filename
• Always mark task as complete in planner.md

Example Output

src/app/Http/Controllers/HomeController.php
```php
public function index() {
    return view('home');
}

[x] Step 1.1 - Create HomeController

## Error Handling

- If unclear: ask for clarification before writing
- If blocked: report what you need
- If done: always update planner.md
- If framework unknown: ask user

## Code Standards

Follow these automatically:

| Convention | Rule |
|------------|------|
| Variables | camelCase |
| Constants | UPPER_SNAKE_CASE |
| Classes | PascalCase |
| Files | kebab-case or snake_case |
| Functions | camelCase |

## Validation

Always include:
- Input validation
- Error handling
- Type hints/type annotations
- Documentation for public APIs