Gemini CLI Information
Tells the Gemini CLI how to find blog posts and their images on a Jekyll site.
What this file does
Tells the Gemini CLI how to find blog posts and their images on a Jekyll site.
When to use it
- You want the Gemini CLI to generate or update blog posts for your Jekyll site
- You need to explain your Jekyll blog structure to an AI assistant
- You are onboarding a new contributor who uses Gemini CLI to manage content
Assumes this stack
Gemini CLI Information
This document provides helpful information for the Gemini CLI about the structure of this website.
Blog Posts
Blog posts for this website are located in the _posts folder. Each blog post is a separate file in Markdown format.
The name of each blog post file must start with the date, followed by a dash, then the title of the post, and finally the .md extension. For example: YYYY-MM-DD-your-post-title.md.
Each blog post file also needs a section at the very top, enclosed by --- lines, where you can define details like the title, author, and date for the website to use. This is called "Front Matter".
Blog Post Images
Images for blog posts should be placed in the img/posts/ directory.
To keep things organized, create a new subfolder inside img/posts/ for each blog post. The name of this subfolder should match the date and title part of your blog post file.
For example, if your blog post file is 2025-12-18-my-new-blog-post.md, you would create a folder named 2025-12-18-my-new-blog-post inside img/posts/. All images for that specific blog post would then go into this new folder.
When you use an image in your blog post, you would link to it like this: /img/posts/2025-12-18-my-new-blog-post/your-image-name.jpg.
What's inside
2 sections: blog post file naming and location, image folder structure and linking.
Change this for your project
- Replace
_postswith your own posts directory if different - Replace
img/posts/with your own image directory path - Replace
2025-12-18-my-new-blog-postwith your actual post filename pattern
Where it goes
Keep it in your repository where the agent or team that needs it will read it.
Related Documents
Totem — Development Rules
Defines team-wide conventions for a pnpm monorepo: branch strategy, commit rules, tooling, and a mandatory knowledge-search workflow before coding.
MechCAD-MLLM
Proposes a MLLM + dual-decoder architecture for mechanical CAD generation, combining Drawing2CAD and CAD-GPT ideas.
Prompt Generator
Generates Stable Diffusion and Flux prompts via Qwen3-8B on Ollama, with a Gradio UI and CLI.
Agent Instructions
Defines a three-layer architecture (directive, orchestration, execution) for AI agents that self-anneal errors and update living SOPs.