Execute Prp

# Execute PRP Command

Implement a feature using the PRP file provided as $ARGUMENTS.

## Process

### Load Context
Read the entire PRP file completely. Understand all requirements, constraints, and success criteria. Note the target platform (React Native Expo or Cloudflare Worker). Identify all referenced documentation and examples.

### Plan Implementation
Think hard before you execute the plan. Create a comprehensive plan addressing all requirements. Break down complex tasks into smaller, manageable steps using your todos tools. Use the TodoWrite tool to create and track your implementation plan. Identify implementation patterns from existing code to follow.

### Execute with Validation
Implement each component step by step following the patterns and conventions from the PRP. Run validation commands after each major step. Test functionality as you build. Handle errors and edge cases as specified in the PRP.

### Validation Loops
Run all test commands specified in the PRP. Execute linting and type checking. Verify all success criteria are met. Note: If validation fails, use error patterns in PRP to fix and retry. Continue until all validations pass.

### Platform-Specific Implementation

#### For React Native Expo (hippo/ folder):
- Follow React Native and Expo conventions from existing codebase
- Test on appropriate simulators/devices
- Verify compatibility with Expo SDK version
- Check bundle size and performance
- Validate navigation and state management patterns

#### For Cloudflare Workers (backend/ folder):
- Test locally with Wrangler
- Verify environment variables and secrets
- Test edge cases and error handling
- Check performance and memory usage
- Validate deployment configuration

### Final Verification
Run complete test suite. Verify integration with existing code. Check that all PRP requirements are satisfied. Ensure code follows project conventions from CLAUDE.md. Test the feature end-to-end.

## Success Criteria
Implementation is complete when:
- All PRP requirements are implemented
- All validation commands pass
- Code follows project conventions
- Feature works as specified
- No critical errors or warnings