AI SummaryGiGL provides essential Cursor coding standards emphasizing explicit naming conventions and fail-fast error handling to improve code readability and maintainability. Developers working with graph neural networks and large-scale ML projects benefit from these foundational best practices.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "GiGL — Cursor Rules" prompt rules to my project. Repository: https://github.com/Snapchat/GiGL Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Core coding standards - explicit naming and fail-fast error handling
Verify Features Before Submitting
Once a feature is code complete, verify it works by running the type checker and relevant tests. Do not skip these steps or suppress errors with workarounds like # type: ignore.
Use Explicit Variable Names
Never abbreviate variable names unless the abbreviation is universally understood in the domain (e.g. i for a loop index, e in a catch block, url, id, config). Shortened names reduce readability and make code harder to search and refactor. It is ok to shorten or abbreviate names to avoid shadowing other variables. `python
BAD - unclear abbreviation
for nt in node_types: et = edge_type_map.get(nt)
GOOD - explicit and readable
for node_type in node_types: edge_type = edge_type_map[node_type] ` When in doubt, spell it out.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts