Add HOL (Hashgraph Online) TypeScript SDK cursor rules

[kantorcodes]

Adding cursor rules for Hashgraph Online (HOL) - a TypeScript SDK for building AI agents on the Hedera network.

The .cursorrules file includes:

• Technology stack (TypeScript, Node.js 20+, pnpm, Jest)

• HOL SDK patterns (RegistryBrokerClient, agent search, chat)

• Code quality standards

• Testing patterns

• Website: https://hol.org

• GitHub: https://github.com/hashgraph-online/standards-sdk

• NPM: @hashgraphonline/standards-sdk

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new HOL (Hedera TypeScript SDK) cursorrules document and references in the README describing TypeScript HOL development rules, SDK usage examples (RegistryBrokerClient flows), coding standards, testing workflow, validation checklist, and environment configuration.

Changes

Cohort / File(s)	Summary
README Updates README.md	Adds a new HOL (Hedera TypeScript SDK) entry to the Contents and to the Backend / Full-Stack section linking to the new cursorrules file.
HOL Cursor Rules (new) rules/hol-hedera-typescript-cursorrules-prompt-file/.cursorrules	New comprehensive HOL TypeScript development guide covering tech stack, TypeScript and React conventions, RegistryBrokerClient SDK usage examples (init, search, UAID resolution, registration, chat, stats, vector search), testing requirements and workflow, validation checklist, env configuration, and resources.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• PatrickJS

Poem

🐰 I hopped through rules and left a clue,
TypeScript paths and HOL in view,
Registry calls and tests in tune,
I danced beneath the coding moon,
✨📜

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding cursor rules for HOL (Hashgraph Online) TypeScript SDK, which directly corresponds to the new .cursorrules file and README entries introduced in this PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@README.md`:
- Line 133: The README entry for "HOL (Hedera TypeScript SDK)" currently
contains an external link to Hashgraph Online (https://hol.org); update the
README.md entry so the visible link is only the relative path to
./rules/hol-hedera-typescript-cursorrules-prompt-file/.cursorrules and remove
the external https://hol.org URL from the same line (you may instead add that
external reference inside the .cursorrules file if needed), ensuring the entry
follows the project guideline of using relative links.

In `@rules/hol-hedera-typescript-cursorrules-prompt-file/.cursorrules`:
- Around line 36-41: Examples in .cursorrules violate the "No console.log - use
Logger from standards-sdk" rule by showing console.log in multiple example
blocks; replace every console.log example usage with the Logger API from
`@hashgraphonline/standards-sdk`, add a consistent logger instantiation (single
named logger used across examples), and switch calls to the appropriate logger
methods (debug/info/warn/error) and structured key/value logging; update the
example snippets referenced (the blocks currently showing console.log) to
import/instantiate Logger and use logger.info/debug/etc with the same contextual
message structure to match the rule.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@rules/hol-hedera-typescript-cursorrules-prompt-file/.cursorrules`:
- Around line 83-95: The examples call client.resolveUaid (and other client.*
methods) but never show how client is created; update each snippet to initialize
a RegistryBrokerClient instance (e.g., create and configure a const client = new
RegistryBrokerClient(...) or equivalent) before using it so the examples are
runnable—specifically add the RegistryBrokerClient instantiation and any minimal
config/credentials required just above usages of client (locations referencing
resolveUaid, resolveAgent, or any other client.method) and ensure the variable
name remains client to match existing calls.