القائمة
Use this skill for prompt-only review, repair, and re-review where the prompt must be improved without executing the workflow it describes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use this skill for backend API, DTO, or enum changes that require frontend request wrappers, types, enums, or UI adaptations.
Use this skill for durable execution records, runbooks, evidence folders, artifacts, and validation of archive layout after task completion.
Use this skill for validated local commit and optional push workflows where scope, staged content, identity, gates, and human confirmation must be handled explicitly.
Use this skill for desktop productivity UI design systems, design tokens, dense tables, status markers, theme tokens, and non-AI-looking Electron app visual standards.
Use this skill for Electron desktop packaging and release readiness across Windows, macOS, and Linux, including signing boundaries, artifacts, dry-runs, and public release checks.
Use this skill for cross-platform desktop UI QA of Electron apps, including renderer screenshots, native window behavior, shell prerequisites, task logs, and platform-specific checks.
استنادا إلى تصنيف SOC المهني
| name | prompt-qa |
| description | Use this skill for prompt-only review, repair, and re-review where the prompt must be improved without executing the workflow it describes. |
| os | cross-platform |
Use this Skill when the situation matches the frontmatter description. It is cross-platform and tool-neutral: judgment, sequencing, risk boundaries, and human confirmation points live here; deterministic checks should be delegated to installed workflow runtime paths first, then to source repository paths when the runtime is not installed.
os: cross-platform. Prompt review is text-first and should not depend on platform-specific commands unless the prompt itself names a platform boundary.
Prefer installed runtime paths:
~/.agent-routines/workflows.agent-routines/workflowsSource fallback:
workflows/<workflow-name>/Recommended workflows: none required
Ask before executing any workflow described by the prompt, accessing external systems, mutating files, committing, pushing, publishing, installing, or authorizing tools.
If a prompt cannot be made safe without a missing product decision, mark the ambiguity as BLOCKED instead of filling it with a risky assumption.