# Vc Context Discovery

Discover and load all relevant context for the current task.

- Repository: https://github.com/withkynam/vibecode-pro-max-kit (1164 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-06-21
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add withkynam/vibecode-pro-max-kit --skill vc-context-discovery -g -a claude-code -y`
Codex: `npx skills add withkynam/vibecode-pro-max-kit --skill vc-context-discovery -g -a codex -y`
Cursor: `npx skills add withkynam/vibecode-pro-max-kit --skill vc-context-discovery -g -a cursor -y`
Gemini CLI: `npx skills add withkynam/vibecode-pro-max-kit --skill vc-context-discovery -g -a gemini-cli -y`

## Description

Discover and load all relevant context for the current task. Lists feature group nested files with full paths, loads process/context/ files by domain routing. Called at the start of every agent session.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# vc-context-discovery

> **Output style:** Follow `process/development-protocols/communication-standards.md`, answer-first, plain language, no unexplained jargon, TL;DR on long responses.

Discover and load all relevant context for the current task. This skill lists feature group nested files with full paths and loads `process/context/` files by domain routing table. It is the canonical context-loading entrypoint for every agent session.

## When To Invoke

At the start of every agent session (research, innovate, plan, validate, execute, update-process, fast-mode). Also at the start of any skill that needs repo context before operating.

## Frontmatter Schemas

Document the canonical schemas for three file types used across the repo. These schemas enable frontmatter-aware routing and filtering.

**Context file frontmatter schema:**
```yaml
name: context:{slug}
description: "one-line scope, used by vc-context-discovery for routing"
keywords: comma, separated, task, vocabulary, terms   # drives grep-first keyword routing
related: [context:{other-slug}, context:{another-slug}]  # sibling/cross-group links (optional)
date: dd-mm-yy
```

- `keywords`, strongly recommended, non-empty. Comma-separated task-vocabulary terms an
  agent would use to describe a task this doc serves (e.g. `session, token, refresh, jwt,
  login`). This is the match surface for `discover-context.mjs --match`; weak/absent
  keywords are why a relevant doc never gets routed to. Lint WARNS when empty (so existing
  projects don't break on sync), backfill at UPDATE-PROCESS.
- `related`, OPTIONAL list of `context:{slug}` values for sibling docs that are usually
  needed together (the markdown-native equivalent of cross-links). Every slug listed MUST
  resolve to a real `context:` doc; dangling links fail lint. Discovery follows these after
  the primary match so a task touching two domains loads both.

The rest: https://github.com/withkynam/vibecode-pro-max-kit/blob/HEAD/.claude/skills/vc-context-discovery/SKILL.md