agentleFS
hailo-aihailo-ai/hailo-apps/.cursor/rules/pipeline-apps.mdc

hailo-apps / rules

Cursor rule506 starsChanged 7 months agoMITView on GitHub

You are working on a GStreamer pipeline application. Read these files before making changes (paths relative to .hailo/):

We split this pipeline-apps.mdc into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 are 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.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read these files before making changes (paths relative to .hailo/):

    line 12
  2. Very specific:

    If camera input: memory/camera_and_display.md, skills/hl-camera.md

    line 23
  3. Very specific:

    If adding models: skills/hl-model-management.md, toolsets/hailort-api.md

    line 24
  4. Very specific:

    Use get_pipeline_parser() for CLI arguments

    line 29
  5. Very specific:

    Use SHARED_VDEVICE_GROUP_ID for hailonet elements

    line 31
  6. Very specific:

    Always resolve HEF paths with resolve_hef_path(path, app_name, arch)

    line 32

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
pipeline-apps.mdc
---
globs: ["**/pipeline_apps/**"]
alwaysApply: false
---

# Pipeline Apps — Contextual Instructions

You are working on a **GStreamer pipeline application**.

## Required Context Files

Read these files before making changes (paths relative to `.hailo/`):

- `instructions/gstreamer-pipelines.md` — Pipeline composition, fragments, architecture
- `instructions/coding-standards.md` — Import rules, logging, HEF resolution
- `toolsets/gstreamer-elements.md` — All Hailo + standard GStreamer elements
- `toolsets/core-framework-api.md` — GStreamerApp, buffer_utils, parsers
- `memory/pipeline_optimization.md` — Bottleneck patterns, queue tuning, scheduler fixes
- `memory/common_pitfalls.md` — Known anti-patterns to avoid

## Additional Context (load if relevant)

- If camera input: `memory/camera_and_display.md`, `skills/hl-camera.md`
- If adding models: `skills/hl-model-management.md`, `toolsets/hailort-api.md`

## Key Patterns for Pipelines

- Subclass `GStreamerApp` and implement `get_pipeline_string()`
- Use `get_pipeline_parser()` for CLI arguments
- Compose pipelines using helper functions from `gstreamer_helper_pipelines.py`
- Use `SHARED_VDEVICE_GROUP_ID` for hailonet elements
- Always resolve HEF paths with `resolve_hef_path(path, app_name, arch)`
- Register new apps in `hailo_apps/python/core/common/defines.py`

## Reference Implementations

- Detection: `hailo_apps/python/pipeline_apps/detection/`
- Pose: `hailo_apps/python/pipeline_apps/pose_estimation/`
- Instance segmentation: `hailo_apps/python/pipeline_apps/instance_segmentation/`
- Pipeline helpers: `hailo_apps/python/core/gstreamer/gstreamer_helper_pipelines.py`

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.