Code Repository Search & Analysis Environment
This skill configures Cursor for efficient code search and analysis across multiple repositories. It provides automated formatting, TypeScript/JavaScript preferences, search optimization, and build automation for developers working with CSV databases and GitHub Actions workflows.
What This Skill Does
Enforces consistent code formatting with Prettier on save and pasteConfigures TypeScript and JavaScript with single quotes and non-relative importsOptimizes search by excluding build artifacts and dependenciesSets up editor preferences with 4-space indentation and 100-character rulersExcludes unnecessary files from file watching to improve performanceAutomates builds on save (excluding ignored directories)Instructions
When using this skill, configure the development environment with the following settings:
1. Code Formatting Configuration
Enable `formatOnSave` and `formatOnPaste` for automatic code formattingSet Prettier as the default formatter across all file typesEnsure consistent formatting without manual intervention2. TypeScript & JavaScript Preferences
Configure both TypeScript and JavaScript to use: - **Import style**: Non-relative module specifiers (e.g., `import { x } from '@/lib/utils'` instead of `../../lib/utils`)
- **Quote style**: Single quotes for all string literals
These settings improve code readability and maintain consistency3. Search Optimization
Exclude the following directories from search results to improve performance:
`**/node_modules/**` - Package dependencies`**/dist/**` - Distribution/compiled output`**/.git/**` - Git version control files`**/build/**` - Build artifacts4. Editor Settings
Configure the editor with:
**Tab size**: 4 spaces**Insert spaces**: Use spaces instead of tabs**Detect indentation**: Auto-detect file indentation**Trim trailing whitespace**: Remove on save**Insert final newline**: Add newline at end of files**Rulers**: Display vertical ruler at 100 characters5. File Exclusions
Exclude these patterns from:
**File explorer**: `.git/`, `node_modules/`, `dist/`, `build/`**File watchers**: Same patterns to reduce system resource usage6. Automated Tasks
Configure save-triggered tasks:
**On save**: Run `npm run build` automatically**Exclude from task**: `node_modules/`, `dist/`, `.git/`, `build/`This ensures the project builds automatically while excluding unnecessary filesUsage Examples
Example 1: Setting Up a New Repository Project
When cloning a repository for code analysis, this skill will:
1. Auto-format all code files when you open and save them
2. Configure imports to use clean, non-relative paths
3. Enable fast search that skips build artifacts
4. Trigger builds automatically when you modify source files
Example 2: Working with CSV Databases
For projects integrating CSV databases:
1. Search functionality will efficiently locate CSV processing code
2. Consistent formatting ensures CSV parsing logic is readable
3. Auto-build on save validates changes immediately
4. File watchers ignore large CSV files in build directories
Example 3: GitHub Actions Integration
When working with GitHub Actions workflows:
1. TypeScript workflow files use consistent single-quote syntax
2. Search quickly locates workflow definitions without noise
3. Auto-formatting keeps YAML and TS files clean
4. Build automation catches errors before committing
Important Notes
The `npm run build` task runs on every save - ensure your `package.json` includes a build scriptNon-relative imports require proper path mapping in `tsconfig.json` or `jsconfig.json`Excluded directories are hidden but still exist - use terminal for direct access if neededThe 100-character ruler is a guide, not a hard limitFile watcher exclusions significantly improve performance on large projectsConstraints
Requires Prettier to be installed as a project dependency or globallyBuild automation assumes `npm` as the package managerNon-relative imports require proper module resolution configurationAuto-build on save may slow down the editor on very large projects