Blog post writing guidelines for gkoreli.com. Use when writing, editing, or reviewing blog posts. Covers voice, structure, content format, sourcing rules, formatting balance, transparency, and technical writing standards for an engineering audience.
Reverse-engineer honest external doorways from an already-shaped article: publication role, reader and search intent, H1/seoTitle/description/standfirst, headings, keywords, internal cross-references, link-worthy assets, and distribution. Use when titling,…
The full creative-writing canon for gkoreli.com — Goga's voice, the exposed register, the claims that bleed, what makes essays and engineering articles worth reading and sharing, and the collaboration protocol between Goga and the agent. Use when writing,…
Identify and protect an article's living center before drafting, editing, or reviewing it. Use for any gkoreli.com article to choose its governing form, preserve unresolved experience and load-bearing roughness, give humans and AI agents enough context to…
Evidence-based mechanics for engineering articles that get read, shared, cited by AI search, and answered—title mechanics, agentic-search reality, trust, share triggers, and the pre-publish checklist. Run after article-discovery-positioning has fixed the…
Draft and polish concise, direct, natural prose. Use when writing, editing, or reviewing articles, documentation, PR descriptions, release notes, and messages, especially when asked to tighten writing, remove mechanical phrasing, or apply Orwell-style prose…
Research, write, edit, and review OSS Radar issues for gkoreli.com in either single-project deep-dive or cohort-scan mode. Use for code-backed open-source analysis, product-thesis and vision reconstruction, competing-theory tests, market framing, claim…
Use when Claude/Fable should delegate implementation, review, investigation, UI verification, or mechanical coding work to Codex CLI or another Claude Code worker from this project.