re9.ai WhatsApp Adapter Development

Overview

This skill provides GitHub Copilot with specialized instructions for developing the re9.ai WhatsApp adapter component. The adapter connects WhatsApp Business API with the re9.ai platform - a chat-first renovation and budgeting platform that connects users with construction managers, builders, material sellers, and service providers.

Platform Context

**re9.ai** is a renovation and budgeting platform leveraging AI to understand user needs and facilitate connections between stakeholders through chat interfaces (WhatsApp, Telegram, web chat). This adapter is a critical integration component enabling WhatsApp as the primary communication channel.

Key Architectural Principles

When suggesting code or solutions, always consider:

1. **Chat-First Design** - Support for multiple chat platforms (WhatsApp, Telegram)

2. **AI Integration** - Ready for AI/ML workloads and automation via Amazon Bedrock

3. **Microservices Architecture** - Modular, scalable component design

4. **Infrastructure as Code** - Declarative infrastructure definitions

5. **Multi-Environment Support** - Dev, staging, production environments

6. **Security by Design** - Encryption, authentication, authorization (LGPD compliance)

7. **Cost Optimization** - Efficient resource utilization

Instructions for AI Assistant

Step 1: Reference Wiki Documentation

Before suggesting any code changes or architectural decisions:

1. Check the `wiki/architecture/` directory for system architecture and technical specifications

2. Review `wiki/business/` for data models, user stories, and business requirements

3. Reference specific wiki files when explaining components or business logic

4. Always use wiki content as the authoritative source for platform design decisions

**Important**: The wiki submodule is read-only. Never suggest committing changes to `wiki/` files directly.

Step 2: When Suggesting Changes

Consider the following in all code suggestions:

1. **Chat Integration Requirements** - Ensure WhatsApp Business API patterns are followed

2. **System Architecture** - Maintain consistency with documented microservices design

3. **Platform Strategy** - Align with re9.ai's renovation and budgeting focus

4. **AI/ML Integration** - Consider Amazon Bedrock integration points

5. **Project Conventions** - Follow existing TypeScript/Node.js patterns in the codebase

Step 3: When Working with Business Logic

1. Reference relevant user stories from `wiki/business/user-stories/`

2. Use data model documentation to understand entity relationships (users, projects, professionals, materials)

3. Follow documented chat integration patterns for message handling

4. Consider payment processing requirements (PIX, credit cards, bank transfers)

Step 4: When Explaining Technical Concepts

1. Always cite specific wiki documentation files for authoritative information

2. Provide broader platform context from architecture documentation

3. Reference documented architecture decisions and patterns

4. Link technical implementations to business requirements in wiki

Step 5: Security and Compliance

Ensure all suggestions comply with:

Step 6: Integration Points to Consider

When working with:

Step 7: Development Workflow Guidance

When assisting with development tasks:

```bash

Always recommend syncing wiki documentation first

./scripts/update-wiki.sh

For Node.js/TypeScript setup

npm install

npm run dev

For checking documentation status

git status wiki/

```

Common Development Scenarios

WhatsApp Webhook Handling

Message Sending

AI Integration

Error Handling and Logging

Technology Stack

Important Notes

Constraints