Foundation
Architecture
Separate the iron from the jazz: Rust extraction up front, Python rule execution behind a stable contract.
A Compiler
for Prose
Industrial parsing meets jazz-age rulecraft.
Explore the tool
Contract
IR Contract
A deterministic schema between parsing and analysis so rules operate on regions, spans, and capability-planned detail.
Rules
Rule Engine
Typed Python rules with direct navigability, explicit capabilities, and diagnostics rendered without guesswork.
Grammar
Grammar Layer
From tokens to clauses only when capability planning requires it. Syntax stays subordinate to fidelity.
CLI
CLI & UX
Ruff-inspired commands, legible configuration, and safe fixes that never lose track of the underlying source.
Testing
Testing Sandbox
Hermetic fixtures, isolated runs, and typed outputs so rule development behaves like software engineering, not divination.
Diagnostics
Diagnostic Matrix
Readable verdicts with span truth, provenance, and byte-level evidence instead of flattened guesswork.
Plan
Roadmap
Vertical slices from Markdown core to rule packs, richer editors, and sharper contracts at each phase boundary.
Why Stilyagi
Absolute Source Fidelity
Findings map to exact byte spans. No lossy transforms, no invented context, no flattened approximation.
Policy
Programmable Policy
Typed Python rules over a rich IR let teams encode house style, compliance, and taste without falling back to regex folklore.
Planning
Capability-Planned Analysis
Run only the analysis you need. Fast by default, deeper when requested, always explicit about the cost.
The pipeline, as printed
Figure 01 · Presentation board from the Stilyagi deck, reused here as the canonical overview
of the processing chain.
Start in three commands
Read the source on GitHub
$ stilyagi check
Run analysis and print diagnostics with source-backed spans and stable ordering.
$ stilyagi dump-ir
Inspect the intermediate representation so rules can reason about the same contract the extractor emitted.
$ stilyagi clean
Remove caches and temporary artefacts when you want a fresh run or a tidier working tree.
Choose your briefing room
Manifesto
Why
The case against the weak camps and the argument for source-faithful documentation analysis.
Read the manifesto →Mechanics
How
Architecture, CLI shape, capability planning, and the line between extraction and rule execution.
Inspect the mechanics →Reference
Docs
Rules catalogue, configuration shape, suppressions, and the growing manual for the tool itself.
Open the docs →Planning
Roadmap
The phase plan from markdown core through plugins, diagnostics, and richer editor integrations.
See the roadmap →