Agent skill · 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.
What it needs
About 4k tokens when loaded.
What this skill does
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 subagenttype: "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 1. 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). 2. Match a playbook. Copy its steps into the todolist before any bespoke plan. Skipped step → skip: <reason>. 3. Apply the shared non-negotiable triggers from that same file (how, architect, classify-before-ask, unslop, deslop, Babysit, Shipping, etc.). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills cursor/dyl-mode