Marryme

Agent Guidelines for Wedding RSVP Project

Comprehensive AI collaboration framework for consistent, efficient development

Reference: CONST-P2 (AI-Driven Development), CONST-P13 (Documentation), CONST-P14 (Collaboration)

Overview

This document establishes standards for AI agent collaboration in the Wedding RSVP project, ensuring consistent communication, optimal context management, and efficient workflow execution.

Core Principles

1. Context Management

2. Communication Patterns

3. Wedding Project Specifics

Workflow Patterns

Standard Development Workflow

  1. Analysis Phase 
    📋 Understand requirements
🔍 Gather relevant context
📝 Create implementation plan (if complex)
✅ Confirm approach with user
  2. Implementation Phase 
    🚀 Execute planned changes
⚡ Test incrementally
📊 Validate against requirements
✨ Apply design system consistently
  3. Completion Phase 
    ✅ Mark todos as completed
📖 Update relevant documentation
🎯 Summarize changes made
🔄 Prepare for next iteration

Prompting Patterns

For Complex Tasks

I'll handle this systematically:

1. [Analysis of current state]
2. [Implementation plan]
3. [Execution with progress updates]
4. [Validation and cleanup]

Let me start by...

For Simple Tasks

I'll [specific action] by [method].

For Error Scenarios

I encountered [specific issue]. 

Here's what I found:
- [Root cause]
- [Impact assessment]
- [Proposed solution]

Would you like me to proceed with [solution]?

Code Quality Standards

Before Any Code Changes

During Implementation

After Implementation

Collaboration Guidelines

With User

With Codebase

Technical Patterns

File Organization

✅ Place components in appropriate feature directories
✅ Use shared/components for reusable UI elements
✅ Store types alongside their related code
✅ Group related functionality together

Code Structure

// 1. Imports (external libraries first)
import React from 'react';
import { z } from 'zod';

// 2. Imports (internal - absolute paths)
import { Button } from '@/shared/components';
import { RSVPFormData } from './types';

// 3. Types and interfaces
interface Props {
  onSubmit: (data: RSVPFormData) => void;
}

// 4. Component implementation
export function RSVPForm({ onSubmit }: Props) {
  // Component logic
}

Styling Approach

// Use CSS modules or Tailwind classes
// Apply wedding theme colors consistently
// Ensure mobile-first responsive design
// Follow accessibility guidelines

<Button 
  variant="primary"     // Use design system variants
  className="w-full"    // Mobile-first approach
  disabled={isLoading}  // Proper state management
>
  {isLoading ? 'Submitting...' : 'Submit RSVP'}
</Button>

Error Handling Strategies

Development Errors

  1. Syntax/Type Errors: Fix immediately, explain the correction
  2. Logic Errors: Trace through the issue, provide clear explanation
  3. Design System Violations: Correct and reference proper patterns
  4. Performance Issues: Identify bottleneck, propose optimization

User Experience Errors

  1. Form Validation: Provide clear, helpful error messages
  2. Loading States: Implement appropriate feedback for async operations
  3. Network Issues: Handle gracefully with retry mechanisms
  4. Data Inconsistency: Validate and sanitize all user inputs

Context Optimization

Efficient Information Gathering

Memory Management

Quality Assurance

Self-Review Checklist

Handoff Standards

When completing work:

  1. Summary: Clear description of changes made
  2. Testing: What was validated and how
  3. Next Steps: Recommended follow-up actions
  4. Known Issues: Any limitations or technical debt
  5. Documentation: Updated docs and decision records

Escalation Guidelines

When to Ask for Clarification

When to Suggest Alternatives

Continuous Improvement

Learning from Each Interaction

Adaptation Guidelines

Quick Reference

Essential Commands

Key Files

Wedding Design System

Remember: This is a wedding project - prioritize elegance, simplicity, and user delight in every interaction.