Update README Installation Instructions

Update the README installation instructions:
- Tell users the values they should set the Theme Colour options to (it should be the default background colours from the theme). [Image #1]
- Step 2 can be a direct link to the Custom CSS settings page: https://kagi.com/settings/custom_css
Base directory for this skill: /Users/rod/.claude/skills/markdown
GitHub Flavored Markdown Generation
Version: 1.2.1
Generate GFM that passes markdownlint validation with zero violations.
Core Principles
1. Blank Lines Are Mandatory
- Before/after ALL lists (MD032)
- Before/after ALL headings except document start (MD022)
- Before/after ALL code blocks (MD031)
- Between ALL block-level elements
2. Consistency Required
- Use
-for lists - Use
#for headings (ATX) - Regular spaces only—never tabs/nbsp
3. Structure Matters
- Heading hierarchy: 1→2→3 (not 1→3)
- ONE H1 per document
- Files end with one newline
- Lines under 80 chars
4. Invisible Characters Matter
- Use ONLY regular spaces (U+0020)
- Never non-breaking spaces (U+00A0, )
- Never tabs
- UTF-8 encoding
Pre-Generation Checklist
- Where will lists/headings/code appear?
- Heading levels verified (1→2→3)?
- Using
-for all lists? - Code languages specified?
- Lines under 80 chars?
- Line breaks needed? (two trailing spaces)
- Using regular spaces only?
- URLs wrapped in
<>or[]? - Document starts with H1?
- Ordered lists use
1.for all items? - File ends with single newline?
- Tables use consistent spacing?
Essential Rules
Lists (MD032, MD004)
Headings (MD001, MD022)
Code Blocks (MD031, MD040)
Nested Fences: When showing markdown examples that contain code blocks, use one more backtick than the deepest level:
- Three backticks (
```): Regular code - Four backticks (
````): Markdown examples with code - Five backticks (
`````): Nested markdown examples
Line Length (MD013)
Break long lines at natural points. Use reference-style links for long URLs.
URLs and Email (MD034)
Wrap bare URLs and emails:
Document Structure (MD041)
Start with H1 (or front matter then H1):
Ordered Lists (MD029)
Use 1. for all items:
File Endings (MD047)
End with single newline:
Table Column Style (MD060)
Use consistent spacing in tables. Three styles:
Compact (recommended): | cell | - single space around content
Aligned: Pipes vertically aligned with padding
Tight: |cell| - no spaces
Pick ONE style per document. Compact is preferred.
Character Encoding
Detection: View → Render Whitespace in VS Code
Fix: Find \u00A0 → Replace with space
Critical for AI: Two trailing spaces = intentional line breaks. Do NOT remove them.
Critical Error Patterns
1. List Without Blank Lines
<!-- markdownlint-disable MD032 -->Wrong:
Right:
2. Heading Without Blank Lines
<!-- markdownlint-disable MD022 -->Wrong:
Right:
3. Code Without Blanks/Language
<!-- markdownlint-disable MD031 MD040 -->Wrong:
Right:
4. Inconsistent Markers
<!-- markdownlint-disable MD004 -->Wrong:
Right:
5. Skipping Levels
<!-- markdownlint-disable MD001 -->Wrong:
Right:
Post-Generation Validation
- Lists have blank lines before/after
- Headings have blank lines before/after
- Code has blank lines before/after
- Heading progression: 1→2→3→4
- All lists use
- - All code has language
- Lines under 80 chars
- Document starts with H1
- URLs wrapped properly
- Ordered lists use
1. - File ends with one newline
- Two trailing spaces used intentionally
- Only regular spaces (no nbsp/tabs)
- Tables use consistent column spacing
Mental Model
Markdown is blocks with mandatory spacing:
Every block transition = blank line required.
Quick Patterns
List:
Heading:
Code:
Nested:
Ordered:
Table:
Common Languages
Programming: python javascript java c cpp go rust ruby
php swift kotlin typescript
Shell: bash sh powershell cmd zsh
Markup: html css xml json yaml toml markdown
Database: sql postgresql mysql
Other: text diff log
Validation
Goal: Zero errors/warnings.
Additional Resources
See bundled references:
references/complete-rules.md- Full rule catalogreferences/edge-cases.md- Platform quirksreferences/examples.md- Detailed examples
Remember
Most common: Missing blank lines around lists/headings/code.
Two trailing spaces: Intentional line breaks. Do NOT remove.
When in doubt:
- Add blank lines before/after blocks
- Use
-for lists - Use
#for headings - Specify code language
- Increment headings by one
- Use regular spaces only
- Two trailing spaces = line break
I've updated the Install section of README.md. I haven't committed it, and I didn't run markdownlint.
- Step 2: it now links straight to the Custom CSS settings page. That replaces the old route through Settings, Appearance, Custom CSS and Change.
- Theme Colour: a new step gives the two values in a small table:
#fbf3dbfor the light theme and#103c48for the dark theme. These match--bg-0inkagi-selenized.css(lines 23 and 259). - Enable Custom CSS: the toggle is on the same settings page, as your screenshot shows, so I dropped the Control Centre directions. The step now says to switch it on and save.
I made some edits you didn't ask for. I removed the "choose Change" and "Save Changes" wording because I couldn't see those buttons in your screenshot. If they still exist on the page, say so and I'll put them back. I also merged the old steps 3 and 4 into one final step, so there are five steps in total.
Final step now says "choose Save Changes", so the button is named again. The page also shows a Cancel button, and the README doesn't mention it. I didn't restore Change, since the page shows the CSS box directly. Nothing is committed yet.
The commit is done locally, but the push failed. GitHub rejected it twice with an Internal Server Error, so nothing is on the remote.
- Branch: I committed on a new branch,
chore/readme-install-instructions, because the repo was onmain. - Commit message: "Link to Custom CSS settings and document Theme Colour values in README install steps".
- Push: the error comes from the GitHub server, not from anything in the commit. The request IDs were
CBC5:318FC1:12017E6:173CC66:6ADF63A2andCCE7:2A6EEF:12056D8:173FF55:6ADF63A8.
I haven't tried a third time. Rod, would you like me to retry in a minute or two, once GitHub has had time to recover? You can check githubstatus.com in the meantime.