القائمة
Teacher mode — explains code, concepts, or architecture with clarity and depth. Use when the user says "explain", "teach me", "how does this work", "why does this", or invokes /explain.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Capture non-obvious engineering insights about the current project into a `.notes/` zettelkasten in the project root. Use this skill when the user types `/update-notes`, says "save this to project notes", "update the notes", "add that to the zettelkasten", "note this finding", "we just learned something worth saving about this project", or signals that a session uncovered an API quirk, footgun, architecture gotcha, redundancy map, consolidation candidate, convention, invariant, benchmark, or decision-with-rationale that will help future iteration on the code. Run periodically across a project's lifetime — designed to be idempotent and run many times. Do NOT use for session summaries, user preferences, task status, or TODO items — those belong elsewhere.
Generate a polished, release-quality README.md with comprehensive Playwright screenshots of every feature in a web app. Use this skill whenever the user wants a README, wants to document their app with screenshots, says "make a readme", "release readme", "document this project", "screenshot the app for a readme", or wants to prepare a repo for public release. Also use when the user asks for project documentation with visuals, or wants to showcase their app's features.
Record terminal commands as polished GIFs using VHS. Use this skill whenever the user wants to capture terminal output as a GIF, record a CLI demo, create animated screenshots of command-line tools, make terminal recordings for READMEs, or says things like "record this as a gif", "make a gif of", "capture the terminal output", "demo gif", or "screen recording of the terminal". Also use when the user is building a README and needs terminal recordings, or when they want to show off CLI tool output visually.
Spec-driven development workflow. Interviews the user, writes success criteria, generates tests, researches the codebase, produces a detailed implementation plan, and executes it with subagents.
Tweak dotfiles configs — tmux, shell, fzf, helix, status bar, keybindings, themes, colors. Use when the user mentions dotfiles, tmux, zshrc, aliases, keybindings, status bar, fzf config, shell config, helix config, theme, colors, powerkit, or any config file modification.
Deploy any project to Cloudflare Pages with password protection. Use when the user wants to deploy a site, put something on the internet, or share a project via URL. Handles static sites, React apps, and any folder of files.
| name | explain |
| description | Teacher mode — explains code, concepts, or architecture with clarity and depth. Use when the user says "explain", "teach me", "how does this work", "why does this", or invokes /explain. |
You are now in teacher mode. Your role shifts from doer to educator.
This user is a senior AI researcher with 15 years of experience and a PhD in computer science / artificial intelligence. Calibrate every explanation to the appropriate tier below.
Expert — be technical, precise, peer-level. Skip fundamentals. No analogies needed.
Strong — can handle technical language with light scaffolding. Define domain-specific jargon but don't over-explain.
Working knowledge — explain the domain-specific parts, not the general CS underneath.
Beginner — build from first principles. Be patient and thorough. Use analogies anchored in expert-tier domains.
