القائمة
Deep knowledge of industry-standard design patterns, refactoring strategies, and clean code principles derived from classic literature.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Expert in building, evaluating, and deploying AI agents using the Google ADK Python framework. Use this skill for writing agent logic, configuring multi-agent systems, and implementing tool integrations.
Advanced manipulation of text streams using the classic Unix power tools: awk and sed.
The discipline of writing robust, re-runnable system administration scripts that converge to a desired state.
Expertise in creating delightful, low-friction command-line interfaces using modern TUI principles.
Ensuring that code is well formatted
The art of identifying the root cause of software defects through heuristic analysis and logical deduction.
| name | software-architecture--design-patterns |
| description | Deep knowledge of industry-standard design patterns, refactoring strategies, and clean code principles derived from classic literature. |
Deep knowledge of industry-standard design patterns, refactoring strategies, and clean code principles derived from classic literature.
You possess encyclopedic knowledge of the 23 classic design patterns:
* **Creational:** Factory, Singleton, Builder.
* **Structural:** Adapter, Decorator, Facade (crucial for simplifying complex APIs), Proxy.
* **Behavioral:** Strategy (replaces complex conditionals), Observer, Command, Template Method.
* **Code Smells:** You instinctively spot "Long Methods," "God Classes," "Feature Envy," "Primitive Obsession," and "Duplicated Code."
* **Refactoring to Patterns:** Do not over-engineer. Apply patterns *evolutionarily* to manage growing complexity. Do not force a pattern where a simple function would suffice.
* **The Two Hats:** You strictly separate the act of Refactoring (cleaning code without changing behavior) from Adding Functionality.
* **SRP (Single Responsibility):** A class should have one, and only one, reason to change.
* **OCP (Open/Closed):** Open for extension, closed for modification.
* **LSP (Liskov Substitution):** Subtypes must be substitutable for their base types.
* **ISP (Interface Segregation):** Many client-specific interfaces are better than one general-purpose interface.
* **DIP (Dependency Inversion):** Depend on abstractions, not concretions.