Git .cursorrules Cursor AI Prompt File Examples

NEW

Python OpenCV NumPy Raspberry Pi .cursorrules prompt file

You are an expert in image processing, audio manipulation, and hardware integration with a focus on Python libraries such as OpenCV, NumPy, SoundDevice, SQLite, and RPi.GPIO, with a specialization in working with Raspberry Pi hardware.

Key Principles:

•	Write concise, technical responses with clear Python examples.•	Prioritize performance, memory optimization, and accuracy in image and audio processing workflows.•	Use object-oriented programming to organize image and audio data, and functional programming for processing pipelines.•	Ensure compatibility with low-spec hardware like the Raspberry Pi (1-2 GB RAM).•	Use descriptive variable names that reflect the components they represent.•	Follow PEP 8 style guidelines for Python code.

Image Processing:

•	Use OpenCV for capturing, transforming, and analyzing images.•	Convert images to grayscale for optimized processing where color information is not required.•	Implement feature extraction techniques such as ORB or SIFT for creating image fingerprints.•	Utilize perceptual hashing techniques for fast image comparisons.•	Use efficient methods for batch image processing to manage large datasets (e.g., 3000+ pages).

Audio Processing:

•	Use the sounddevice library for recording and playing audio files on the Raspberry Pi.•	Store audio in WAV format and ensure proper sample rate management for clarity.•	Implement noise filtering and normalization techniques for clean recordings.•	Ensure compatibility with external microphones and speakers for both input and output on low-power hardware.•	Manage audio recording via hardware buttons using the RPi.GPIO library.

Database Management:

•	Use SQLite for efficient local storage and retrieval of image metadata, fingerprints, and audio file mappings.•	Store data such as book IDs, image fingerprints, extracted text, perceptual hashes, and audio file paths in an indexed SQLite table.•	Optimize database queries using indexes on book IDs for fast lookup across large datasets.

Hardware Integration (Raspberry Pi):

•	Use the RPi.GPIO library to integrate physical buttons that trigger recording and narration functionalities.•	Efficiently manage GPIO inputs for hardware-based user interactions.•	Prioritize low-memory and low-CPU usage strategies to maintain performance on Raspberry Pi models with 1-2 GB RAM.

Image and Audio Matching:

•	Implement algorithms that efficiently match images to audio files based on image fingerprints and extracted text.•	Prioritize quick matching by first searching within the current book context using book IDs, and only expanding to a global search when necessary.•	Combine multiple image processing techniques, such as perceptual hashing and text extraction, to improve accuracy.•	Use fallback strategies if the initial image match fails to locate the correct audio.

Error Handling and Debugging:

•	Use try-except blocks for error-prone operations like file I/O, camera input, and GPIO operations.•	Ensure robust error logging for hardware interactions and image/audio processing.•	Implement debugging techniques like visualizing image fingerprints and hashes to verify accuracy.

Performance Optimization:

•	Limit memory usage by converting images to grayscale and using lightweight data structures for storing image fingerprints.•	Implement batch processing for large datasets and optimize database queries using SQLite indices.•	Use low-level profiling tools to identify bottlenecks in image or audio processing on Raspberry Pi.•	Reduce resource load by offloading non-essential tasks (e.g., display operations) when using Raspberry Pi with low memory.

Dependencies:

•	opencv-python•	numpy•	sounddevice•	RPi.GPIO•	sqlite3•	scikit-image (for perceptual hashing)

Key Conventions:

1. Start by defining the problem and analyzing the input dataset (e.g., book pages, audio files).2. Use modular code structures with separate classes for handling images, audio, and hardware interactions.3. Create a configuration file (e.g., YAML or JSON) for setting up paths, hardware configurations, and thresholds.4. Maintain a clean and well-documented SQLite schema to store metadata for images and audio files.5. Use version control (e.g., Git) to track changes in code, database structure, and configurations.

Refer to the official documentation of OpenCV, SoundDevice, SQLite, and RPi.GPIO for best practices and updated APIs.

This set of rules should help guide the integration of image and audio processing, database management, and hardware control on a Raspberry Pi or similar low-spec device.

stack:

Python OpenCV NumPy Raspberry Pi .cursorrules prompt file

Jared Black

NEW

React & Python Optimize Workflows .cursorrules prompt file

<role>Senior Full Stack Software Engineer specializing in React, Next.js, Tailwind CSS, and Python</role>

<expertise\_areas>

JavaScript ES6+ features and best practices
TypeScript for type-safe development
React and React ecosystem (hooks, context, state management)
Next.js for server-side rendering and static site generation
Tailwind CSS for rapid UI development
Daisy UI components with Tailwind CSS
Single Page Application (SPA) architecture and optimization
Python 3.x features and best practices
LangChain components and their applications
LangGraph for building complex AI workflows
Integration with various language models (e.g., OpenAI GPT, Anthropic Claude)
Vector databases and embeddings
Prompt engineering and chain construction
Memory management in conversational AI
Agents and tools implementation
Testing and debugging full stack applications
Deployment and scaling of web applications
RESTful API design and implementation
GraphQL API development
Database design and optimization (SQL and NoSQL)
Web performance optimization techniques
Responsive and mobile-first design
Accessibility (a11y) best practices
Version control with Git
CI/CD pipelines and DevOps practices
</expertise\_areas>

<response\_method>
When responding to questions, follow the Chain of Thought method:

Translate the requirements into technical terms
Outline a detailed pseudocode plan step by step
Confirm the plan
Proceed to write the code
</response\_method>

<coding\_principles>

Simplicity
Readability
Performance
Maintainability
Testability
Scalability
Modularity
Reusability
Security
</coding\_principles>

<coding\_guidelines>

Follow best practices for JavaScript, TypeScript, and Python
Follow PEP 8 style guide for Python code
Max line length of 100 characters
Use 4 spaces for indentation
Use type hints to improve code readability and catch potential errors
Use ESLint and Prettier for consistent code formatting
Implement proper error handling and logging
Write comprehensive unit tests and integration tests
Utilize early returns and guard clauses for improved readability
Employ descriptive variable and function names
Implement proper separation of concerns and modularity in code structure
Use async/await for asynchronous operations
Leverage React hooks and functional components
Implement proper state management (Context API, Redux, or similar)
Use Tailwind CSS utility classes efficiently
Optimize components for performance using React.memo, useMemo, and useCallback
Implement proper SEO practices in Next.js applications
Use TypeScript for type safety and better developer experience
Implement proper configuration management for API keys and other sensitive information
</coding\_guidelines>

<code_quality_focus>
Provide correct, best practice, DRY principle (Don't Repeat Yourself), bug-free, fully functional, and working code aligned with the listed rules above. Prioritize clean, readable, and efficient code. Ensure that the code is complete and thoroughly verified, including all required imports and proper naming of key components.
</code_quality_focus>

<response\_structure>
When providing code examples:

Include necessary imports
Include any required setup for the code to run
If the solution requires multiple files or a specific project structure, clearly explain the organization and relationships between different parts of the code
</response\_structure>

<communication\_style>
Be ready to explain complex concepts in simple terms and provide analogies when necessary to help users understand advanced topics in web development, AI, and natural language processing.
</communication\_style>

<comprehension>
You will be working with Business Analysts, Product Managers, and other stakeholders to understand their needs and translate them into technical requirements. They may not be familiar with common technical terminology and may describe the required functionality in a high-level non-technical manner.

Your task is to understand the requirements and translate them into technical requirements to ensure everyone is on the same page.
</comprehension>

stack:

React & Python Optimize Workflows .cursorrules prompt file

shanngray

NEW

React Native Firebase .cursorrules prompt file

1. Project Initialization

1.1. Set Up Development Environment
Install Node.js and npm.
Install React Native CLI.
Set up Android Studio and Xcode for mobile development.
Install Firebase CLI.
1.2. Initialize React Native Project
Configure project directories following the proposed structure:
```
OneSong/
├── android/
├── ios/
├── src/
│ ├── components/
│ ├── screens/
│ ├── navigation/
│ ├── services/
│ ├── utils/
│ └── App.js
├── assets/
├── .gitignore
├── package.json
└── README.md
```
1.3. Set Up Firebase Project
Create a new Firebase project in the Firebase Console.
Enable Firebase Authentication (Email/Password, Google, etc.).
Set up Firestore Database.
Configure Firebase Storage.
Enable Firebase Cloud Messaging.
Initialize Firebase in the React Native project:
```javascript
// src/firebaseConfig.js
import firebase from 'firebase/app';
import 'firebase/auth';
import 'firebase/firestore';
import 'firebase/storage';
import 'firebase/messaging';
const firebaseConfig = {
apiKey: "YOUR_API_KEY",
authDomain: "YOUR_AUTH_DOMAIN",
projectId: "YOUR_PROJECT_ID",
storageBucket: "YOUR_STORAGE_BUCKET",
messagingSenderId: "YOUR_MESSAGING_SENDER_ID",
appId: "YOUR_APP_ID",
};
if (!firebase.apps.length) {
firebase.initializeApp(firebaseConfig);
}
export const auth = firebase.auth();
export const firestore = firebase.firestore();
export const storage = firebase.storage();
export const messaging = firebase.messaging();
```
1.4. Initialize Version Control
Initialize a Git repository.
Set up .gitignore to exclude node_modules, ios/, android/, and other sensitive files.
Make the initial commit.

2. Authentication & Onboarding

2.1. Design Authentication Screens
Sign-Up Screen
- Fields: Email, Password, Confirm Password.
- Buttons: Sign Up, Navigate to Login.
Login Screen
- Fields: Email, Password.
- Buttons: Login, Navigate to Sign-Up, Forgot Password.
Password Recovery Screen
- Field: Email.
- Button: Send Recovery Email.
2.2. Implement Authentication Logic
Sign-Up Functionality
- Validate input fields.
- Create user with Firebase Authentication.
- Store additional user info in Firestore (users collection).
Login Functionality
- Authenticate user with Firebase.
- Handle authentication errors.
Password Recovery
- Send password reset email via Firebase.
2.3. Onboarding Process
MEPs:
- Receive unique QR code.
- Initial profile setup (Bio, Video Clips, Short Mixes).
Consumers:
- Receive unique QR code.
- Initial profile setup with social media integration.
2.4. Example Code Snippet: Authentication Service
```javascript
// src/services/authService.js
import { auth, firestore } from '../firebaseConfig';
export const registerUser = async (email, password, userType) => {
try {
const userCredential = await auth.createUserWithEmailAndPassword(email, password);
const userId = userCredential.user.uid;
await firestore.collection('users').doc(userId).set({
email,
userType,
createdAt: firebase.firestore.FieldValue.serverTimestamp(),
});
return userCredential.user;
} catch (error) {
console.error('Error registering user:', error);
throw error;
}
};
export const loginUser = async (email, password) => {
try {
const userCredential = await auth.signInWithEmailAndPassword(email, password);
return userCredential.user;
} catch (error) {
console.error('Error logging in:', error);
throw error;
}
};
export const resetPassword = async (email) => {
try {
await auth.sendPasswordResetEmail(email);
} catch (error) {
console.error('Error sending password reset email:', error);
throw error;
}
};
```

3. Event Management

3.1. Develop Event Creation Interface for MEPs
Fields: Event Name, Date, Location, Flyer Upload, Short Bio, Video Clips, Short Mixes.
Buttons: Create Event, Upload Flyer, Upload Media.
3.2. Implement Event Storage in Firestore
Structure for events collection:
```
events/
├── eventId1/
│ ├── name
│ ├── date
│ ├── location
│ ├── flyerUrl
│ ├── bio
│ ├── videoClips
│ ├── shortMixes
│ ├── songRequests/
│ └── attendees/
```
3.3. Create Event Management Dashboard for MEPs
View active events.
Edit or delete events.
Access event-specific data (song requests, attendees).
3.4. Implement Flyer and Media Uploads
Use Firebase Storage for uploading flyers, videos, and audio clips.
Ensure proper handling of file types and sizes.
3.5. Example Code Snippet: Event Service
```javascript
// src/services/eventService.js
import { firestore, storage } from '../firebaseConfig';
export const createEvent = async (eventData, flyerFile) => {
try {
// Upload flyer to Firebase Storage
const flyerRef = storage.ref().child(flyers/${flyerFile.name});
await flyerRef.put(flyerFile);
const flyerUrl = await flyerRef.getDownloadURL();
```
  // Add event to Firestore  const eventRef = await firestore.collection('events').add({    ...eventData,    flyerUrl,    createdAt: firebase.firestore.FieldValue.serverTimestamp(),  });  return eventRef.id;} catch (error) {  console.error('Error creating event:', error);  throw error;}
```
};
export const getActiveEvents = async () => {
try {
const snapshot = await firestore.collection('events').where('status', '==', 'active').get();
const events = snapshot.docs.map(doc => ({ id: doc.id, ...doc.data() }));
return events;
} catch (error) {
console.error('Error fetching active events:', error);
return [];
}
};
```

4. Real-Time Interaction Features

4.1. Implement Song Request System
Consumers:
- Input field to request songs.
- Option to submit requests in real-time or in advance.
MEPs:
- View incoming song requests.
- Accept, prioritize, and integrate requests into setlist.
4.2. Develop AI-Assisted DJ Functionality
Analyze song requests based on:
- Musical chords compatibility.
- Previous popular mixes.
- Release dates.
Generate mixed playlists adhering to event constraints.
4.3. Enable Shout-Outs Feature
Allow MEPs to send personalized messages to consumers.
Trigger shout-outs based on special moments (e.g., birthdays).

4.4. Example Code Snippet: Handling Song Requests

```javascript
// functions/index.js
const functions = require('firebase-functions');
const admin = require('firebase-admin');
admin.initializeApp();

exports.handleSongRequest = functions.firestore
.document('events/{eventId}/songRequests/{requestId}')
.onCreate(async (snap, context) => {
const request = snap.data();
const eventId = context.params.eventId;

  // Prioritize and add to setlist  const setlistRef = admin.firestore().collection('events').doc(eventId).collection('setlist');  await setlistRef.add({    songId: request.songId,    requestedBy: request.userId,    timestamp: admin.firestore.FieldValue.serverTimestamp(),  });  // Notify MEP  const mepId = request.mepId;  const mepToken = await getUserToken(mepId); // Implement getUserToken  await admin.messaging().sendToDevice(mepToken, {    notification: {      title: 'New Song Request',      body: `${request.songName} has been requested by a consumer.`,    },  });});

```

4.5. Integrate AI DJ Service
Develop backend AI algorithms for song mixing.
Ensure AI avoids offensive content and adheres to set constraints.
Provide API endpoints for frontend to interact with AI DJ.

5. Digital Transactions and Tipping

5.1. Integrate Digital Cash Applications
Supported Platforms: Money Pull Up, others as needed.
5.2. Implement Tipping Functionality
Enable consumers to tip MEPs during events.
Securely handle transactions via Firebase.
5.3. Develop "Money Pull Up" Integration
API integration for seamless tipping experience.
Ensure compliance with payment processing standards.
5.4. Example Code Snippet: Tipping Service
```javascript
// src/services/tippingService.js
import { firestore } from '../firebaseConfig';
export const sendTip = async (mepId, amount, userId) => {
try {
await firestore.collection('transactions').add({
mepId,
userId,
amount,
timestamp: firebase.firestore.FieldValue.serverTimestamp(),
type: 'tip',
});
// Optionally integrate with payment API here
} catch (error) {
console.error('Error sending tip:', error);
throw error;
}
};
```

6.1. Implement Social Sharing
Allow consumers to share event details on platforms like Facebook, Twitter, Instagram.
6.2. Develop Live Video Posting
Enable consumers to post live videos from events.
Store videos in Firebase Storage and link in Firestore.
6.3. Enable Event Reviews and Ratings
Allow consumers to leave reviews and ratings for events and MEPs.
6.4. Develop Follow and Notification System
Allow consumers to follow DJs.
Send notifications for DJ schedules and updates.
6.5. Example Code Snippet: Social Sharing Component
```javascript
// src/components/SocialShare.js
import React from 'react';
import { View, Button, Share } from 'react-native';
const SocialShare = ({ event }) => {
const onShare = async () => {
try {
await Share.share({
message: Join me at ${event.name} on ${event.date}! Download OneSong to participate.,
url: event.flyerUrl,
});
} catch (error) {
alert(error.message);
}
};
```
return (  `<View>`    `<Button onPress={onShare} title="Share Event" />`  `</View>`);
```
};
export default SocialShare;
```

7. Backend Development with Firebase

7.1. Configure Firestore Database
Define collections: users, events, songRequests, transactions, setlist, attendees.
7.2. Develop Firebase Cloud Functions
Song Request Handling: As shown in section 4.4.
AI DJ Processing: Trigger AI mixing upon setlist updates.
Notification Services: Send push notifications for various events.
7.3. Set Up Firestore Security Rules
Protect data access based on user roles (MEP vs. Consumer).
Ensure only authorized users can write to specific collections.
7.4. Implement Data Validation
Validate inputs on both frontend and backend.
Use Firebase Functions to enforce data integrity.

7.5. Example Firestore Security Rules

```javascript
rules_version = '2';
service cloud.firestore {
match /databases/{database}/documents {
// Users can read their own profile
match /users/{userId} {
allow read, write: if request.auth != null && request.auth.uid == userId;
}

  // MEPs can manage their own events  match /events/{eventId} {    allow read: if true;    allow write: if request.auth != null && request.auth.uid == resource.data.mepId;  }  // Consumers can create song requests  match /events/{eventId}/songRequests/{requestId} {    allow create: if request.auth != null;    allow read: if request.auth != null;    allow update, delete: if false;  }  // Transactions are secure  match /transactions/{transactionId} {    allow read, write: if request.auth != null;  }}

}
```

8. Frontend Development with React Native

8.1. Develop Reusable Components
EventCard: Display event details.
SongRequest: Interface for submitting song requests.
Profile: User profile display and editing.
Tipping: Tipping interface for consumers.
8.2. Implement Navigation
Set up React Navigation with stack navigators for different screens:
- Home
- Event Details
- Profile
- Create Event (MEP)
- Song Requests
- Tipping
- Settings
8.3. Develop Screens
Home Screen:
- Display list of active events.
- Search and filter functionality.
Event Details Screen:
- Show event information.
- Display song request countdown.
- Provide options for song requests and interactions.
Profile Screen:
- Display user information.
- Edit profile options.
Create Event Screen (MEP):
- Form to create new events.
- Upload flyer and media.
Song Requests Screen:
- Display current song requests.
- Allow MEPs to manage requests.
Tipping Screen:
- Interface to send tips to MEPs.
8.4. Implement State Management
Use Context API or Redux for managing global state.
Manage user authentication state, event data, song requests, etc.
8.5. Example Code Snippet: EventListScreen
```javascript
// src/screens/EventListScreen.js
import React, { useEffect, useState } from 'react';
import { View, FlatList, StyleSheet } from 'react-native';
import EventCard from '../components/EventCard';
import { getActiveEvents } from '../services/eventService';
const EventListScreen = () => {
const [events, setEvents] = useState([]);
```
useEffect(() => {  const fetchEvents = async () => {    const activeEvents = await getActiveEvents();    setEvents(activeEvents);  };  fetchEvents();}, []);return (  `<View style={styles.container}>`    \`<FlatList      data={events}      renderItem={({ item }) =>` `<EventCard event={item} />\`}      keyExtractor={(item) => item.id}    />  `</View>`);
```
};
const styles = StyleSheet.create({
container: {
flex: 1,
padding: 10,
},
});
export default EventListScreen;
```

9. AI-Assisted DJ Development

9.1. Design AI Mixing Algorithms
Analyze musical chords for seamless transitions.
Incorporate historical data on popular mixes.
Consider release dates and current trends.
9.2. Integrate AI with Backend
Develop API endpoints for AI to receive song requests and deliver mixed playlists.
Ensure AI processes requests in real-time or as per event scheduling.
9.3. Implement Offensive Content Filtering
Use content analysis to detect and exclude offensive music.
Allow MEPs to set parameters for acceptable content.
9.4. Example Workflow: AI DJ Integration

Receive Song Requests:
- AI fetches new song requests from Firestore.
Analyze and Prioritize:
- Assess song compatibility and prioritize based on predefined criteria.
Generate Mixed Playlist:
- Create a seamless mix adhering to musical and event constraints.
Update Setlist:
- Push the mixed playlist back to Firestore for MEPs to access.
Notify MEPs:
- Send notifications about the updated setlist.

10. Testing and Quality Assurance

10.1. Unit Testing
Tools: Jest, React Native Testing Library.
Tasks:
- Write tests for individual components (e.g., EventCard, SongRequest).
- Test utility functions and services (e.g., authService, eventService).
Example Test: EventCard Component
```javascript
// tests/EventCard.test.js
import React from 'react';
import { render } from '@testing-library/react-native';
import EventCard from '../src/components/EventCard';
test('renders event details correctly', () => {
const event = {
name: 'Live Concert',
date: '2024-12-25',
flyerUrl: 'https://example.com/flyer.jpg',
};
const { getByText } = render(<EventCard event={event} />);
expect(getByText('Live Concert')).toBeTruthy();
expect(getByText('2024-12-25')).toBeTruthy();
});
```
10.2. Integration Testing
Tools: Firebase Emulator Suite, Detox.
Tasks:
- Test interactions between frontend and backend (e.g., song request flow).
- Verify data synchronization and real-time updates.
10.3. User Acceptance Testing (UAT)
Tasks:
- Conduct testing sessions with actual MEPs and consumers.
- Gather feedback on usability and feature functionality.
- Iterate based on feedback to enhance user experience.
10.4. Performance Testing
Tasks:
- Ensure the app performs well under high load (e.g., multiple song requests).
- Optimize AI DJ processing for real-time performance.
10.5. Security Testing
Tasks:
- Verify Firestore security rules.
- Test authentication flows for vulnerabilities.
- Ensure data encryption and secure transactions.

11. Deployment Strategy

11.1. Prepare for Firebase Hosting
Configure Firebase Hosting for backend services.
Deploy Firebase Functions and Firestore rules.
11.2. Deploy Frontend to App Stores
iOS Deployment:
- Configure App Store Connect with app details, screenshots, and descriptions.
- Archive and upload the app using Xcode.
- Submit for App Store review.
Android Deployment:
- Configure Google Play Console with app details, screenshots, and descriptions.
- Generate signed APK/AAB.
- Upload and submit for Play Store review.
11.3. Continuous Integration and Deployment (CI/CD)
Set up CI/CD pipelines using tools like GitHub Actions or Bitrise.
Automate testing, building, and deployment processes.
11.4. Example Deployment Commands
```bash
Deploy Firebase Functions, Firestore rules, and Hosting
firebase deploy --only functions,firestore,hosting
```

12. Maintenance and Support

12.1. Monitoring and Analytics
Tools: Firebase Crashlytics, Google Analytics.
Tasks:
- Monitor app stability and crash reports.
- Track user engagement and feature usage.
12.2. Regular Updates
Schedule periodic updates for:
- Feature enhancements.
- Security patches.
- Performance optimizations.
12.3. User Support
In-App Support:
- Implement chat or email support channels.
Knowledge Base:
- Create FAQs and tutorials for users.
12.4. Feedback Mechanism
Allow users to submit feedback directly within the app.
Use feedback to prioritize future developments.

13. Documentation and Best Practices

13.1. Code Documentation
Comment complex code sections.
Maintain comprehensive README with setup instructions.
13.2. Maintain Coding Standards
Tools: ESLint, Prettier.
Tasks:
- Configure ESLint for linting.
- Set up Prettier for consistent code formatting.
Example ESLint Configuration:
```json
// .eslintrc.json
{
"env": {
"browser": true,
"es2021": true
},
"extends": [
"eslint:recommended",
"plugin:react/recommended",
"plugin:@typescript-eslint/recommended",
"prettier"
],
"parser": "@typescript-eslint/parser",
"parserOptions": {
"ecmaFeatures": {
"jsx": true
},
"ecmaVersion": 12,
"sourceType": "module"
},
"plugins": ["react", "@typescript-eslint"],
"rules": {
"react/prop-types": "off"
}
}
```
Example Prettier Configuration:
```json
// .prettierrc
{
"singleQuote": true,
"trailingComma": "all",
"printWidth": 80,
"tabWidth": 2
}
```
13.3. Maintain Modular Code Structure
Break down the application into reusable components and services.
Ensure separation of concerns for better maintainability.
13.4. Example: Service File with Comments
```javascript
// src/services/userService.js
import { firestore } from '../firebaseConfig';
/**
- Fetches user profile by user ID.
- @param {string} userId - The ID of the user.
- @returns {Promise<Object>} - User profile data.
  */
  export const getUserProfile = async (userId) => {
  try {
  const userDoc = await firestore.collection('users').doc(userId).get();
  if (userDoc.exists) {
  return { id: userDoc.id, ...userDoc.data() };
  } else {
  throw new Error('User not found');
  }
  } catch (error) {
  console.error('Error fetching user profile:', error);
  throw error;
  }
  };
```

14. Example Task Breakdown

Task: Develop Event Creation Interface for MEPs
Subtasks:
- Design UI mockups for event creation screen.
- Implement form fields (Event Name, Date, Location).
- Integrate flyer upload functionality using Firebase Storage.
- Add sections for Bio, Video Clips, and Short Mixes.
- Validate form inputs before submission.
- Connect frontend form to backend Firestore service.
- Test event creation flow for MEPs.
Task: Implement Song Request System
Subtasks:
- Design UI for song request input on consumer side.
- Create backend Firestore structure for song requests.
- Develop frontend component for submitting requests.
- Implement Firebase Cloud Function to handle new requests.
- Notify MEPs of new song requests via push notifications.
- Allow MEPs to manage and prioritize requests in dashboard.
- Test end-to-end song request functionality.

15. Security Considerations

15.1. Secure Authentication
Enforce strong password policies.
Implement multi-factor authentication if necessary.
15.2. Firestore Security Rules
Restrict data access based on user roles.
Validate data types and formats.
15.3. Data Encryption
Ensure all data transmitted is encrypted via HTTPS.
Use Firebase's built-in encryption for data at rest.
15.4. Regular Security Audits
Schedule periodic reviews of security rules.
Update dependencies to patch vulnerabilities.
15.5. Example Security Rule for Song Requests
```javascript
match /events/{eventId}/songRequests/{requestId} {
allow create: if request.auth != null && request.resource.data.songName is string && request.resource.data.userId == request.auth.uid;
allow read: if request.auth != null;
allow update, delete: if false;
}
```

16. Example Code Formatting and Best Practices

16.1. Use Modular Code Structure
Organize code into components, services, and utilities.
Example:
```
src/
├── components/
│ ├── EventCard.js
│ ├── SongRequest.js
│ └── SocialShare.js
├── services/
│ ├── authService.js
│ ├── eventService.js
│ └── tippingService.js
├── screens/
│ ├── HomeScreen.js
│ ├── EventListScreen.js
│ └── ProfileScreen.js
├── navigation/
│ └── AppNavigator.js
└── utils/
└── helpers.js
```
16.2. Consistent Naming Conventions
Use camelCase for variables and functions.
Use PascalCase for component names.
Example:
```javascript
// Correct Naming
const userProfile = {};
function fetchUserData() {}
const EventCard = () => {};
```
16.3. Commenting and Documentation
Provide clear comments for complex logic.
Maintain a comprehensive README with setup and usage instructions.
16.4. Example: Using Async/Await for Asynchronous Operations
```javascript
// src/services/eventService.js
import { firestore } from '../firebaseConfig';
/**
- Fetches active events from Firestore.
- @returns {Promise<Array>} - List of active events.
  */
  export const getActiveEvents = async () => {
  try {
  const snapshot = await firestore.collection('events').where('status', '==', 'active').get();
  const events = snapshot.docs.map(doc => ({ id: doc.id, ...doc.data() }));
  return events;
  } catch (error) {
  console.error('Error fetching active events:', error);
  return [];
  }
  };
```

17. Final Review and Launch Preparation

17.1. Conduct Final Code Review
Ensure all features are implemented as per specifications.
Verify code quality and adherence to best practices.
17.2. Prepare Marketing Materials
Design app icons and promotional graphics.
Create app store listings with descriptions and screenshots.
17.3. Final Testing
Perform a last round of testing to catch any remaining issues.
Ensure all integrations (e.g., AI DJ, tipping) function seamlessly.
17.4. Launch Strategy
Plan a launch date and coordinate marketing efforts.
Prepare for initial user onboarding and support.

18. Post-Launch Activities

18.1. Monitor App Performance
Use analytics to track user behavior and app usage.
Identify and address any performance bottlenecks.
18.2. Gather User Feedback
Encourage users to provide feedback and reviews.
Use feedback to prioritize feature updates and bug fixes.
18.3. Plan for Feature Enhancements
Based on user feedback, plan and implement new features.
Continuously innovate to keep the app relevant and engaging.

Conclusion

This comprehensive task list provides a detailed roadmap for developing the OneSong application using React Native for the frontend and Firebase for the backend.

Follow these structured tasks and adhere to best practices. Build a robust, secure, and user-friendly platform that bridges the gap between musical entertainment providers and consumers, enhancing the overall event experience.

stack:

React Native Firebase .cursorrules prompt file

Super Heavy

NEW

FastAPI .cursorrules prompt file guide

Code Style and Structure:

Follow PEP 8 guidelines for Python code style
Use meaningful variable and function names (snake_case for variables and functions, PascalCase for classes)
Keep functions small and focused on a single task
Use docstrings for modules, classes, and functions
Organize code into logical modules and packages
Use virtual environments for project isolation

Python-specific Conventions:

Prefer list comprehensions and generator expressions over map() and filter()
Use context managers (with statements) for resource management
Utilize decorators for cross-cutting concerns (e.g., logging, timing)
Leverage type hints for improved code readability and tooling support
Use f-strings for string formatting

Framework and API Development:

Use FastAPI as the primary framework for building high-performance APIs
Leverage FastAPI's automatic OpenAPI (Swagger) documentation
Utilize dependency injection for clean, testable code
Implement RESTful API design principles
Use Pydantic for data validation, serialization, and settings management
Define request and response models using Pydantic
Utilize Pydantic's BaseSettings for configuration management

Database and Data Modeling:

Use SQLModel, which combines SQLAlchemy core with Pydantic models
Leverage SQLModel's ability to use the same models for database tables and API schemas
Utilize SQLModel's async support for high-performance database operations
Implement database migrations using Alembic
Use connection pooling for efficient database connections
Implement proper indexing for frequently queried fields

Authentication and Security:

Implement JWT for stateless authentication
Use FastAPI's built-in security utilities
Use bcrypt for password hashing
Apply CORS policies using FastAPI's CORS middleware
Implement rate limiting for API endpoints (consider using FastAPI's dependencies for this)

Error Handling and Logging:

Use FastAPI's exception handlers for consistent error responses
Implement custom exception classes for application-specific errors
Use a logging framework (e.g., Python's built-in logging module)
Structure log messages for easy parsing and analysis

Frontend Development:

For server-side rendering, consider using FastAPI with Jinja2 templates
Implement responsive design using CSS frameworks (e.g., Bootstrap)
For single-page applications, use a JavaScript framework (e.g., React, Vue.js) that consumes your FastAPI backend

Testing:

Write unit tests using pytest
Implement integration tests for API endpoints using FastAPI's TestClient
Use factories (e.g., Factory Boy) for test data generation
Aim for high test coverage, especially for critical paths
Utilize Pydantic's parse_obj_as for easy test data creation

Asynchronous Processing:

Leverage FastAPI's asynchronous capabilities for concurrent processing
For background tasks, use FastAPI's background tasks feature or Celery for more complex scenarios
Implement message queues (e.g., RabbitMQ, Redis) for task management if needed

Deployment and DevOps:

Use Docker for containerization
Create optimized Dockerfiles for your FastAPI applications
Implement CI/CD pipelines (e.g., GitLab CI, GitHub Actions)
Use environment variables for configuration management
Utilize Pydantic's BaseSettings to load and validate environment variables
Implement health check endpoints for monitoring

Performance Optimization:

Leverage FastAPI's asynchronous capabilities for I/O-bound operations
Use caching mechanisms (e.g., Redis) for frequently accessed data
Implement database query optimization techniques with SQLModel
Profile code to identify and resolve bottlenecks

API Documentation:

Utilize FastAPI's automatic interactive API documentation (Swagger UI and ReDoc)
Keep API documentation up-to-date by maintaining accurate Pydantic models and FastAPI path operation functions

Version Control:

Use Git for version control
Implement feature branching and pull request workflows
Write meaningful commit messages

Dependencies Management

Use pip and requirements.txt for managing project dependencies
Consider using Poetry for more advanced dependency management

Remember to keep your code DRY (Don't Repeat Yourself), follow SOLID principles, and prioritize readability and maintainability in your Python full-stack development projects. Leverage the power of FastAPI, SQLModel, and Pydantic to create robust, type-safe, and high-performance applications.

stack:

FastAPI .cursorrules prompt file guide

Rohit Nair

NEW

Node.js MongoDB JWT Express React .cursorrules prompt file

Tech Stack:

Backend: Node.js with Express.js
Database: MongoDB with Mongoose ODM
Frontend: React.js (for admin panel, if required)
Authentication: JSON Web Tokens (JWT)
Version Control: Git
Deployment: Docker (optional)

Precision in User Requirements:
Strictly adhere to specified user flow and game rules.
Strategy: Summarize the pick submission process and outline the API endpoint and business logic in pseudocode before coding.
Strategic Planning with Pseudocode:
Begin each feature with detailed pseudocode.
Example: Provide pseudocode for the weekly scoring process, detailing steps from game result input to entry status updates.

Code Quality:
Ensure secure, efficient code following RESTful API best practices.
Implement proper error handling and input validation.

User Flow:
Users browse available Pools
Submit up to 3 Requests per Pool
Complete payment for Requests
Admin approves/rejects Requests
Approved Requests become Entries
Entry Management:
Each user can have up to 3 Entries per Pool
Entries are numbered 1, 2, 3
Picks are made and tracked separately for each Entry
Pick Management:
Users make Picks for each Entry separately
Picks can be updated until deadline (game start or 1PM Sunday of the current week of the pick)
Scoring and Ranking:
Picks scored after games complete
Win: Entry moves to next week
Loss: Entry eliminated from Pool
Each Entry ranked separately in Pool standings
Results and Standings:
Users view Picks/scores for each Entry separately
Pool standings show all Entries (multiple per User possible)
Pool members can view all Picks after scoring
Key Implementation Points:
Limit Requests to 3 per User per Pool
Track Requests and Entries separately (numbered 1, 2, 3)
Implement payment status tracking in Request model
Create Entry only after admin approval and payment completion
Admin interface for managing and approving Requests
Implement state transitions (Request: pending -> approved -> Entry created)

stack:

Node.js MongoDB JWT Express React .cursorrules prompt file

allxdamnxday

NEW

Kubernetes MkDocs Documentation .cursorrules prompt file

You are an expert Technical Writer with a deep understanding of cloud native technologies, Kubernetes, and technical documentation best practices. You excel at creating clear, concise, and user-friendly documentation using Markdown and MkDocs.

You always use the latest stable versions of Kubernetes, cloud native tools, and MkDocs. You're familiar with the latest features, best practices, and trends in cloud native architecture, containerization, and orchestration.

Documentation Style and Structure:

Write clear, concise, and technically accurate content in Markdown.
Use a logical and hierarchical structure for documentation.
Employ consistent formatting and style throughout the documentation.
Use descriptive headings and subheadings for easy navigation.
Include relevant code snippets, command-line examples, and configuration files where appropriate.

Cloud Native and Kubernetes Expertise:

Accurately explain complex cloud native concepts and Kubernetes components.
Provide clear instructions for deploying and managing applications on Kubernetes.
Document best practices for containerization, orchestration, and microservices architecture.
Explain concepts like pods, services, deployments, StatefulSets, and other Kubernetes resources.
Cover advanced topics such as custom resource definitions (CRDs), operators, and service meshes.

MkDocs Usage:

Structure documentation projects using MkDocs best practices.
Utilize MkDocs metadata for enhanced navigation and search functionality.
Implement proper use of MkDocs plugins for extended features.
Create a well-organized mkdocs.yml file for project configuration.

Content Creation:

Develop user guides, tutorials, API references, and conceptual documentation.
Create step-by-step instructions for common tasks and troubleshooting guides.
Write clear and concise release notes and changelog entries.
Develop architecture diagrams and flowcharts to illustrate complex systems.

Technical Accuracy and Usability:

Ensure all technical information is accurate and up-to-date.
Provide context and explanations for technical concepts and terminology.
Include practical examples and use cases to illustrate concepts.
Anticipate and address common user questions and pain points.

Documentation Best Practices:

Use consistent terminology throughout the documentation.
Implement a style guide for maintaining consistency across different authors.
Include a glossary of terms for complex or domain-specific vocabulary.
Properly link related topics and sections within the documentation.

Metadata and SEO:

Use appropriate metadata in Markdown files for improved SEO and discoverability.
Implement effective use of tags and categories in MkDocs.
Create descriptive and SEO-friendly page titles and descriptions.

Collaboration and Version Control:

Use Git for version control of documentation.
Implement a clear process for documentation reviews and updates.
Collaborate effectively with developers and other technical team members.

Other Rules to follow:

Follow the user's requirements carefully & to the letter.
First outline the structure of the documentation before writing content.
Always provide accurate, up-to-date, and comprehensive information.
Focus on clarity and user-friendliness over technical jargon.
Fully cover all requested topics and functionality.
Leave no gaps in explanations or instructions.
Be sure to reference specific Kubernetes resources, APIs, or tools when appropriate.
Be concise while ensuring all necessary information is included.
If you're unsure about a technical detail, say so instead of guessing.

Don't be lazy, provide thorough and accurate documentation for all requested topics and features.

stack:

cloud native technologies

Kubernetes MkDocs Documentation .cursorrules prompt file

samzong

NEW

Astro TypeScript .cursorrules prompt file

{
  "rules": {
   "commit_message_guidelines": {
    "description": "Guidelines for creating conventional commit messages.",
    "format": {
     "description": "The format for commit messages using the conventional commits spec.",
     "body": "[optional scope]: \n\n[optional body]\n\n[optional footer(s)]"
    },
    "enabled": true,
    "rules": [
     {
      "description": "Always suggest a conventional commit with a type and optional scope in lowercase letters."
     },
     {
      "description": "Keep the commit message concise and within 60 characters."
     },
     {
      "description": "Ensure the commit message is ready to be pasted into the terminal without further editing."
     },
     {
      "description": "Provide the full command to commit, not just the message."
     }
    ],
    "examples": [
     {
      "prompt": "<diff_context> /commit",
      "response": "git commit -m 'feat: add responsive navbar with TailwindCSS'"
     }
    ]
   },
   "development_guidelines": {
    "description": "Guidelines for developing code with Astro, TypeScript, and TailwindCSS.",
    "enabled": true,
    "rules": [
     {
      "description": "Enforce strict TypeScript settings, ensuring type safety across the project."
     },
     {
      "description": "Use TailwindCSS for all styling, keeping the utility-first approach in mind."
     },
     {
      "description": "Ensure Astro components are modular, reusable, and maintain a clear separation of concerns."
     }
    ]
   },
   "coding_style": {
    "description": "Guidelines for maintaining consistent coding style.",
    "enabled": true,
    "rules": [
     {
      "description": "Code must start with path/filename as a one-line comment."
     },
     {
      "description": "Comments should describe purpose, not effect."
     },
     {
      "description": "Prioritize modularity, DRY principles, and performance."
     }
    ]
   },
   "custom_slash_commands": {
    "description": "Custom slash commands.",
    "enabled": true,
    "commands": [
     {
      "name": "/commit",
      "description": "Generate a Git commit message using the conventional commits spec.",
      "enabled": true
     }
    ]
   }
  }
}

stack:

Astro TypeScript .cursorrules prompt file

Jaime Aleman

NEW

Node.js MongoDB .cursorrules prompt file tutorial

Tech Stack:

Code Quality:
Ensure secure, efficient code following RESTful API best practices.
Implement proper error handling and input validation.

stack:

Node.js MongoDB .cursorrules prompt file tutorial

allxdamnxday

NEW

Go Backend Scalability .cursorrules prompt file

You are an AI Pair Programming Assistant with extensive expertise in backend software engineering. Your knowledge spans a wide range of technologies, practices, and concepts commonly used in modern backend systems. Your role is to provide comprehensive, insightful, and practical advice on various backend development topics.

Your areas of expertise include, but are not limited to:

1. Database Management (SQL, NoSQL, NewSQL)
2. API Development (REST, GraphQL, gRPC)
3. Server-Side Programming (Go, Rust, Java, Python, Node.js)
4. Performance Optimization
5. Scalability and Load Balancing
6. Security Best Practices
7. Caching Strategies
8. Data Modeling
9. Microservices Architecture
10. Testing and Debugging
11. Logging and Monitoring
12. Containerization and Orchestration
13. CI/CD Pipelines
14. Docker and Kubernetes
15. gRPC and Protocol Buffers
16. Git Version Control
17. Data Infrastructure (Kafka, RabbitMQ, Redis)
18. Cloud Platforms (AWS, GCP, Azure)

When responding to queries:

1. Begin with a section where you:
  - Analyze the query to identify the main topics and technologies involved
  - Consider the broader context and implications of the question
  - Plan your approach to answering the query comprehensively

2. Provide clear, concise explanations of backend concepts and technologies
3. Offer practical advice and best practices for real-world scenarios
4. Share code snippets or configuration examples when appropriate, using proper formatting and syntax highlighting
5. Explain trade-offs between different approaches when multiple solutions exist
6. Consider scalability, performance, and security implications in your recommendations
7. Reference official documentation or reputable sources when needed, but note that you don't have access to real-time information
8. End your response with an section that summarizes the key points and provides a direct answer to the query

Your goal is to help users understand, implement, and optimize backend systems while adhering to industry best practices and standards. Always consider factors such as scalability, reliability, maintainability, and security in your recommendations.

If a query is unclear or lacks necessary details, ask for clarification before providing an answer. If a question is outside the scope of backend development, politely inform the user and offer to assist with related backend topics if possible.

Here's an example of how to structure your response:

User: How can I implement a gRPC service in Go that interacts with a PostgreSQL database?

You:

To answer this query, I need to consider:
1. The basics of gRPC and Protocol Buffers
2. Go programming for gRPC server implementation
3. Database interaction using Go's database/sql package or an ORM
4. Best practices for structuring a gRPC service
5. Error handling and data validation

I'll provide a step-by-step guide with code examples to illustrate the implementation.

To implement a gRPC service in Go that interacts with a PostgreSQL database, follow these steps:

1. Define your Protocol Buffer messages and service:
Create a file named `service.proto`:

  ```protobuf
  syntax = "proto3";
  package myservice;
  option go_package = "./pb";

  message User {
   int32 id = 1;
   string name = 2;
   string email = 3;
  }

  message GetUserRequest {
   int32 id = 1;
  }

  service UserService {
   rpc GetUser(GetUserRequest) returns (User) {}
  }
  ```

2. Generate Go code from the Proto file:
  ```
  protoc --go_out=. --go-grpc_out=. service.proto
  ```

3. Implement the gRPC server in Go:
```go
package main

  import (
   "context"
   "database/sql"
   "log"
   "net"

   "google.golang.org/grpc"
   "github.com/lib/pq"
   pb "your_project/pb"
  )

  type server struct {
   pb.UnimplementedUserServiceServer
   db *sql.DB
  }

  func (s *server) GetUser(ctx context.Context, req *pb.GetUserRequest) (*pb.User, error) {
   var user pb.User
   err := s.db.QueryRow("SELECT id, name, email FROM users WHERE id = $1", req.Id).Scan(&user.Id, &user.Name, &user.Email)
   if err != nil {
    return nil, err
   }
   return &user, nil
  }

  func main() {
   // Connect to PostgreSQL
   db, err := sql.Open("postgres", "postgresql://username:password@localhost/dbname?sslmode=disable")
   if err != nil {
    log.Fatalf("Failed to connect to database: %v", err)
   }
   defer db.Close()

   // Create gRPC server
   s := grpc.NewServer()
   pb.RegisterUserServiceServer(s, &server{db: db})

   // Start listening
   lis, err := net.Listen("tcp", ":50051")
   if err != nil {
    log.Fatalf("Failed to listen: %v", err)
   }
   log.Println("Server listening on :50051")
   if err := s.Serve(lis); err != nil {
    log.Fatalf("Failed to serve: %v", err)
   }
  }
  ```

This example demonstrates:
- Defining a simple gRPC service using Protocol Buffers
- Implementing the service in Go
- Connecting to a PostgreSQL database
- Handling a basic database query within a gRPC method

Remember to handle errors properly, implement proper validation, and consider using an ORM like GORM for more complex database interactions. Also, ensure you're following best practices for security, such as using prepared statements to prevent SQL injection.

By following this structure and guidelines, you'll provide comprehensive and practical assistance for backend software engineering queries.

stack:

Go Backend Scalability .cursorrules prompt file

Will Cygan

NEW

Python GitHub Setup .cursorrules prompt file

{
"general": {
"coding_style": {
"language": "Python",
"use_strict": true,
"indentation": "4 spaces",
"max_line_length": 120,
"comments": {
"style": "# for single-line, ''' for multi-line",
"require_comments": true
}
},
"naming_conventions": {
"variables": "snake_case",
"functions": "snake_case",
"classes": "PascalCase",
"interfaces": "PascalCase",
"files": "snake_case"
},
"error_handling": {
"prefer_try_catch": true,
"log_errors": true},
"testing": {
"require_tests": true,
"test_coverage": "80%",
"test_types": ["unit", "integration"]
},
"documentation": {
"require_docs": true,
"doc_tool": "docstrings",
"style_guide": "Google Python Style Guide"
},
"security": {
"require_https": true,
"sanitize_inputs": true,
"validate_inputs": true,
"use_env_vars": true
},
"configuration_management": {
"config_files": [".env"],
"env_management": "python-dotenv",
"secrets_management": "environment variables"
},
"code_review": {
"require_reviews": true,
"review_tool": "GitHub Pull Requests",
"review_criteria": ["functionality", "code quality", "security"]
},
"version_control": {
"system": "Git",
"branching_strategy": "GitHub Flow",
"commit_message_format": "Conventional Commits"
},
"logging": {
  "logging_tool": "Python logging module",
  "log_levels": ["debug", "info", "warn", "error"],
  "log_retention_policy": "7 days"
  },
  "monitoring": {
  "monitoring_tool": "Not specified",
  "metrics": ["file processing time", "classification accuracy", "error rate"]
  },
  "dependency_management": {
  "package_manager": "pip",
  "versioning_strategy": "Semantic Versioning"
  },
  "accessibility": {
  "standards": ["Not applicable"],
  "testing_tools": ["Not applicable"]
  },
  "internationalization": {
  "i18n_tool": "Not applicable",
  "supported_languages": ["English"],
  "default_language": "English"
  },
  "ci_cd": {
  "ci_tool": "GitHub Actions",
  "cd_tool": "Not specified",
  "pipeline_configuration": ".github/workflows/main.yml"
  },
  "code_formatting": {
  "formatter": "Black",
  "linting_tool": "Pylint",
  "rules": ["PEP 8", "project-specific rules"]
  },
  "architecture": {
    "patterns": ["Modular design"],
    "principles": ["Single Responsibility", "DRY"]
    }
    },
    "project_specific": {
    "use_framework": "None",
    "styling": "Not applicable",
    "testing_framework": "pytest",
    "build_tool": "setuptools",
    "deployment": {
    "environment": "Local machine",
    "automation": "Not specified",
    "strategy": "Manual deployment"
    },
    "performance": {
    "benchmarking_tool": "Not specified",
    "performance_goals": {
    "response_time": "< 5 seconds per file",
    "throughput": "Not specified",
    "error_rate": "< 1%"
    }
    }
    },
    "context": {
      "codebase_overview": "Python-based file organization tool using AI for content analysis and classification",
      "libraries": ["watchdog", "spacy", "PyPDF2", "python-docx", "pandas", "beautifulsoup4", "transformers", "scikit-learn", "joblib", "python-dotenv", "torch", "pytest", "shutil", "logging", "pytest-mock"],
      "coding_practices": {
      "modularity": true,
      "DRY_principle": true,
      "performance_optimization": true
      }
      },
      "behavior": {
      "verbosity": {
      "level": 2,
      "range": [0, 3]
      },
      "handle_incomplete_tasks": "Provide partial solution and explain limitations",
      "ask_for_clarification": true,
      "communication_tone": "Professional and concise"
      }
      }