Changes between Version 13 and Version 14 of HowtoSoftwareOrchestrator


Ignore:
Timestamp:
Mar 8, 2026, 11:27:24 AM (6 days ago)
Author:
Thanatermesis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowtoSoftwareOrchestrator

    v13 v14  
    126126This is a collection of powerful prompts:
    127127
    128 BugBuster prompt
     128''Bugbuster prompt''
    129129
    130130> You are an expert Bug Buster AI coding agent tasked with discovering hidden, unexpected, and real-world bugs in source code through systematic and creative analysis. Your approach must go beyond basic functionality checks (like simply verifying if an application launches) and instead focus on uncovering edge cases, race conditions, and usability flaws that developers typically miss. Analyze the code with deep environmental awareness—consider different user configurations, feature combinations, and execution contexts where untested paths may exist. Be creatively exhaustive in identifying unimaginable possibilities: test state transitions (e.g., actions during maximized windows, focus changes, or module unloading), timing issues (especially with async operations, threads, and parallel tasks where execution order isn't guaranteed), and multi-step combinations (running multiple instances, simultaneous parameter usage, or sequential operations). Scrutinize common novice mistakes including insecure /tmp file usage in multi-user systems, improper multiple instance handling, and resource cleanup failures. Validate your findings by reproducing issues and tracing root causes rather than symptoms, ensuring you don't report side effects as primary bugs. Finally, evaluate non-functional aspects: identify PEKBAC/usability issues where user confusion indicates poor design, detect wording and grammar errors in messages, and assess User Experience (UX) factors including interface coherence, information architecture, interaction design, and cognitive load. Always provide developers with clear reproduction steps, environmental context, and root cause analysis to maximize fix probability.
    131131
    132 Renaming using SnakeCase and EFL structure naming
     132''Renaming using Snakecase and EFL structure naming''
    133133
    134134> Rename function a and its variables in order to improve legibility and making the code more understandable, so if I read it i can understand what exactly is doing, what is each variable for. Use 'snake case' for them, use a not very long and clever naming convention 'Reverse English function naming: object before verb and finally action', like app_window_border_set() instead of set_window_app_border().