md tweak to readme

Author: EdwardAngert

README.md

@@ -7,18 +7,27 @@ To ensure consistent and context-aware assistance from ChatGPT or Claude Code, u
 ```md
 You are assisting with technical documentation for the open source Coder project (https://github.com/coder/coder). You should follow the rules and preferences outlined in these files:
 
-- style-guide.md (formatting and tone rules)
-- architecture-notes.md (high-level architecture of the product)
-- doc-template.md (content structure scaffolds)
-- snippet-library.md (reusable CLI/YAML/config blocks)
-- ai-project-notes.md (recent work log and in-progress ideas)
-- claude-code-config.md (rules for Claude's behavior)
+1. style-guide.md (formatting and tone rules)
+
+1. architecture-notes.md (high-level architecture of the product)
+
+1. doc-template.md (content structure scaffolds)
+
+1. snippet-library.md (reusable CLI/YAML/config blocks)
+
+1. ai-project-notes.md (recent work log and in-progress ideas)
+
+1. claude-code-config.md (rules for Claude's behavior)
 
 You are not responsible for copyediting or tone unless asked; focus on:
-- technical accuracy (based on the codebase and documented architecture)
-- adherence to file placement and structure
-- verifying commands, parameters, and file references
-- following our markdown and terminology conventions
+
+1. technical accuracy (based on the codebase and documented architecture)
+
+1. adherence to file placement and structure
+
+1. verifying commands, parameters, and file references
+
+1. following our markdown and terminology conventions
 
 Do not use emojis in headings or list items. Use relative paths in links. If you're unsure, ask before making assumptions.
 ```
@@ -34,19 +43,22 @@ This directory — `coder-docs-writing/` — is meant to live alongside the `cod
 ---
 
 ## Purpose
+
 This repo acts as a **persistent memory store** for markdown/style preferences, architectural understanding, and AI-generated notes. It is designed to:
 
-- Serve as a **sidecar knowledgebase** for the primary maintainer (Edward Angert)
-- Act as an **AI Subject Matter Expert (AI-SME)** for use in LLM workflows
-- Be a **shared workspace** for coworkers to contribute insights, style clarifications, architecture notes, and documentation patterns
+1. Serve as a **sidecar knowledgebase** for the primary maintainer (Edward Angert)
+
+1. Act as an **AI Subject Matter Expert (AI-SME)** for use in LLM workflows
+
+1. Be a **shared workspace** for coworkers to contribute insights, style clarifications, architecture notes, and documentation patterns
 
 The goal is to reduce context-switching, enforce style and consistency, and enable teammates or AI to step in seamlessly.
 
 ---
 
 ## Structure
 
-```
+```text
 coder-docs-writing/
 ├── README.md                      # This file
 ├── style-guide.md                # Markdown and tone/style preferences
@@ -66,28 +78,23 @@ Documentation paths should refer to content under `../coder/docs/`. Image assets
 
 ## Getting Started
 
-1. **Clone the repo locally** (or fork it for sandboxed edits):
-   ```bash
-   git clone git@github.com:yourusername/coder-docs-writing.git ~/.coder-docs-writing
-   ```
+1. Clone the repo locally (or fork it for sandboxed edits):
+
+    ```bash
+    git clone git@github.com:yourusername/coder-docs-writing.git ~/.coder-docs-writing
+    ```
 
-2. **(Optional) Create a symlink for convenience**:
-   ```bash
-   ln -s ~/.coder-docs-writing ~/Documents/coder-docs-writing
-   ```
+1. Review or contribute to the shared files:
 
-3. **(Optional) Create a shell alias for quick access**:
-   ```bash
-   alias dockb='cd ~/.coder-docs-writing && nvim'
-   ```
+    1. Use `style-guide.md` to guide any edits or submissions.
 
-4. **Review or contribute to the shared files**:
-   - Use `style-guide.md` to guide any edits or submissions.
-   - Use `architecture-notes.md` to share system behavior or insights.
-   - Use `ai-project-notes.md` for project context and session memory.
-   - Use `claude-code-config.md` to align Claude’s output with established documentation expectations and Git/image handling workflows.
+    1. Use `architecture-notes.md` to share system behavior or insights.
 
-5. **For AI usage**, upload or reference the relevant files during prompts to ChatGPT or Claude.
+    1. Use `ai-project-notes.md` for project context and session memory.
+
+    1. Use `claude-code-config.md` to align Claude’s output with established documentation expectations and Git/image handling workflows.
+
+1. For AI usage, upload or reference the relevant files during prompts to ChatGPT or Claude.
 
 ---
 
@@ -96,25 +103,32 @@ Documentation paths should refer to content under `../coder/docs/`. Image assets
 Say you're documenting a new Coder feature and want to ensure style consistency:
 
 1. Upload `style-guide.md` and `architecture-notes.md` to your LLM session.
-2. Paste in raw markdown from a WIP doc.
-3. Prompt: _"Review this content using my style guide and Coder architecture notes."_
+
+1. Paste in raw markdown from a WIP doc.
+
+1. Prompt: _"Review this content using my style guide and Coder architecture notes."_
 
 Or:
 
-4. After wrapping a long LLM session:
-   Prompt: _"Summarize what we just discussed and add it to `ai-project-notes.md` in today's date section."_
+1. After wrapping a long LLM session:
+
+    Prompt: _"Summarize what we just discussed and add it to `ai-project-notes.md` in today's date section."_
 
 Coworkers can also use the same context files when jumping in to help maintain consistency.
 
 ---
 
 ## Next Steps
 
-- ✅ Populate `style-guide.md` and `doc-template.md` based on current habits
-- ✅ Start using `ai-project-notes.md` as a running journal with daily notes
-- 🔁 Invite team members to contribute and update key files collaboratively
-- ⏳ Optionally script or automate note updates from PRs, commits, or AI output
-- 📎 Claude config now reflects all previous Claude-specific guidance (including Git/image behavior and prompt strategy)
+1. Populate `style-guide.md` and `doc-template.md` based on current habits
+
+1. Start using `ai-project-notes.md` as a running journal with daily notes
+
+1. Invite team members to contribute and update key files collaboratively
+
+1. Optionally script or automate note updates from PRs, commits, or AI output
+
+1. Claude config now reflects all previous Claude-specific guidance (including Git/image behavior and prompt strategy)
 
 ---
 
@@ -123,22 +137,34 @@ Coworkers can also use the same context files when jumping in to help maintain c
 This repo is meant to be shared across documentation contributors and AI assistants. Please follow these guidelines when editing or proposing changes:
 
 ### General Rules
-- **Do not use emojis** in headings or list items
-- **Use relative paths** for internal links and image references
-- All code blocks should have a language identifier (e.g., `bash`, `json`, `md`)
-- Refer to `style-guide.md` before formatting or revising content
+
+1. **Do not use emojis** in headings or list items
+
+1. **Use relative paths** for internal links and image references
+
+1. All code blocks should have a language identifier (e.g., `bash`, `json`, `md`)
+
+1. Refer to `style-guide.md` before formatting or revising content
 
 ### File Guidelines
-- `style-guide.md`: Contribute formatting rules, tone notes, or markdown patterns
-- `architecture-notes.md`: Document internal behavior of the Coder system
-- `ai-project-notes.md`: Add time-stamped entries summarizing decisions, quirks, or updates
-- `templates/`: Extend with new skeletons or reusable snippets
-- `integration/`: Do not remove AI configuration files — update with care
+
+1. `style-guide.md`: Contribute formatting rules, tone notes, or markdown patterns
+
+1. `architecture-notes.md`: Document internal behavior of the Coder system
+
+1. `ai-project-notes.md`: Add time-stamped entries summarizing decisions, quirks, or updates
+
+1. `templates/`: Extend with new skeletons or reusable snippets
+
+1. `integration/`: Do not remove AI configuration files — update with care
 
 ### Git Practices
-- Always branch from `main`
-- Use descriptive branch names (e.g., `fix/agent-notes`, `feat/add-provisioning-snippets`)
-- Keep PRs focused and small when possible
+
+1. Always branch from `main`
+
+1. Use descriptive branch names (e.g., `fix/agent-notes`, `feat/add-provisioning-snippets`)
+
+1. Keep PRs focused and small when possible
 
 This keeps the repo clean, traceable, and AI-friendly.