source▌

Build Holoscan SDK from source via the in-tree ./run script. Use only when published packages don't meet the user's needs.

Reference docs for writing Python code against the browser-use library. Read the relevant file based on what the user needs.

Create maintainer-friendly pull requests while avoiding 16 common rejection mistakes. \n \n Prevents personal development artifacts (SESSION.md, planning docs, debug screenshots, temp test files) from being committed using a pre-PR check script \n Enforces three critical workflow rules: always use feature branches, test thoroughly before submitting, and keep PRs focused on a single change under 400 lines \n Provides templates and guides for PR descriptions using What/Why/How structure, conventio

Guides open source as a commercialization path: build community and trust first, monetize later. Many products use open source for early growth (Cursor from VSCode, Llama, Qwen, Dify) and later commercialize via managed services or open core. For GitHub (SEO, GEO, README, Awesome lists), see github. For directory submission (DevHunt, Awesome lists), see directory-submission.

ln-645-open-source-replacer

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.