llm-context

Manage LLM context in the .llm/ directory and enforce Git exclusion.

14|4|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/motlin/claude-code-plugins --skill llm-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-context
Source: https://github.com/motlin/claude-code-plugins/tree/main/plugins/orchestration/skills/llm-context
Command: npx skills add https://github.com/motlin/claude-code-plugins --skill llm-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent management of LLM-specific context files can lead to confusion, accidental version control tracking of sensitive data, and a cluttered repository. This Skill provides clear guidelines for organizing and securing your AI's context.

Core Features & Use Cases

  • Standardized Structure: Defines the .llm/ directory at the repository root for all LLM-related context.
  • Git Exclusion Enforcement: Ensures the .llm/ directory is properly untracked by Git, preventing sensitive or temporary files from being committed.
  • Context Categorization: Differentiates between editable context (e.g., todo.md for tasks) and read-only context (e.g., git clones, saved documentation).
  • Use Case: Automatically verify that your .llm/ directory is correctly configured and git-ignored, providing a clean, organized, and secure space for AI-specific context without cluttering your version control.

Quick Start

Verify that the .llm/ directory in this repository is properly git-ignored and structured.

Frequently Asked Questions about llm-context

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

FAQPage Schema
How do I organize LLM context files in my Git repository?

Create a `.llm/` directory at your repository root to centralize LLM context. This standardized structure separates editable files like task lists from read-only reference content, keeping AI-specific guidance organized and distinct from version-controlled code.

Why should I exclude the .llm/ directory from Git tracking?

Excluding `.llm/` from version control prevents accidental commits of sensitive data, temporary files, and AI-specific context that shouldn't persist across commits. Git exclusion via `.git/info/exclude` ensures the directory remains private and untracked.

Can I use editable task lists alongside read-only context in .llm/?

Yes. Store editable content like `todo.md` for planning alongside read-only reference files such as cloned documentation. This separation lets you manage dynamic tasks independently from static contextual guidance without version control interference.

How do I verify that .llm/ is properly configured and git-ignored?

Check that `.llm/` exists at your repository root and is listed in `.git/info/exclude` to confirm Git ignores it. Verification ensures your LLM context directory is correctly structured, secure, and won't clutter your version control history.

What's the best way to structure AI context in a development workflow?

Use `.llm/` as a dedicated space for AI guidance, separating it from your codebase. Combine editable planning files with read-only contextual references, then exclude the entire directory from Git to maintain a clean repository and prevent sensitive context leaks.