context-bootstrap

Collect repository structure, runnable commands, and architecture anchors at startup.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/paradox123/shared-ai-docs --skill context-bootstrap-paradox123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-bootstrap
Source: https://github.com/paradox123/shared-ai-docs/tree/main/skills-repo/skills/context-bootstrap
Command: npx skills add https://github.com/paradox123/shared-ai-docs --skill context-bootstrap-paradox123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstraps the NCG agent session with a deterministic baseline by collecting repository structure, runnable commands, and architecture anchors from source and documentation at startup. This ensures implementation sessions begin with known context even when READMEs/AGENT files are sparse.

Core Features & Use Cases

  • Bootstraps repository structure, commands, and architecture anchors to establish a repeatable starting state.
  • Supports environments where documentation is sparse by inferring context from manifests, config, and targeted anchors.
  • Use case: starting a new NCG project or resuming a session in a partially documented repository, ensuring consistent baseline knowledge.

Quick Start

Initialize the NCG session context for the current repository.

Frequently Asked Questions about context-bootstrap

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

FAQPage Schema
How do I bootstrap an agent session with deterministic repository context?

Bootstrap an agent session by collecting repository structure, runnable commands, and architecture anchors from manifests and config files to establish a repeatable baseline context at startup.

What is the best way to establish baseline knowledge in a partially documented repository?

Establish baseline knowledge by inferring context from manifests, config files, and targeted architecture anchors when documentation is sparse, ensuring implementation sessions begin with known architecture.

How do I collect runnable commands and architecture anchors for a new project session?

Collect runnable commands and architecture anchors by sourcing context from the local project directory and targeted anchors, parsing documented sources from manifests and config files.

Can I use context bootstrap in repositories with sparse README or AGENT files?

Yes, the context bootstrap mechanism supports environments with sparse documentation by inferring startup context from manifests, config files, and referenced architecture anchors.

Do I need documented manifests and config files to build a repeatable startup context?

Yes, building a repeatable startup context requires documented sources from manifests, config files, and referenced docs to ensure deterministic baseline knowledge at session initialization.

Why does my agent session lack consistent architecture context on startup?

Agent sessions lack consistent context when baseline knowledge is not collected from repository structure and architecture anchors, leading to non-deterministic startup states in sparse documentation.