Skill UI

This agent is dedicated to systematically exploring technical ideas, such as new features, refactoring, or bug fixes, *before* committing to code changes. It investigates the existing codebase, analyzes current architecture, compares multiple potential approaches (including pros, cons, and effort), and generates a structured 'exploration' report with a clear recommendation and identified risks. It ensures thorough planning and risk mitigation during the design phase.

This skill enables applying John Ousterhout's design principles to reduce complexity in software systems. It guides decisions on module boundaries, API design, information hiding, and abstraction depth. Use it when refactoring shallow interfaces or managing cognitive load during development. Ideal for architects and senior engineers optimizing system structure and ensuring maintainable codebases through proper abstraction layers.

Apply Martin Fowler-inspired refactoring rules to improve existing code structure while preserving observable behavior. Covers code smells, small safe refactoring steps, test-backed cleanup, and separating refactoring from feature changes.

This skill applies Refactoring.Guru-inspired rules for diagnosing code smells and selecting appropriate refactoring techniques. It helps preserve behavior while avoiding uncontrolled redesign. Before making design or code decisions, read the mini rules first. Use the full guide only as a deeper reference when needed. It ensures targeted cleanup without over-engineering.

This skill allows delegating self-contained coding tasks to assistants like Codex or Claude Code via non-interactive background processes. It supports feature development, code review, and refactoring. Use OpenSquilla's exec_command and process tools to manage sessions, poll output, and send inputs without blocking the main workflow. Ideal for tasks requiring substantial file exploration.

A set of behavioral guidelines derived from Andrej Karpathy's observations to help users writing, reviewing, or refactoring code with Large Language Models (LLMs). It guides developers to avoid overcomplication, make surgical changes, explicitly surface assumptions, and define verifiable success criteria, promoting clean, simple, and robust code development.

This skill provides a comprehensive guide for optimizing Angular applications. It covers performance bottlenecks, bundle size reduction, and rendering efficiency. Use it when writing, reviewing, or refactoring Angular code to ensure optimal speed and load times.

This skill performs a comprehensive architecture audit on codebases by mapping module dependencies and checking layering integrity. It identifies structural decay using principles from classic engineering books. The tool generates Mermaid dependency graphs, assesses testability seams, and applies Conway's Law checks to ensure architectural health. It is suitable for developers needing to understand codebase structure, review folder organization, or detect circular imports before refactoring.

Resume interrupted project work from saved handoffs and current checkout evidence, reconciling completed tasks, pending changes, and user constraints without inventing success or resetting a dirty working tree.

This skill specializes in code refactoring using clean code principles and SOLID patterns. It helps improve code quality, maintainability, and performance by reducing complexity and duplication. Use it for tangled code, preparing modules for new features, or improving testability. Avoid for small fixes or documentation-only requests.

This skill helps identify technical debt in software projects by analyzing code and change history. It estimates impact, prioritizes improvements, and creates actionable remediation plans. Focuses on code quality, architecture, testing, and infrastructure issues to reduce maintenance costs and improve development velocity.

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use it to clean up code, reduce unnecessary complexity, improve readability, and align recent edits with project-specific best practices.