Kreuzberg Core Principles FAQs

Question 1

What is the primary focus of the Kreuzberg Core Principles skill?

Accepted Answer

It enforces strict architectural rules, emphasizing Rust-core logic, production-grade safety, and a minimalist file-editing approach to maintain high-performance document processing standards.

Question 2

How does this skill improve Python code quality?

Accepted Answer

The skill mandates that Python code uses builtin imports at the top, utilizes frozen and hashable dataclasses with slots, and follows a strictly function-based testing pattern.

Question 3

Why is the architecture constrained to a Rust core?

Accepted Answer

This ensures that all heavy-lifting and document extraction logic is centralized for performance and consistency, while other language bindings only provide idiomatic APIs.

Question 4

Does this skill help with project documentation?

Accepted Answer

No, it specifically follows a 'no proactive documentation' policy, instructing Claude to focus strictly on requested code changes rather than creating unnecessary READMEs or docs.

Question 5

What are the Rust safety requirements included in this skill?

Accepted Answer

It forbids the use of .unwrap() in production code, requires explicit SAFETY comments for any unsafe blocks, and ensures that lock poisoning is always handled.

Kreuzberg Core Principles

Key Features

Use Cases

Kreuzberg Core Principles

Key Features

Use Cases