chromium-docs

This tool provides a specialized search interface for the extensive Chromium documentation ecosystem, covering approximately 2000+ markdown files across the source tree. It is designed for developers, contributors, and researchers who need to navigate complex subsystem documentation, architectural design documents, Mojo IPC interfaces, and platform-specific guides (Android, iOS, ChromeOS). By indexing the repository locally, the skill enables fast retrieval of technical information without requiring manual file-system traversal.

• Full-text search across documentation rooted in docs/, README.md files, and component-specific documentation directories.

• Categorized results mapping findings to specific domains including GPU, networking, security, performance, accessibility, and build systems.

• Contextual indexing that captures design patterns, best practices, and integration guides for major Chromium subsystems.

• Direct mapping of search queries to file paths, facilitating quick navigation to the relevant source markdown files for deep reading.

• Support for maintenance workflows like index building and refreshing to ensure that documentation references remain current after git rebasing or syncing.

• Inputs consist of natural language queries regarding architectural concepts, component APIs, or documentation discovery (e.g., 'where are the site isolation design docs').

• Outputs provide a ranked list of relevant documents with titles, linked file paths, category tags, and content excerpts.

• The index must be initialized with the --build-index command before the first search; re-build the index following significant syncs or updates to ensure accuracy.

• This skill should be used when documentation is required for learning or navigation; it should not be activated for direct code debugging, implementation tasks, or build execution unless documentation lookup is explicitly requested.

• Typical usage scenarios include identifying API boundaries, understanding multi-process architectural models, researching GPU rendering paths, or finding testing frameworks for unit and browser tests.