القائمة
Use when a request is feature design heavy, ambiguous, or likely to change architecture. Turn ideas into an approved design before implementation handoff.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when writing technical articles, blog posts, X/Twitter threads, LinkedIn posts, documentation, runbooks, or any text that must sound like a specific person, not a generic assistant. Also use when the user asks to humanize text, remove AI-sounding language, rewrite in their voice, or convert rough notes into publishable content. Trigger even when the user just says "write this up" or "draft a post about X" without explicitly mentioning voice or tone.
Use when reviewing architecture, planning refactors, reducing coupling, improving testability, or deciding whether modules should become deeper behind simpler interfaces.
Use when the user asks for caveman mode, terse mode, fewer tokens, less prose, or very brief technical communication.
Use for hard bugs, failing checks, pipeline failures, homelab incidents, performance regressions, or reports that something is broken and needs root-cause analysis.
Use before git mutation, branch deletion, resets, cleaning, force pushes, broad restore commands, PR operations, or any git action with destructive or remote side effects.
Use when a plan, design, or implementation request has ambiguity that could change scope, architecture, acceptance criteria, safety, or validation.
| name | brainstorming |
| description | Use when a request is feature design heavy, ambiguous, or likely to change architecture. Turn ideas into an approved design before implementation handoff. |
Use this skill when at least one is true:
Do not use for small, already-clear single-file fixes.
Do not implement code changes until a design direction is presented and accepted.
ls, rg) first to map relevant modules and constraints.ideate subagent.writer subagent.Return these sections:
Context: relevant files, constraints, and assumptions.Options: 2-3 approaches with pros and risks.Recommendation: preferred approach and reasoning.Proposed design: implementation-ready outline.Approval gate: explicit prompt for user approval before implementation.