← Dyslex.aiCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Dyslex.ai
Snapshot Sep 30, 2026 · 23:13 UTC · version 0.3.7
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "identifier-safety",
"description": "Protect technical identifiers from automatic correction. Use during rewriting, typo handling, proofreading, diffs, terminal output summaries, code explanations, or any task containing commands, paths, URLs, package names, variables, hashes, keys, or regexes.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 217
}
],
"skill_md_contents": "---\nname: identifier-safety\ndescription: Protect technical identifiers from automatic correction. Use during rewriting, typo handling, proofreading, diffs, terminal output summaries, code explanations, or any task containing commands, paths, URLs, package names, variables, hashes, keys, or regexes.\n---\n\n# Identifier Safety\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\nTechnical tokens are data. Preserve them exactly unless the user explicitly asks for a change.\n\n## Protect\n\n- Variables, functions, classes, methods\n- File paths and URLs\n- Commands and CLI flags\n- Package names and imports\n- JSON keys and environment variables\n- Branch names, commit hashes, IDs\n- Regular expressions and quoted strings\n\n## If A Token Looks Wrong\n\nSay that it may be wrong. Do not silently fix it.\n\nUse this wording:\n\n```text\nPossible technical-token issue: `<token>` may be intended as `<candidate>`. Confirm before changing it.\n```\n"
}SHA-256: 25e82cfad72a0003771e99e24d157049db246dc1e2df5f247ef1c945cb3fc630