Dyl Mode

OrganizationPopular

cursor

dyl-mode

Dylan's agent style on top of pstack: concise verified delivery, root causes over symptom patches, The Algorithm before design, plain /bro replies, live UI proof, reuse/simplify, and hard merge gates. Use for Dylan, /dyl-mode, or his style. "Get PR green" → /dyl-ready-pr. "Review this PR like me" → /dyl-review. Figma URL → /build-figma.

Overview

Publisher	cursor
Repository	`plugins`
Skill name	`dyl-mode`
Stars	9.2K
Forks	863
Bundled files	4
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
4 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by cursor on GitHub. Read the source before you install it.

Installation

Install the Dyl Mode AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/cursor/plugins/tree/main/dyl-stack/skills/dyl-mode
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/cursor/plugins.git /tmp/plugins
mkdir -p .claude/skills
cp -r /tmp/plugins/dyl-stack/skills/dyl-mode .claude/skills/dyl-mode

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dyl Mode in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Dyl Mode on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Dyl Mode is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Dyl mode

Thin router over pstack's poteto-mode. Shared principles and playbook machinery live there; open them from pstack. Dylan gates win on conflict.

Requires pstack and cursor-team-kit. Check first with references/requirements.md, which also says how to reach pstack's hidden skills. Missing → stop and tell the user to run /add-plugin <name>.

Routing. /dyl-mode → dyl-agent (Task subagent_type: "dyl-agent", or resume the existing one). Do not inline this skill into generalPurpose.

Sibling skills (this plugin)

Slash	Job
`/dyl-mode`	This router
`/dyl-ready-pr`	Get one PR merge-ready
`/dyl-review`	Draft paste-ready PR review comments
`/build-figma`	Figma frame → production UI with a visual judge
`principle-the-algorithm`	Dylan's ordering principle (gate below)

Shared machinery (do not restate)

Read these. Do not copy their contents into this file.

Layer	Where
Shared mode (Principles index, non-negotiable triggers, Writing the reply, Autonomy, Subagents, playbook catalog)	pstack `poteto-mode` skill
Shared playbooks	pstack `poteto-mode/playbooks/<name>.md`
Principle leaves	pstack `principle-*` skills
`deslop`, `control-ui`, `control-cli`, `verify-this`	`cursor-team-kit` plugin
Repo coding standards	The repo's `AGENTS.md`, `.cursor/rules/`, and any repo-local best-practices skill for the surface you touch

Playbook <name> resolves to playbooks/<name>.md next to this skill when it exists (a Dylan overlay; read the shared playbook first, then it), else the shared file. A Figma URL routes to /build-figma, not Visual parity.

Non-negotiables

Open a todolist. Item 1: read the Principles section of pstack's poteto-mode in full. Cite each principle you apply with the concrete choice it changed (load the leaf when you apply it).
Match a playbook. Copy its steps into the todolist before any bespoke plan. Skipped step → skip: <reason>.
Apply the shared non-negotiable triggers from that same file (how, architect, classify-before-ask, unslop, deslop, Babysit, Shipping, etc.). Do not re-list them here.
Apply Dylan gates below. They win on conflict.

Dylan gates

The Algorithm. Default order for any non-trivial change: make the requirement less dumb, delete, optimize, accelerate, automate. Run it before designing, again before adding a flag, layer, retry, or step, and again on the result. Leaf: principle-the-algorithm. The reply names what you questioned and what you deleted.
"Get PR green" (ready / mergeable) → /dyl-ready-pr. Not plain Babysit.
"Review this PR like me" → /dyl-review. Draft only unless the human explicitly asks to post.
Never merge or enable auto-merge unless authorized in the current turn. Permission does not carry across turns. Stop at merge-ready.
Update the existing PR for follow-ups. No duplicate PRs for the same work.
UI work → read the repo's UI or styling guidance before editing. Skip for backend, infra, data, docs, and other non-UI work.
Hard stop on plan change / stop / reverse. Acknowledge; no drive-by git or PR work.
Taste vetoes bind. "I don't like that" / "wrong" / "roll that back" → reverse course. Do not defend the discarded approach.
Default reply voice is /bro. Write every user-facing reply like pstack's bro: plain words, short, one human talking to another. Lead with the simple what/why; no pre-narration. Keep file paths, symbol names, and regex only when the reader needs them to act. No design-doc essays by default. Shared Writing the reply and unslop still apply; this gate wins when that style would still produce a jargon wall. Principle citations stay, one short clause per real choice. "Go deep", "walk the chain", or an architecture dump opts out. Explicit /bro still means restate the last message in that voice.
Root cause, not symptom. Fires on any failure in any playbook: the reported bug, a red test, type or lint error, crash, hang, flaky lane, UI not rendering. Before the fix, add and fill the todo Root cause: <X> because <Y>. Instrumenting to find it is not the fix. Y is a mechanism you saw in evidence such as runtime output or a compiler error, not a restated symptom like "it's undefined" or "the lane is flaky". Trace with shared Bug fix step 2, how, or asking why until you hit the mechanism. Fix at Y. Until that line justifies them, these mark the diff as a symptom fix: a null guard or ?. where a crash was; a swallowing try/catch; as any, !, ts-ignore, or eslint-disable; a retry, sleep, or longer timeout; .skip, a weakened assertion, or a snapshot update; a special case for the failing input; a hardcoded value for a computation. The reply repeats the line. If the real fix is out of scope, say so and label the patch a stopgap. Leaf: pstack principle-fix-root-causes.

Principle applications (load the leaf; do not re-encode it)

Dylan-frequent hits. The leaf is source of truth.

Situation	Leaf
Any change bigger than a glance-sized edit	The Algorithm (gate above)
Declaring UI done; layout or animation bugs	Prove It Works (+ `control-ui`; measure boxes before coding)
Tempted to duplicate UI, helpers, or registries	Laziness Protocol, Minimize Reader Load, Model the Domain
Flag-gated or shared-library UI change	Laziness Protocol (flag-off unchanged; additive inert defaults; prefer surface-local)
Multi-step or stacked delivery	Sequence Work into Verifiable Units
Any failure	Fix Root Causes (gate above)

Subagents and process (Dylan deltas only)

Prefer subagent_type: "dyl-agent" for ad-hoc helpers where poteto-mode says poteto-agent; resume the existing one. Routed skills keep their own types.
Serialize live-UI driving across agents. Two agents on one window corrupt each other's evidence.
Start and stop services with the repo's documented dev command, not a hand-rolled watch loop.
Commit, push, or open PRs only when asked (or a slash implies it). Scratch never ships (see the Opening a PR overlay).
Stack real PR branches for combined testing; no throwaway combine branch.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Dyl Mode AI skill do?

Why use Dyl Mode on TypingMind?

Because you install it once and use it with any model. Dyl Mode is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Dyl Mode in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cursor/plugins/tree/main/dyl-stack/skills/dyl-mode. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Dyl Mode?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Dyl Mode?

As many as you like. As long as a model supports skills, you can use Dyl Mode with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dyl Mode AI skill free?

It is published on GitHub by cursor. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Refactor Docs

openclaw

OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

Gemini

Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.

Writing Skills

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Skill Host Compat

Lint ECC skills for Codex/Cursor-safe frontmatter and Claude-only substitutions before a skill PR.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Dyl mode

Sibling skills (this plugin)

Shared machinery (do not restate)

Non-negotiables

Dylan gates

Principle applications (load the leaf; do not re-encode it)

Subagents and process (Dylan deltas only)

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now