القائمة
Use when the user wants contract-preserving simplification, anti-slop cleanup, or a final-pass polish after the main decision is made.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants architecture-first product and system design with explicit stack rationale, boundaries, tradeoffs, data model choices, and phased delivery planning.
Use when the user wants to decide whether implementation is ready, what remains blocked, and what the exact next build step should be.
Use when the user wants logic validation: states, transitions, invariants, edge cases, dead ends, and blockers before implementation.
Use when the user wants evidence-backed technology choices, OSS evaluation, and source-grounded validation of the stack proposed in `$arch`.
Use when the user wants a security and trust-boundary review of the current design before implementation or release.
Use when the user wants a DX and UX review of the planned workflow before implementation proceeds.
| name | cleanup |
| description | Use when the user wants contract-preserving simplification, anti-slop cleanup, or a final-pass polish after the main decision is made. |
Use this skill inside Codex when the core behavior is understood but the artifact still needs simplification, deslop work, or clearer prose. cleanup is a non-gating helper skill.
Produce:
references/style-and-deslop.md for simplification and prose cleanup patterns.