path-context

Register external project folders and surface relevant files within a 15-file budget.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/fxckcode/skills-kit --skill path-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: path-context
Source: https://github.com/fxckcode/skills-kit/tree/main/skills/path-context-skill
Command: npx skills add https://github.com/fxckcode/skills-kit --skill path-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

External project folders contain valuable source context but are often too large to read in full. This Skill provides a disciplined protocol to register paths and surface only the most relevant files within a strict budget.

Core Features & Use Cases

  • Register external project folders from config, --add-dir, or in-prompt declarations, and load them into context for a task.
  • Perform a 6-pass discovery to surface entry points, domain keywords, imports, and signals while respecting a hard 15-file budget.
  • Support project-map mode for large repositories, delivering a structural overview instead of per-file reads.

Quick Start

Trigger a context load with @context /projects/design-system and the agent will surface the most relevant files within the 15-file budget.

Frequently Asked Questions about path-context

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

FAQPage Schema
How do I load external project folders as context without exceeding token limits?

You can load external project folders as context by registering paths via config, --add-dir, or in-prompt declarations. The skill uses a six-pass discovery protocol to surface only the most relevant files within a strict 15-file budget.

What is the best way to discover entry points and imports in large repositories?

Discovering entry points and imports in large repositories is handled by a six-pass protocol that identifies naming signals, domain keywords, and recency. It can also provide a structural project-map overview instead of reading individual files.

Can I register multiple external project paths as reference context at the same time?

You can register multiple external project paths as reference context simultaneously, supporting up to three registered paths. It processes them together to surface relevant files while enforcing a hard 15-file total budget across all directories.

Does loading external project folders risk modifying my source code?

Loading external project folders does not risk modifying your source code because the skill enforces a read-only constraint. It strictly forbids writing to the source directories and only reads a small, bounded set of files.

How do I trigger a context load for a specific design system directory?

You trigger a context load for a specific directory by using the @context command followed by your project path. The agent will then execute the discovery protocol and surface the most relevant files within the 15-file budget.

What are the limitations of using automated file discovery for project context?

Limitations of automated file discovery include a hard 15-file total budget and support for a maximum of three registered paths. It reads only a bounded set of files, which may omit deeply nested or less recent context.