init-context

Generates a project-specific CLAUDE.md by scanning fragment metadata and matching conditions to codebase signals.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hve4638/hve-cc-marketplace --skill init-context-hve4638
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-context
Source: https://github.com/hve4638/hve-cc-marketplace/tree/main/common/skills/init-context
Command: npx skills add https://github.com/hve4638/hve-cc-marketplace --skill init-context-hve4638

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates a project-specific CLAUDE.md by scanning fragment files, reading their frontmatter (name, description, condition), and matching conditions against the repository's signals to produce candidate content for final assembly.

Core Features & Use Cases

  • Scans the fragment pool under the skill's designated fragments directory and reads each fragment's metadata to shortlist viable CLAUDE.md components.
  • Applies a structured six-stage workflow (scan, match, confirm, synthesize, conflict check, finalize) to ensure reproducibility, safety, and traceability.
  • Enables multi-language distribution and backup/versioning to guard against data loss and enable re-synthesis.

Quick Start

Invoke '/init-context' to generate and finalize CLAUDE.md for your current project.

Frequently Asked Questions about init-context

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

FAQPage Schema
How do I generate a CLAUDE.md file for a multi-language project?

To generate a CLAUDE.md for a multi-language project, the init-context skill scans fragment frontmatter and matches conditions against codebase signals, organizing fragments into root and subdirectory CLAUDE.md outputs after user confirmation.

What is the best way to assemble project context files from fragments?

Assembling project context files from fragments is done by scanning a fragment pool, reading frontmatter metadata, and matching conditions against repository signals to produce candidate content for final CLAUDE.md assembly.

How does the six-stage workflow for generating CLAUDE.md ensure reproducibility?

The six-stage workflow ensures reproducibility by scanning, matching, confirming, synthesizing, conflict checking, and finalizing CLAUDE.md outputs with idempotent re-synthesis, backups, and whitespace normalization.

Can I automate CLAUDE.md creation for subdirectories in a complex codebase?

Yes, you can automate CLAUDE.md creation for subdirectories by matching fragment conditions against codebase signals, then organizing the matched fragments into root and subdirectory CLAUDE.md outputs.

Does generating CLAUDE.md with fragments require any external dependencies?

Generating CLAUDE.md with fragments requires no external dependencies, relying solely on the skill's internal six-stage workflow to scan, match, synthesize, and finalize context files from the designated fragments directory.