User.project_index

Maintain a persistent project index cache in Neovim using .nvim markers.

1|Updated Oct 26, 2025
One-click install
npx skills add https://github.com/NeKon69/nvim-dot --skill user-project-index
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: User.project_index
Source: https://github.com/NeKon69/nvim-dot/tree/main/.agents/skills/user.project_index
Command: npx skills add https://github.com/NeKon69/nvim-dot --skill user-project-index

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines project management by automatically indexing and maintaining a list of your projects, making it easier to navigate and switch between them.

Core Features & Use Cases

  • Automatic Project Detection: Identifies projects based on .nvim directories and markers.
  • Cache Management: Maintains a persistent cache of project information for quick access.
  • Real-time Updates: Keeps the project index fresh on startup, directory changes, and marker file modifications.
  • Use Case: As you move between different codebases in your editor, this Skill ensures your project list is always up-to-date without manual intervention.

Quick Start

Ensure your project index is up-to-date by running the setup command.

Frequently Asked Questions about User.project_index

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically manage project indexing in Neovim?

Automatic project indexing in Neovim is managed by detecting directories containing `.nvim` and maintaining `.nvim/project_marker` files. This creates a persistent cache of project information, keeping your project list updated on startup and directory changes.

What is the best way to keep a persistent cache of Neovim projects?

A persistent cache of Neovim projects is maintained by tracking `.nvim/project_marker` files. The cache updates automatically during editor startup, directory changes, and marker file modifications, ensuring quick access to your codebases.

Does this project discovery tool require specific marker files to function?

Project discovery requires directories to contain a `.nvim` folder with a `.nvim/project_marker` file. This marker-based detection allows the system to register projects and retrieve extra top-level directories for the cache.

Can I register extra top-level directories for code navigation in Neovim?

Extra top-level directories can be registered for code navigation alongside detected projects. The system supports project registration and retrieval of these directories, keeping the workspace index current without manual intervention.

When do I need a project marker file for Neovim workspace management?

A project marker file is needed when you want a directory recognized by Neovim workspace management. Placing a `.nvim/project_marker` file ensures the directory is indexed and added to the persistent cache for quick switching.