القائمة
Challenge document design with 5-7 pedagogical questions. Checks ordering, prerequisites, and cognitive load. Works with slides (.tex, .qmd, .typ) and documents.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | devils-advocate |
| description | Challenge document design with 5-7 pedagogical questions. Checks ordering, prerequisites, and cognitive load. Works with slides (.tex, .qmd, .typ) and documents. |
| disable-model-invocation | true |
| argument-hint | [Lecture filename] |
| allowed-tools | ["Read","Grep","Glob"] |
Critically examine a document or slide deck and challenge its design with 5-7 specific questions.
Philosophy: "We arrive at the best possible document through active dialogue."
.claude/rules/ for notation conventions and narrative arcGenerate 5-7 challenges from these categories:
"Could students understand this better if we showed X before Y?"
"Do students have the background for this notation at this point?"
"Should we include an intuitive example before this formal proof?"
"Here are 2 other ways to visualize/present this concept."
"This symbol conflicts with earlier lecture usage."
"This slide has too many new symbols. Can we split?"
"If this becomes a book chapter, does this section stand alone?"
Generate 5-7 challenges from these additional categories:
"Is this section ordering optimal for the reader?"
"Is this ATS-compatible? Is the hierarchy clear?"
"Does the narrative build to a clear ask?"
"Is the argument structure compelling? Are counterarguments addressed?"
# Devil's Advocate: [Lecture Title]
## Challenges
### Challenge 1: [Category] — [Short title]
**Question:** [The specific pedagogical question]
**Why it matters:** [What could go wrong]
**Suggested resolution:** [Specific action]
**Slides affected:** [Numbers or titles]
**Severity:** [High / Medium / Low]
[Repeat for 5-7 challenges]
## Summary Verdict
**Strengths:** [2-3 things done well]
**Critical changes:** [0-2 changes before teaching]
**Suggested improvements:** [2-3 nice-to-have changes]
Create new documents in any format — Beamer slides, Typst documents, or Quarto slides. Autonomous pipeline from prompt to publication-quality output.
Syntax guide and ecosystem reference for writing Typst (.typ) files. Use this skill when writing, editing, or debugging Typst documents. Covers core syntax, common errors, packages, and best practices.
Master pipeline — compile, review, fix, and finalize any document. Auto-detects format and runs the full quality loop.
Stage, commit, create PR, and merge to main. Use for the standard commit-PR-merge cycle.
Compile any supported file type. Detects format (.typ, .qmd, .py) and runs appropriate build command.
Show current context status and session health. Use to check how much context has been used, whether auto-compact is approaching, and what state will be preserved.