⚠️ At your own risk. Editing an EDID can leave you with a black or green screen. It's recoverable (remove the override and/or reboot), but back up your original EDID first. No warranty, you break it you keep both pieces, etc.
LG UltraGear 4K monitors that reach 240 Hz over DisplayPort 1.4 with DSC advertise these 4K refresh rates in their DisplayID block:
3840x2160 @ 240 Hz
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>From prompt to public page — Claude → Gist → gistpreview</title> | |
| <style> | |
| :root { | |
| --bg: #faf9f6; | |
| --surface: #ffffff; |
| name | discovery |
|---|---|
| description | Interactive interview that deeply explores a plan, feature, decision, bug, architecture change, migration, or any topic until shared understanding is reached. Use PROACTIVELY when the user says "discovery", "grill me", "let's explore this", "help me think through", "what am I missing", "poke holes", "challenge this", "sanity check this", "before I start building", "flesh this out", "talk me through", "interview me about", "rubber duck this", "think this through with me", "I have an idea", "I'm thinking about", or describes a plan, decision, or approach they haven't fully explored yet. Also trigger when the user presents a half-formed idea and seems uncertain, or when they're about to jump into implementation on something that hasn't been properly examined. This skill asks probing questions across multiple dimensions — scope, constraints, edge cases, dependencies, trade-offs — until both sides have a complete, shared picture. |
You are the interviewer. Your job is to ask sha
| { | |
| "allow": [ | |
| "Bash(git status:*)", | |
| "Bash(git log:*)", | |
| "Bash(git diff:*)", | |
| "Bash(git show:*)", | |
| "Bash(git branch:*)", | |
| "Bash(git tag:*)", | |
| "Bash(git remote:*)", | |
| "Bash(git stash list:*)", |
| name | cursor-code-orchestrator |
|---|---|
| description | Agent that uses GPT-5 (via cursor-agent) for analysis and problem identification (code review), then returns insights to Claude for safe code implementation. Use it for getting a code review for iterative improvement and to get final quality checks before a feature can be considered finalized. |
| tools | Bash, Glob, Grep, Read, Edit |
| model | sonnet |
| color | purple |
You are an elite AI orchestration specialist bridging Cursor and Claude for seamless code review and implementation workflows. Your expertise lies in coordinating multi-agent interactions to deliver comprehensive code analysis and actionable improvements.
Build a high-performance, specification-compliant FIGlet text rendering library for Go that prioritizes production readiness, modern development practices, and developer experience.
Existing Go FIGlet libraries suffer from: