hailo-apps / rules
Cursor rule506 starsChanged 7 months agoMITView on GitHub
Skill: Camera Setup & Management
We split this hl-camera.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 125
Always convert to RGB before sending to VLM: cv2.cvtColor(frame, cv2.COLOR_BGR2RGB)
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
---
description: "Skill: Camera Setup & Management"
alwaysApply: false
---
# Skill: Camera Setup & Management
> Configure and manage camera sources for Hailo applications.
## When to Use This Skill
- User needs to set up a **USB camera**, **RPi camera**, or **RTSP stream**
- User wants to **discover available cameras** on the system
- User needs camera **configuration** (resolution, FPS, format)
## Camera Type Detection
```python
from hailo_apps.python.core.gstreamer.gstreamer_helper_pipelines import get_source_type
from hailo_apps.python.core.common.defines import USB_CAMERA, RPI_NAME_I
source_type = get_source_type(video_source)
# Returns: "usb", "rpi", "file", "rtsp", "ximage"
```
## USB Camera Discovery
```python
from hailo_apps.python.core.common.camera_utils import get_usb_video_devices
devices = get_usb_video_devices()
# Returns: list of device indices, e.g., [0, 2]
# Uses udevadm to enumerate real cameras (filters out virtual devices)
```
## Camera Initialization Patterns
### USB Camera (OpenCV)
```python
import cv2
camera_index = get_usb_video_devices()[0] # First available USB camera
cap = cv2.VideoCapture(camera_index)
cap.set(cv2.CAP_PROP_FRAME_WIDTH, 640)
cap.set(cv2.CAP_PROP_FRAME_HEIGHT, 480)
cap.set(cv2.CAP_PROP_FPS, 30)
# Read frames
ret, frame = cap.read() # frame is BGR numpy array
# Cleanup
cap.release()
```
### RPi Camera (Picamera2)
```python
from picamera2 import Picamera2
picam2 = Picamera2()
config = picam2.create_preview_configuration(
main={"size": (640, 480), "format": "RGB888"}
)
picam2.configure(config)
picam2.start()
# Read frames
frame = picam2.capture_array() # frame is RGB numpy array (note: not BGR!)
# Cleanup
picam2.stop()
```
### RTSP Stream
```python
# Replace with your camera's actual RTSP URL and credentials
cap = cv2.VideoCapture("rtsp://<username>:<password>@<camera-ip>:554/stream")
```
## CLI Source Selection
The standard parser handles source selection:
```bash
# USB camera
python3 my_app.py --input usb
# RPi camera
python3 my_app.py --input rpi
# Video file
python3 my_app.py --input /path/to/video.mp4
# RTSP
python3 my_app.py --input rtsp://camera_ip:554/stream
```
## Camera Abstraction Pattern
For apps that need to support multiple camera types cleanly:
```python
def init_camera(source, source_type):
"""Initialize camera and return (get_frame, cleanup, name) tuple."""
if source_type == "rpi":
from picamera2 import Picamera2
picam2 = Picamera2()
config = picam2.create_preview_configuration(main={"size": (640, 480), "format": "RGB888"})
picam2.configure(config)
picam2.start()
return (lambda: picam2.capture_array(), lambda: picam2.stop(), "RPi")
else:
cap = cv2.VideoCapture(source)
cap.set(cv2.CAP_PROP_FRAME_WIDTH, 640)
cap.set(cv2.CAP_PROP_FRAME_HEIGHT, 480)
return (
lambda: (lambda r: r[1] if r[0] else None)(cap.read()),
lambda: cap.release(),
"USB"
)
```
## Important Notes
- USB cameras return **BGR** frames (OpenCV default)
- RPi cameras can return **RGB** frames (with `format="RGB888"`)
- Always convert to RGB before sending to VLM: `cv2.cvtColor(frame, cv2.COLOR_BGR2RGB)`
- VLM expects **336×336** images — use `Backend.convert_resize_image()`
- Camera release is critical — always clean up in `finally` blocks
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository65 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/core-framework.mdcCursor rule
- .cursor/rules/gen-ai-apps.mdcCursor rule
- .cursor/rules/hailo-global.mdcCursor rule
- .cursor/rules/hl-build-agent-app.mdcCursor rule
- .cursor/rules/hl-build-llm-app.mdcCursor rule
- .cursor/rules/hl-build-pipeline-app.mdcCursor rule
- .cursor/rules/hl-build-standalone-app.mdcCursor rule
- .cursor/rules/hl-build-vlm-app.mdcCursor rule
- .cursor/rules/hl-build-voice-app.mdcCursor rule
- .cursor/rules/hl-event-detection.mdcCursor rule
- .cursor/rules/hl-model-management.mdcCursor rule
- .cursor/rules/hl-monitoring.mdcCursor rule
- .cursor/rules/hl-plan-and-execute.mdcCursor rule
- .cursor/rules/hl-validate.mdcCursor rule
- .cursor/rules/inst-agent-protocols.mdcCursor rule
- .cursor/rules/inst-architecture.mdcCursor rule
- .cursor/rules/inst-coding-standards.mdcCursor rule
- .cursor/rules/inst-gen-ai-development.mdcCursor rule
- .cursor/rules/inst-gstreamer-pipelines.mdcCursor rule
- .cursor/rules/inst-orchestration.mdcCursor rule
- .cursor/rules/inst-testing-patterns.mdcCursor rule
- .cursor/rules/memory-camera_and_display.mdcCursor rule
- .cursor/rules/memory-common_pitfalls.mdcCursor rule
- .cursor/rules/memory-gen_ai_patterns.mdcCursor rule
- .cursor/rules/memory-hailo_platform_api.mdcCursor rule
- .cursor/rules/memory-MEMORY.mdcCursor rule
- .cursor/rules/memory-pipeline_optimization.mdcCursor rule
- .cursor/rules/pipeline-apps.mdcCursor rule
- .cursor/rules/prompt-new-agent-tool.mdcCursor rule
- .cursor/rules/prompt-new-llm-app.mdcCursor rule
- .cursor/rules/prompt-new-pipeline-app.mdcCursor rule
- .cursor/rules/prompt-new-pose-game.mdcCursor rule
- .cursor/rules/prompt-new-standalone-app.mdcCursor rule
- .cursor/rules/prompt-new-vlm-variant.mdcCursor rule
- .cursor/rules/prompt-new-voice-app.mdcCursor rule
- .cursor/rules/prompt-orchestrated-build.mdcCursor rule
- .cursor/rules/standalone-apps.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/toolset-core-framework-api.mdcCursor rule
- .cursor/rules/toolset-gen-ai-utilities.mdcCursor rule
- .cursor/rules/toolset-gstreamer-elements.mdcCursor rule
- .cursor/rules/toolset-hailort-api.mdcCursor rule
- .cursor/rules/toolset-pose-keypoints.mdcCursor rule
- .cursor/rules/toolset-vlm-backend-api.mdcCursor rule
- .cursor/rules/toolset-yolo-coco-classes.mdcCursor rule
- hl-build-agent-appSkill
- hl-build-llm-appSkill
- hl-build-pipeline-appSkill
- hl-build-standalone-appSkill
- hl-build-vlm-appSkill
- hl-build-voice-appSkill
- hl-cameraSkill
- hl-event-detectionSkill
- hl-model-managementSkill
- hl-monitoringSkill
- hl-plan-and-executeSkill
- hl-validateSkill
- hl-build-agent-appSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

