CLAUDE.md

Before every task

Always read .claude/FINDINGS.md first. It contains known issues, fixes applied, and cleanup patterns. Check it before touching any post content or layout to avoid repeating solved problems.

What is this repo?

The RK Solutions blog — a Jekyll site on GitHub Pages with a terminal-aesthetic design. Posts live as Markdown in _posts/, the homepage uses Liquid templates, and individual post pages are generated by Jekyll.

Skills

Check .claude/skills/ for detailed guidance:

• rksolutions-frontend — design system, color tokens, components, responsive rules
• rksolutions-blog — publishing workflow, Jekyll config, frontmatter schema, widgets
• rksolutions-migration — WordPress to Jekyll conversion, cleanup rules, checklist

Commands

# Serve locally (requires Ruby 3.2+ via Homebrew)
export PATH="/opt/homebrew/opt/ruby/bin:$PATH"
export GEM_HOME="$HOME/.gem/ruby/4.0.0"
export PATH="$GEM_HOME/bin:$PATH"
bundle exec jekyll serve --livereload

# Build without serving
bundle exec jekyll build

# Verify no WordPress remnants
grep -r 'stk-\|style="color\|wp-block-heading' _posts/

Key rules

• Posts go in _posts/YYYY-MM-DD-slug.md — Jekyll picks them up automatically
• Code blocks default to PowerShell highlighting — only use ``` fences with explicit language when it’s NOT PowerShell
• Code blocks always stay dark (#141512) regardless of theme
• TOC items must be on separate lines and indented by heading level
• Never commit WordPress CSS remnants (.stk-*, inline style=, has-text-color)
• Run the migration checklist in .claude/skills/rksolutions-migration/SKILL.md for any imported content