Vc Generate Context logo

Vc Generate Context

CommunityPopular
withkynam
vc-generate-context

Generate or update the project's authoritative repository context at process/context/all-context.md. Use when repo context is missing, stale, or contradicted by code.

Overview

Publisherwithkynam
Repositoryvibecode-pro-max-kit
Skill namevc-generate-context
Stars
1.1K
Forks
234
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by withkynam on GitHub. Read the source before you install it.

Installation

Install the Vc Generate Context AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-context
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git /tmp/vibecode-pro-max-kit
mkdir -p .claude/skills
cp -r /tmp/vibecode-pro-max-kit/.claude/skills/vc-generate-context .claude/skills/vc-generate-context
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Vc Generate Context in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Vc Generate Context on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Vc Generate Context is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Generate Context

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

Use this skill to maintain process/context/all-context.md, the broad portable project knowledge layer shared by Codex and Claude. Use process/context/all-context.md as the context router before reading grouped docs.

Optional input: a package, app, feature, context group, or architectural area to refresh first.

Workflow

  1. Read references/generate-context.md for the full context contract.
  2. Determine mode:
    • Full scan when process/context/all-context.md is missing.
    • Delta update when it exists.
  3. Read process/context/all-context.md when present to identify relevant grouped context files.
  4. Inspect current repo state, active plans, feature folders, package scripts, tooling, important architecture files, and relevant process/context/**/*.md docs.
  5. Produce process/context/all-context.md PLUS process/context/{group}/all-{group}.md for each detected or approved group (see Invocation Modes below).
  6. Include scan timestamp, repo HEAD if available, changes since last update, open questions, and source references.
  7. Validate the generated context:
    bash
    node .claude/skills/vc-generate-context/scripts/validate-all-context.mjs
  8. If routing or grouped context changed, also run:
    bash
    node .claude/skills/vc-audit-context/scripts/validate-context-discovery.mjs

Rules

  • Treat process/context/ as durable cross-agent knowledge.
  • Treat process/context/all-context.md as the durable routing protocol; do not replace it with generated prose.
  • Do not store agent-specific mechanics here unless they affect project workflow.
  • Do not rewrite grouped context docs; if they are stale or mis-grouped, flag audit-context.
  • Prefer concise, factual, path-specific documentation.
  • Use pnpm terminology for package management.
  • Treat validation failures as blockers before presenting context as refreshed.

Invocation Modes

ModeTriggerGroup-detectionOutput
setup-delegationCalled by vc-setup passing an approved-groups listSkip re-detection; use the list providedall-context.md + all-{group}.md for each approved group
standalone-fullDirect invocation with no groups listSelf-detect groups via the detection table in references/generate-context.mdall-context.md + all-{group}.md for all detected groups
deltaInvoked when context already exists; update contextSelf-detect; create MISSING groups only; warn on unrecognized; never deleteall-context.md updated + any new all-{group}.md files created

See references/generate-context.md for per-mode instructions, the Context Group Detection Table, and delta-mode group-creation rules.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Vc Generate Context AI skill do?

Generate or update the project's authoritative repository context at process/context/all-context.md. Use when repo context is missing, stale, or contradicted by code.

Why use Vc Generate Context on TypingMind?

Because you install it once and use it with any model. Vc Generate Context is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Vc Generate Context in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-context. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Vc Generate Context?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Vc Generate Context?

As many as you like. As long as a model supports skills, you can use Vc Generate Context with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Vc Generate Context AI skill free?

Yes. It is published on GitHub by withkynam under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇