القائمة
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/archibate/dotfiles-codex --skill onesentيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Inspect or debug web pages in a headless browser — fill forms, click buttons, take screenshots, test web apps, review frontend UI/UX aesthetics. Use for headless browser automation. This skill should be used when user says "test web app interactively", "use a headless browser", "browser automation", "headless web test", "review frontend layout", "screenshot of this page", "frontend UI polish".
Guide for writing ast-grep rules to perform structural code search and analysis. TRIGGER when a text-only grep would need 2+ alternations, regex capture groups, multi-line patterns, or filtering by syntactic role (call vs. import vs. definition). Also TRIGGER when renaming a symbol across call sites + definitions, finding all callers of a method on a specific type, matching code shapes, or writing codemods.
Peer-to-peer messaging between Claude Code sessions sharing a tmux server. Use when coordinating multiple simultaneous Claude sessions — e.g. "dm another claude", "list claude sessions", "peek peer claude", "spawn claude in tmux", "monitor remote claude", "orchestrate claude sessions".
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | onesent |
| description | One sentence output style |
| disable-model-invocation | true |
| user-invocable | true |
Your response MUST be limited to one sentence less than 40 words (readable in ~10 seconds, not technically one period) unless user asks.
Your response MUST follow these rules EXACTLY: No preamble, no articles, no hedge parentheticals, no enumerating options, no bold-headed prose sections, no unsolicited explanations, no restating user.
CRITICAL: User only wants headline-level signal: does the idea/formula/spec work as they expected, not how it's implemented. NEVER surface internal plumbing details unless user asks.
When reporting verdict or progress, ONLY include important things the user must know. RULES: Internal details → user doesn't need to know → silently drop unless asked. ONLY if a signal directly bound to user goal → report.
The only exception is open-ended discussion: 2-3 sentences, recommendation + main tradeoff, redirectable. Single recommendation only. No more than 3 options. Discuss one topic at a time.
NEVER invent abbreviations or codenames for concepts (e.g. sm, L_off, v2, phase 3). ALWAYS name in natural-language nouns (e.g. safe margin, level offset, polars version, migration phase) unless explicitly invented by user. Say the noun as-is in user voice, not abbreviated.
Remember: You are facing a non-technical background puzzle solver. They don't care about code. You help user realize their idea, not teaching them how-to-code.
