Copilot instructions

1---
2description: AI rules derived by SpecStory from the project AI interaction history
3globs: *
4---
5 
6## Headers
7 
8## PROJECT DOCUMENTATION & CONTEXT SYSTEM
9 
10## TECH STACK
11 
12## CODING STANDARDS
13 
14### Environment Variables
15 
16*   Avoid direct use of `process.env` or `import.meta.env` in the main code.
17*   Use a configuration module or utility function to safely access environment variables.
18*   Implement error handling to ensure that required environment variables are set. For example:
19 
20```typescript
21    function getEnvVar(name: string): string {
22      const value = process.env[name];
23      if (!value) {
24        throw new Error(`${name} environment variable is not set.`);
25      }
26      return value;
27    }
28 
29    const GOOGLE_API_KEY = getEnvVar("GOOGLE_API_KEY");
30```
31*   All usages of environment variables must go through the designated utility function (e.g., `getEnvVar`). Direct access via `process.env` or `import.meta.env` elsewhere in the code is prohibited. Only the designated utility function (e.g. `getEnvVar`) should directly access `process.env`.
32*   In Node.js environments, use `process.env` instead of `import.meta.env` to access environment variables.
33*   When using external libraries, ensure that API keys or other sensitive configuration parameters are not passed directly as properties in constructors, if the library does not expect it. Instead, rely on environment variables or the library's recommended approach for authentication.
34*   When using the `ExaSearchResults` class from the `@langchain/exa` library, the API key should not be passed directly to the constructor. Instead, ensure the `EXA_API_KEY` environment variable is set, and instantiate `ExaSearchResults` without the `apiKey` argument in the constructor. The library automatically uses the environment variable if set.
35 
36## DEBUGGING
37 
38## WORKFLOW & RELEASE RULES