context-engineering

Load project context from index files before starting work.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load project context from index files before working. You MUST actually read the files -- not skim, not summarize, not say I'll read this and then skip it.

Core Features & Use Cases

  • Read and load context from core files and all domain indexes to enable informed work.
  • Build a complete domain map from indexes, triage relevance, and present a prioritized reading plan.
  • Read files until a minimum count is reached, with optional deep scan for all relevant domains.

Quick Start

State your task and invoke context-engineering with a numeric minimum (e.g., 10) or 'deep' to read all relevant files.

Frequently Asked Questions about context-engineering

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

FAQPage Schema
How do I load project context from index files before starting work?

Loading project context requires the Skill to read root configs and domain indexes, triage file relevance, and read documents until reaching a user-defined minimum file count.

What is the best way to build a domain map from codebase indexes?

The best way is to read all domain indexes, perform domain triage to rank files by relevance, and present a prioritized reading plan before you begin implementation.

Can I load context for all relevant domains instead of a specific file count?

Yes, you can load all relevant domains by invoking the Skill with 'deep' instead of a numeric minimum, which triggers a deep scan to read all relevant files.

When do I need to load codebase context using a context engineering approach?

You need to load codebase context when starting a new session, switching tasks, or needing project context to answer questions or begin implementation work.

Does loading project context just skim and summarize index files?

No, loading project context requires actually reading the files thoroughly rather than skimming, summarizing, or skipping the content before working.