← Dyslex.aiCONTENT HISTORY

Update to Dyslex.ai

Snapshot Sep 30, 2026 · 23:13 UTC · version 0.3.7

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Infer likely user intent from typos, spelling errors, dysorthography, or malformed wording. Use when the request has mistakes but the likely task is still clear; preserve technical tokens exactly.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 220
    }
  ],
  "name": "typo-tolerant-intent",
  "skill_md_contents": "---\nname: typo-tolerant-intent\ndescription: Infer likely user intent from typos, spelling errors, dysorthography, or malformed wording. Use when the request has mistakes but the likely task is still clear; preserve technical tokens exactly.\n---\n\n# Typo-Tolerant Intent\n\n## Superpowers Gate\n\nBefore applying this skill, verify that Superpowers is available in the current session, such as an active `superpowers:` skill, `using-superpowers`, or equivalent Superpowers workflow instructions.\n\nIf Superpowers is missing or uncertain, stop and reply exactly with this guidance before doing any dyslex.ai work:\n\n```text\ndyslex.ai requires Superpowers before it can run. Install Superpowers from /plugins, or use codex plugin add superpowers@<marketplace> if you manage plugins from the Codex CLI, then start a new session.\n```\n\nDo not perform the requested dyslex.ai workflow until Superpowers is installed and loaded.\n\nInterpret the likely request without calling attention to every mistake.\n\n## Process\n\n1. Identify the likely user goal.\n2. Preserve paths, commands, package names, identifiers, URLs, numbers, and quoted text exactly.\n3. Ask a clarification only when two interpretations would materially change the work.\n4. If clarification is needed, ask one direct question and include the concrete alternatives.\n\n## Do Not\n\n- Do not publicly list every typo.\n- Do not silently correct technical identifiers.\n- Do not assume a medical condition from writing style.\n- Do not turn minor uncertainty into an interrogation.\n"
}

SHA-256 of public snapshot: f523fff06ba25d570cae9527f538d3cbc70778720bd26ac375041e0d8ee75162