meaning-init

Create and configure the .meaning/ directory with schemas and index.yaml.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/bozaah/meaning-fs --skill meaning-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meaning-init
Source: https://github.com/bozaah/meaning-fs/tree/main/.claude/skills/meaning-init
Command: npx skills add https://github.com/bozaah/meaning-fs --skill meaning-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap meaning indexing by creating and configuring the .meaning/ directory for your project. This enables persistent semantic context for files and faster AI-assisted navigation.

Core Features & Use Cases

  • Automatic bootstrap of .meaning/ with language-appropriate schemas and templates
  • Language-agnostic project type detection and schema installation
  • Scans repository files and generates an initial index.yaml with high-confidence suggestions
  • Review workflow to refine metadata and lock in concepts

Quick Start

Run meaning init in your project root to bootstrap the .meaning/ directory. Optionally specify the project type with --type (python|node|rust|docs) and set a file limit with --limit. After indexing, review suggestions with meaning-review and run meaning-update to index additional files.

Frequently Asked Questions about meaning-init

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

FAQPage Schema
How do I bootstrap semantic indexing for my codebase?

Run `meaning init` in your project root to automatically create the `.meaning/` directory, detect your project type, install language-specific schemas, and generate an `index.yaml` file with high-confidence semantic suggestions for your review.

What is semantic indexing and why do I need a .meaning directory?

Semantic indexing via the `.meaning/` directory provides persistent semantic context for your repository files, enabling faster AI-assisted navigation and better codebase inference during development.

Can I use meaning-init with Python, Node, Rust, or documentation projects?

Yes, meaning-init supports Python, Node, Rust, and docs project types. It performs language-agnostic project type detection and installs language-appropriate schemas automatically, or you can specify the type manually using the `--type` flag.

How do I review and refine the initial index.yaml suggestions?

After bootstrapping, use `meaning-review` to refine metadata suggestions and lock in concepts, then run `meaning-update` to index additional files. Low-confidence items are automatically flagged in the generated index for your review.

Do I need Python to run meaning-init for project bootstrapping?

Yes, meaning-init requires a Python environment to execute. It reads your repository files, runs inference, and writes the `.meaning/` templates and `index.yaml` configuration to bootstrap semantic indexing.

How can I limit the number of files scanned during semantic indexing?

Use the `--limit` flag with `meaning init` to set a file limit for the repository scan. This controls how many files are processed during inference and included in the generated `index.yaml`.