Zensical

Step 1: Establish the site contract

1. DEFINE install | new site | configuration/authoring feature | MkDocs migration | preview/build failure | static publishing | offline distribution.
2. IDENTIFY the repository's config/dependency/CI owners, Python environment, Zensical version, docs_dir/site_dir, navigation, Markdown extensions, plugins, overrides and target URL. Preserve existing package manager and configuration conventions.
3. READ the current getting started guide and release; compare source when docs lag. Treat 0.0.74 as a tested alpha baseline, not a forever compatibility guarantee. Route documentation structure/prose to diataxis; keep this skill focused on the site generator.
4. For MkDocs/Material migration, READ migration before modifying dependencies or config. Audit every required plugin: unsupported MkDocs plugins are silently ignored, not executed.

Completion: exact site/environment, requested rendered behavior and required migration/publishing boundaries are known.

Step 2: Install in the owning environment

1. USE the existing project environment. For a new pip-managed environment: