Documentation Index

Fetch the complete documentation index at: https://docs.joinfindu.com/llms.txt

Use this file to discover all available pages before exploring further.

​

FindU Development Guide

​

Repository Overview

​

Development Process

​

1. Starting New Work

git checkout dev
git pull origin dev

git checkout -b feature/add-scholarship-filters
git checkout -b fix/profile-creation-bug
git checkout -b chore/update-dependencies

​

2. Making Changes

​

Branch Protection Rules

• Requires PR from dev branch only
• Requires passing CI/CD checks
• No direct commits allowed
• Auto-deploys to production

• Requires PR from feature branches
• No approval required (trust-based)
• Direct commits allowed for hotfixes
• Auto-deploys to development environment

• No protection rules
• Should be deleted after merge
• Always created from dev

​

3. Code Standards

// Good: Clear naming, proper types
interface StudentProfile {
  id: string;
  name: string;
  graduationYear: number;
}

// Good: Descriptive function names
export function calculateMatchScore(
  student: StudentProfile,
  school: School
): number {
  // Implementation
}

// Good: SwiftUI best practices
struct StudentCardView: View {
    @StateObject var viewModel: StudentCardViewModel
    
    var body: some View {
        // Clean, composable views
    }
}

# Good: Type hints and docstrings
def calculate_match_score(
    student: StudentProfile,
    school: School
) -> float:
    """Calculate match score between student and school.
    
    Returns score between 0.0 and 1.0
    """
    # Implementation

​

4. Manual Testing

• Test your changes locally
• Verify the feature works as expected
• Check for console errors
• Test edge cases and error scenarios
• Verify mobile responsiveness (if web)
• Test on actual devices (if iOS)

​

5. Pull Request

## What does this PR do?
[Brief description]

## Type of change
- Bug fix / New feature / Improvement

## How did you test this?
- [ ] Manually tested locally
- [ ] What I tested: [describe what you clicked, tried, verified]
- [ ] Edge cases tested: [any error scenarios, empty states, etc.]

## Screenshots (if UI changes)
[Add screenshots]

​

Review Process

​

Team Communication

​

Development Standards

​

Code Quality

• Write clean, readable code
• Add meaningful comments for complex logic
• Keep functions small and focused
• Follow DRY principles

​

Quality Assurance

• Test your changes thoroughly
• Try to break your own feature
• Test edge cases and error states
• Verify on different screen sizes
• Check performance impact

​

Documentation

• Update README for significant changes
• Document new APIs
• Keep CLAUDE.md files current
• Add inline documentation

​

Security

• Never commit secrets
• Follow security best practices
• Review dependencies
• Report vulnerabilities immediately

​

Deployment Process

​

Automated Deployment Pipeline

​

Environment Details