## HARD MANDATE: PLAN BEFORE ACTION
- **No Unapproved State Changes:** You MUST NOT execute any tool that modifies the filesystem, runs shell commands (excluding read-only discovery like `ls` or `grep`), or changes system state without first presenting a detailed plan and receiving an explicit "Directive" (e.g., "proceed") from the user. This rule is absolute. REQUIRED!

## Added Memories
- When working on the Hugo wiki, docs, or Caddy routing, immediately run the docs_architecture skill to understand the decoupled architecture, deployment logic, and known Docker/Caddy networking quirks.
- When writing Hugo/Blowfish Markdown front matter, always include 'author', 'date' (ISO-8601), 'lastmod' (YYYY-MM-DD), and 'tags' (list) at the bottom of the metadata block.
- Never perform manual builds or deployments of the Hugo sites to bypass the CI/CD pipeline. Always rely on the Gitea Actions workflows for deployment.
- Avoid making direct edits to Nginx Proxy Manager .conf files because it causes a desync with the Web UI database. Always prefer asking the user to make changes via the NPM Web UI instead. If a direct edit is absolutely necessary, always remind the user that the UI will be out of sync.
- When generating dates for Hugo/Blowfish front matter (or any timestamps), never use UTC (Z). Always use EST (America/New_York) timezone offsets (e.g., -05:00 for EST or -04:00 for EDT).
- For all Markdown files, always ensure there is exactly one empty newline immediately following any heading (e.g., # Heading, ## Subheading).
- Always present a detailed summary of planned changes (identifying specific files and the nature of the edits) before executing any modifications. You MUST explicitly ask the user for permission to proceed and wait for a "Directive" before acting.
- When creating callouts or admonitions in Hugo Markdown files, always use the `> [!TYPE]` blockquote syntax (supported by the `hugo-admonitions` render hook) instead of theme-specific shortcodes.

## REQUIRED! Workflow
- **Evaluate Prompt:** For every user request, first decide if specific skills/agents (e.g., codebase_investigator) are required. REQUIRED!
- **Present Plan:** Always create a clear plan and present it to the user. Do not act until a "Directive" (e.g., "proceed") is given. REQUIRED!
- **Logging:** For every resolved prompt, append a log entry to the project directory. REQUIRED!
    - Format: Use a Markdown table.
    - Columns: `| Date (EST) | Prompt | Resolution Steps (Detailed Files/Paths/Tools) |`.
    - Rule: Never remove or overwrite entries; only append.
    - Timezone: Always use EST/EDT offsets.
    - Confirm the project directory by asking the user.
