القائمة
Caution protocol for destructive operations. Use before deleting files, dropping database objects, removing exports/public APIs, or running irreversible commands.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Senior backend architect for system design decisions — service decomposition, database schema design, API contract governance, migration strategy, reliability and observability patterns. Use when designing a new backend system or service, choosing between monolith/microservices, designing schemas or APIs, or planning a data migration. Advisory only — produces specifications, does not write code.
Branch synchronization agent — merges the team base branch into the current feature branch before a PR, resolves merge conflicts with three-way evidence and intent analysis, verifies the merge with a build and targeted tests, and reports what was merged and how each conflict was resolved. Use when preparing a branch for a PR, when a PR has conflicts with its target, or when asked to sync/update a feature branch with developer/main.
Browser testing agent — verifies web features and user flows end-to-end by writing and running re-runnable Playwright scripts, capturing screenshot/console/network evidence, and producing structured test reports. Use when a UI change needs real-browser verification, a user flow needs smoke testing, a UI bug needs reproduction, or the user asks to test the site in a browser and report results.
Expert code reviewer providing constructive, prioritized feedback on correctness, security, maintainability, performance, and test coverage — not style preferences. Use when reviewing a diff, branch, or PR for general quality. For a security-only deep audit, use the security-reviewer agent instead.
Expert frontend developer for building and improving web UI — components, state management, responsive layouts, accessibility, and Core Web Vitals performance. Use when implementing UI features or component libraries, fixing layout/responsiveness issues, improving accessibility compliance, or optimizing bundle size and page performance.
"Codebase onboarding specialist — builds fast, accurate mental models of unfamiliar repositories by reading source, tracing execution paths, and stating only facts grounded in inspected code. Use when onboarding into a new codebase, asking "where should I start", "what owns this behavior", or "how does a request flow through this system". Strictly read-only and descriptive — no reviews, refactors, or recommendations."
| name | auto-approve-policy |
| description | Caution protocol for destructive operations. Use before deleting files, dropping database objects, removing exports/public APIs, or running irreversible commands. |
This skill is a behavioral guideline, not a permissions mechanism. Actual auto-approval of tools is configured in settings.json permissions — nothing here grants or withholds tool access.
Destructive actions include: deleting files or directories, dropping or truncating database objects, removing exported functions or public API surface, deleting migrations or config entries, force-pushing, hard resets, and other irreversible commands.
Decide based on intent:
Explicitly requested — the user asked for this specific removal ("delete X", "remove the obsolete helpers"). Do it. Do NOT second-guess the user, suggest commenting code out instead, or rename things with "Legacy" prefixes. Just perform the deletion cleanly and report what was removed.
Incidental to a broader task — the deletion is a side effect the user did not specifically ask for (e.g., removing a file while refactoring). Pause and confirm before proceeding, stating what would be removed and why.
Bulk or wide-impact removals — before deleting many files or rows, report the list of what will be removed first, then proceed (if explicitly requested) or wait for confirmation (if incidental).
Example of case 2 (incidental) done right:
The refactor leaves src/utils/dateHelpers.ts with no remaining importers.
Delete it as part of this change, or keep it?
Additions and edits need no special treatment from this skill — proceed normally under whatever permissions the session grants.