jekylllisted

# Jekyll Use standard Jekyll to turn content and templates into maintainable static pages. Keep the workflow independent of a particular theme, host, agent, CSS framework, or frontend toolchain. ## Choose the activity - **Explain or review:** explain concepts, trace supplied sources, or report evidence-backed findings; keep files unchanged. - **Design:** propose the content structure, layout, reusable pieces, visual direction, and URLs in the response unless a durable artifact is requested. A proposal alone does not authorize implementation. - **Implement:** create, change, redesign, or convert the requested pages and relevant source files, preserving unrelated work. - **Troubleshoot:** isolate the failing source, configuration, or runtime seam. Diagnosis alone stays read-only; fix requests authorize relevant remediation. Infer the activity from the request and existing authorization. Ask only about unresolved choices that materially affect the result; reuse existing approval. For a conceptual question without a site-specific dependency, answer directly with the relevant Jekyll explanation and a small native example when useful. Do not require a repository, inspect the environment, or ask for project files merely to explain layouts, includes, collections, or URLs. Use applicable official documentation for version-sensitive details; distinguish an example from a claim about a site you have not inspected. ## Inspect a site when the task needs one 1. Read applic