Built a set of skill files for Claude and Gemini that make every session start warm instead of cold

Reddit r/artificial / 4/30/2026

💬 OpinionDeveloper Stack & InfrastructureTools & Practical Usage

Key Points

  • The author addresses the “cold start” problem in AI workflows by using skill files so each new session doesn’t require re-explaining business context and preferences.
  • A skill file is described as a Markdown document uploaded to a Claude Project or pasted into a Gemini chat, where the content serves as persistent context.
  • The post highlights three example skill files: brand-voice.md for tone and formatting rules, client-router.md to load a client’s project context automatically, and seo-aeo-audit-checklist.md for a structured website scoring checklist.
  • The author invites others to share whether they use similar systems and what information they keep persistent across sessions.
  • Overall, the approach emphasizes reusable, structured instructions and context to make AI interactions faster and more consistent across sessions.

One thing that frustrates me about most AI workflows is the cold start problem. Every new session you re-explain your business, your voice, your clients.

I started solving this with skill files. A skill file is a markdown document you upload to a Claude Project or paste into a Gemini Gem. It holds your context permanently so you never re-explain anything.

The three I use most:

brand-voice.md: defines tone, writing rules, and platform-specific formatting

client-router.md: when you say a client name, Claude loads their full project context automatically

seo-aeo-audit-checklist.md: structured audit that scores any website out of 100 across 7 sections including AI search visibility

Anyone else using a similar system? Curious what context you keep persistent across sessions.

submitted by /u/Wise-Cardiologist-31
[link] [comments]