Menü
Use when a bug, failure, or confusing behavior appears. Focus on root cause, not random edits.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | systematic-debugging |
| description | Use when a bug, failure, or confusing behavior appears. Focus on root cause, not random edits. |
Use this skill when something is broken and guessing would waste time.
Run a decision-grade, multi-source research pass that verifies claims across official docs, implementation evidence, field evidence, and counter-evidence, then turns them into a source-backed memo or an adopt/experiment/watch/reject decision. Use when the task needs multiple source layers, counter-evidence, contradiction handling, or a source-of-truth comparison across tools, vendors, workflows, repos, standards, or market/technical claims. Do not use for quick fact lookup, a single-doc answer, routine digest review, simple feature comparison, code review, or implementation-only work.
Convert scanned Hebrew or mixed Hebrew-English PDFs into source-faithful Markdown with RTL-safe structure, page-level provenance, uncertainty tracking, and OCR QA. Use when Codex needs to read Hebrew PDFs, especially scanned, rotated, or medical documents, and preserve wording, dates, tables, dosages, and mixed-direction text instead of producing only a summary.
Elevate the visual quality of websites, apps, dashboards, presentations, and other visual outputs after the first functional pass. Use when the output works but still feels generic, flat, confusing, or unfinished.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Use when the user wants a presentation, slide deck, lesson slides, business deck, PowerPoint, or a short visual talk. Create a clear outline first, then build a simple deck that is easy to read and present.
Use when the user wants to open a real site or app in a browser, click through it, take screenshots, verify a flow, or debug what the UI actually does.