{
  "rules": [
    {
      "name": "Architecture Consistency",
      "description": "Maintain hexagonal architecture with clear separation between domain, application, and infrastructure layers",
      "examples": [
        "Use repository pattern for data access",
        "Keep business logic in domain services",
        "Use DTOs for API communication"
      ]
    },
    {
      "name": "Authentication Requirements",
      "description": "All endpoints must validate JWT tokens and check user permissions",
      "examples": [
        "Include authorization middleware on protected routes",
        "Return 401 for invalid tokens",
        "Return 403 for insufficient permissions"
      ]
    }
  ]
}

https://lovable.dev/projects/create?template=https://pre.dev/s/abc123

## User Profile Component
- Avatar display with fallback
- Name and bio fields
- Edit mode toggle
- Form validation
- Save/cancel actions

Create a user profile component with:
- Circular avatar (64px) with initials fallback
- Editable name and bio fields
- Toggle between view/edit modes
- Form validation for required fields
- Save and cancel buttons
- Loading states for async operations

# generate-spec.sh
#!/bin/bash
curl -X POST https://api.pre.dev/fast-spec \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"input\": \"$1\", \"outputFormat\": \"markdown\"}" \
  > docs/spec.md

echo "Spec generated: docs/spec.md"

# .github/workflows/generate-spec.yml
name: Generate Feature Spec
on:
  pull_request:
    types: [opened]
    paths: ['features/**']

jobs:
  spec:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Generate Spec
        run: |
          curl -X POST https://api.pre.dev/fast-spec \
            -H "Authorization: Bearer ${{ secrets.ARCHITECT_API_KEY }}" \
            -H "Content-Type: application/json" \
            -d "{\"input\": \"Implement $(cat features/${{ github.event.pull_request.number }}.md)\", \"outputFormat\": \"markdown\"}" \
            > spec.md
      - name: Comment on PR
        uses: actions/github-script@v6
        with:
          script: |
            const spec = require('fs').readFileSync('spec.md', 'utf8');
            github.rest.issues.createComment({
              issue_number: context.issue.number,
              owner: context.repo.owner,
              repo: context.repo.repo,
              body: '## Generated Specification\n\n' + spec
            });

// Pseudo-code for extension
import { ArchitectAPI } from '@predev/architect-api';

export async function generateSpecForSelection() {
  const selectedText = vscode.window.activeTextEditor?.document.getText(selection);
  const api = new ArchitectAPI(process.env.ARCHITECT_API_KEY);

  const result = await api.generateSpec({
    input: `Add feature: ${selectedText}`,
    currentContext: getCurrentProjectContext(),
    outputFormat: 'markdown'
  });

  // Open spec in new tab
  const doc = await vscode.workspace.openTextDocument({
    content: result.markdown,
    language: 'markdown'
  });

  await vscode.window.showTextDocument(doc);
}

Given a user is logged in
When they create a new task
Then the task should be saved with correct attributes
And the task should appear in their task list
And they should receive a success notification

describe('Task Creation', () => {
  it('should create task with correct attributes', async () => {
    const user = await createAuthenticatedUser();
    const taskData = { title: 'Test Task', description: 'Description' };

    const response = await request(app)
      .post('/api/tasks')
      .set('Authorization', `Bearer ${user.token}`)
      .send(taskData)
      .expect(201);

    expect(response.body).toMatchObject({
      id: expect.any(String),
      title: taskData.title,
      description: taskData.description,
      completed: false,
      createdAt: expect.any(String)
    });
  });

  it('should add task to user task list', async () => {
    // Test implementation
  });

  it('should send success notification', async () => {
    // Test implementation
  });
});

Spec Generation → Task Assignment → Parallel Implementation → Integration
     ↓              ↓                      ↓              ↓
  Single Source  Clear Boundaries    Coordinated Work  Verified Integration
  of Truth       of Responsibility   No Conflicts      Meets Requirements

## Integration Point: User Authentication
- Backend provides: POST /api/auth/login → { token, user }
- Frontend consumes: Login component calls API, stores token
- Testing validates: End-to-end login flow works

Backend Agent: "Completed login endpoint, returns JWT token"
Frontend Agent: "Updated login component to call endpoint"
Testing Agent: "Validated login flow meets acceptance criteria"