Development

Control OpenCode sessions via tmux for background and parallel coding tasks.

Research software tools via source code, GitHub, web. Use when creating skills, learning new tools, finding undocumented features, or bleeding-edge patterns.

Make objects service, repair, or maintain themselves, eliminating external intervention

Divide complex objects, systems, or processes into smaller independent parts to make them more manageable, flexible, or functional

Place one object inside another, which is inside a third, maximizing space utilization and increasing system compactness

Cross-reference 39 engineering parameters in a matrix to systematically identify which of 40 inventive principles resolve your technical contradiction

Build authentic influence through inner character alignment when formal authority is insufficient

Making automatic assumptions about individuals based on their group membership rather than actual characteristics or behavior

Systematically manage application state across components using patterns like centralized stores, observable state, atomic updates, and unidirectional data flow

Test software properties with automatically generated inputs instead of hand-written examples, uncovering edge cases humans miss

Build developer ecosystems when value comes from third-party complements, not direct transactions

Systematically maximize efficiency, improve speed, and enhance responsiveness through profiling, performance budgets, bottleneck identification, and iterative optimization - apply measurement-driven approaches to reduce latency, increase throughput, and optimize resource utilization in front-end and back-end systems

Mental model for making rough estimates by thinking in powers of 10, enabling quick reasoning about scale, feasibility, and relative importance

Design systems that improve through variation, selection pressure, and inheritance of successful traits over generations

Build reactive user interfaces by binding Views to ViewModels that expose observable state and commands, separating UI from presentation logic

Separate UI from business logic using Model (data), View (UI markup), and ViewModel (presentation logic with data binding) for testable, reactive applications

Separate application logic into Model (data), View (presentation), and Controller (input handling) for maintainable software architecture

Separate user interface logic into Model (data), View (presentation), and Controller (input handling) for maintainable, testable GUI applications

Minimize dependencies and maximize modularity between system components through well-defined interfaces, abstraction layers, and separation of concerns - enable independent deployment, component isolation, and parallel team evolution when building software requiring flexibility, testability, and long-term maintainability

Build exponential value as adoption grows by creating shared communication standards when establishing protocols that benefit from universal participation

Model decay processes by the time required for half of a quantity to degrade, enabling exponential decay predictions

Visualize evolutionary optimization as a search through multidimensional space where each position represents a solution and height represents fitness

Comprehensive methodology for creating and maintaining scalable, consistent design through reusable components, patterns, and documentation

Systematic decision-making process for choosing optimal data structure based on problem requirements, performance constraints, and operational characteristics