style(docs): replace em/en-dashes with ASCII hyphens

- Replace U+2014 (em-dash) and U+2013 (en-dash) with '-' across
  rules and skills for plain-ASCII consistency
- Scoped via rg (respects .gitignore); no changes to .git,
  node_modules, or lockfiles
- 37 replacements across 17 files; no semantic changes

Author: d-padmanabhan

rules/010-workflow.mdc

@@ -93,7 +93,7 @@ For non-trivial work, keep a single “north star” scope document and use it t
 - **Rule**: Break work into features small enough for the agent to execute reliably (one feature per cycle)
 
 **When to create `tmp/design.md`:**
-- Level 3–4 tasks (multi-module or architectural)
+- Level 3-4 tasks (multi-module or architectural)
 - Any time there are multiple valid approaches with meaningful tradeoffs
 - Any time interfaces, data models, or operational behaviors might change
 

rules/015-context-engineering.mdc

@@ -38,9 +38,9 @@ This rule strengthens agent performance by making context **intentional**, **min
 ### Always carry (paste/recap)
 
 - **Goal**: one sentence
-- **Non-goals**: 1–3 bullets
+- **Non-goals**: 1-3 bullets
 - **Constraints**: security, tooling, performance, “don’t refactor”, etc.
-- **Current plan**: 3–7 steps max
+- **Current plan**: 3-7 steps max
 - **Current state**: what’s done / what’s blocked
 - **Critical artifacts**: exact file paths, key identifiers, and error messages (verbatim)
 

rules/100-core.mdc

@@ -486,7 +486,7 @@ def process_order(order_id: int) -> Order:
 
   * Over-engineered abstractions for simple problems.
   * Premature optimization.
-  * Extensive test suites (provide 1–2 examples instead).
+  * Extensive test suites (provide 1-2 examples instead).
   * Complex frameworks when stdlib suffices.
   * Features not in requirements.
   * Generic boilerplate text or “best practices” not tied to the task (“AI slop”).

rules/130-git.mdc

@@ -51,7 +51,7 @@ git merge origin/main        # Integrate when ready
 
 **What is the Reflog?**
 
-The **reflog** (reference log) is Git's time machine. While `git log` shows only commits reachable from branches/tags, the reflog records **every movement of HEAD** — every checkout, reset, commit, rebase, branch switch, and even "lost" commits.
+The **reflog** (reference log) is Git's time machine. While `git log` shows only commits reachable from branches/tags, the reflog records **every movement of HEAD** - every checkout, reset, commit, rebase, branch switch, and even "lost" commits.
 
 **Key insight:** The reflog remembers everything, even commits that appear "lost" from your branch history. This makes Git operations reversible and gives you confidence to experiment.
 
@@ -63,7 +63,7 @@ The **reflog** (reference log) is Git's time machine. While `git log` shows only
 - **Debugging** - Track "what commit was I on 20 minutes ago?"
 - **Learning** - Understand Git internals by watching HEAD movements
 
-**Reflog is your safety net** — it makes "dangerous" operations safe because you can always undo them.
+**Reflog is your safety net** - it makes "dangerous" operations safe because you can always undo them.
 
 ### Basic Reflog Usage
 
@@ -794,7 +794,7 @@ pre-commit autoupdate
 Every repo **must** contain the following foundational files with project-appropriate content.
 
 > [!IMPORTANT]
-> **Always use `.yaml` extension, NOT `.yml`** — This is a project-wide convention for consistency and clarity.
+> **Always use `.yaml` extension, NOT `.yml`** - This is a project-wide convention for consistency and clarity.
 
 ## Required Files
 

rules/200-python.mdc

@@ -2971,7 +2971,7 @@ def function_name(param: str) -> int:
 ## 17) Scaling Guidelines
 
 - **Small Scripts (<50 lines):** Stick to basics - skip advanced features unless critical.
-- **Medium Scripts (50–200 lines):** Add type hints, logging, small functions. Consider `argparse` or `Pydantic`.
+- **Medium Scripts (50-200 lines):** Add type hints, logging, small functions. Consider `argparse` or `Pydantic`.
 - **Large Projects (>200 lines):** Use OOP, SOLID principles, plugins, deployment tools. Optimize with profiling/concurrency.
 
 ## 18) Example Script

rules/412-aws-iam.mdc

@@ -194,7 +194,7 @@ If a vendor assumes a role in your account, require an `ExternalId` and lock to
 
 When a **resource-based policy** grants access to an **AWS service principal** (for example,
 `cloudtrail.amazonaws.com`, `events.amazonaws.com`, `sns.amazonaws.com`), the policy is trusting the
-service principal — not the human/role that configured the calling service.
+service principal - not the human/role that configured the calling service.
 
 To reduce confused-deputy risk, restrict the service principal with global condition keys:
 

rules/800-markdown.mdc

@@ -486,11 +486,11 @@ Use standard Markdown links so URLs render as clickable in GitHub, IDEs, and com
 
 - **Preferred**: `[AWS Lambda documentation](https://docs.aws.amazon.com/lambda/)`
 - **Avoid for navigation**: bare URLs in running text when a short label reads better (still use `https://...` in link target)
-- **Do not** wrap URLs that readers should **click** in backticks: `` `https://docs.aws.amazon.com/lambda/` `` — inline code styling often prevents click-through and copies poorly.
+- **Do not** wrap URLs that readers should **click** in backticks: `` `https://docs.aws.amazon.com/lambda/` `` - inline code styling often prevents click-through and copies poorly.
 
 ### When backticks around a URL are correct
 
-Wrap a URL in backticks only when it is a **literal value**, not a navigation affordance—for example: configuration samples, CLI transcripts, log lines, schema defaults, or strings inside code-oriented examples.
+Wrap a URL in backticks only when it is a **literal value**, not a navigation affordance-for example: configuration samples, CLI transcripts, log lines, schema defaults, or strings inside code-oriented examples.
 
 ### Paths and anchors
 

rules/810-documentation.mdc

@@ -250,9 +250,9 @@ Prefer **neutral** or **imperative** phrasing over second-person voice.
 
 ### Punctuation
 
-**Never use em dashes (—) or en dashes (–). Use hyphens (-) instead.**
+**Never use em dashes (-) or en dashes (-). Use hyphens (-) instead.**
 
-- **Bad:** `Astral's type checker—10x faster than mypy—is now available.`
+- **Bad:** `Astral's type checker-10x faster than mypy-is now available.`
 - **Good:** `Astral's type checker - 10x faster than mypy - is now available.`
 
 **Rationale:**

skills/agent-workflow/references/context-engineering.md

@@ -33,9 +33,9 @@ It complements:
 ### Always carry
 
 - **Goal**: one sentence
-- **Non-goals**: 1–3 bullets
+- **Non-goals**: 1-3 bullets
 - **Constraints**: security, tooling, “don’t refactor”, etc.
-- **Current plan**: 3–7 steps max
+- **Current plan**: 3-7 steps max
 - **Current state**: what’s done / what’s blocked
 - **Critical artifacts**: exact file paths, key identifiers, and error messages (verbatim)
 

skills/agent-workflow/references/context-management.md

@@ -41,7 +41,7 @@ For non-trivial work, keep a single “north star” scope document and use it t
 
 **When to create `tmp/design.md`:**
 
-- Level 3–4 tasks (multi-module or architectural)
+- Level 3-4 tasks (multi-module or architectural)
 - Any time there are multiple valid approaches with meaningful tradeoffs
 - Any time interfaces, data models, or operational behaviors might change