Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -22,10 +22,11 @@ node_modules

# IDE - VSCode
.vscode/*
!.vscode/extensions.json
!.vscode/launch.json
!.vscode/mcp.json
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json

# misc
/.sass-cache
Expand Down
10 changes: 10 additions & 0 deletions .mcp.json
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,16 @@
"type": "stdio",
"command": "npx",
"args": ["nx-mcp"]
},
"context7": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@upstash/context7-mcp@latest"]
},
"chrome-devtools": {
"type": "stdio",
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}
5 changes: 3 additions & 2 deletions .prettierignore
Original file line number Diff line number Diff line change
Expand Up @@ -29,10 +29,11 @@ node_modules

# IDE - VSCode
.vscode/*
!.vscode/extensions.json
!.vscode/launch.json
!.vscode/mcp.json
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json

# misc
/.sass-cache
Expand Down
16 changes: 16 additions & 0 deletions .vscode/mcp.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
{
"servers": {
"nx-mcp": {
"command": "npx",
"args": ["nx-mcp"]
},
"context7": {
"command": "npx",
"args": ["-y", "@upstash/context7-mcp@latest"]
},
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}
27 changes: 27 additions & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,3 +16,30 @@

- Prefer `undefined` over `null` when representing missing values unless an API explicitly requires `null`.
- Prefer chaining Lexical `append` calls inside the final `$getRoot().append(...)` when setting up document structure in tests so the hierarchy is readable at a glance.

# Context 7 Library Documentation

The Context 7 MCP server is available for looking up library documentation and code examples. **No API key is required.**

## Using Context 7 to look up library documentation

When you need documentation for a library or package:

1. Use `mcp_context7_resolve-library-id` to find the library ID:

```
mcp_context7_resolve-library-id with libraryName="Library Name"
```

This will return matching libraries with their Context7-compatible IDs (format: `/org/project`), descriptions, code snippet counts, and trust scores.

2. Once you have the library ID, use `mcp_context7_get-library-docs` to fetch documentation:
```
mcp_context7_get-library-docs with context7CompatibleLibraryID="/org/project"
```
You can also specify a `topic` parameter to focus on specific aspects (e.g., "hooks", "routing", "components").

## Example: Looking up Lexical documentation

- Resolve: Find Lexical → returns `/facebook/lexical` (official, trust score 9.2)
- Fetch: Get docs for `/facebook/lexical` → Returns 661 lines of documentation with code examples for editor creation, React setup, state management, etc.
27 changes: 27 additions & 0 deletions CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -191,3 +191,30 @@ When working with scripture data:

- Prefer `undefined` over `null` when representing missing values unless an API explicitly requires `null`.
- Prefer chaining Lexical `append` calls inside the final `$getRoot().append(...)` when setting up document structure in tests so the hierarchy is readable at a glance.

# Context 7 Library Documentation

The Context 7 MCP server is available for looking up library documentation and code examples. **No API key is required.**

## Using Context 7 to look up library documentation

When you need documentation for a library or package:

1. Use `mcp_context7_resolve-library-id` to find the library ID:

```
mcp_context7_resolve-library-id with libraryName="Library Name"
```

This will return matching libraries with their Context7-compatible IDs (format: `/org/project`), descriptions, code snippet counts, and trust scores.

2. Once you have the library ID, use `mcp_context7_get-library-docs` to fetch documentation:
```
mcp_context7_get-library-docs with context7CompatibleLibraryID="/org/project"
```
You can also specify a `topic` parameter to focus on specific aspects (e.g., "hooks", "routing", "components").

## Example: Looking up Lexical documentation

- Resolve: Find Lexical → returns `/facebook/lexical` (official, trust score 9.2)
- Fetch: Get docs for `/facebook/lexical` → Returns 661 lines of documentation with code examples for editor creation, React setup, state management, etc.
Loading