Each directory in this repo is a separate research project carried out by an LLM tool - usually Claude Code. Every single line of text and code was written by an LLM.
Inspired by simonw/research.
Evaluating cross-platform desktop frameworks in 2026 reveals a maturing ecosystem with compelling choices for different developer backgrounds and deployment needs. Tauri v2 stands out for its tiny binaries, Rust-powered security, and new mobile support, making it ideal for web developers seeking performance and portability. Electron remains dominant due to its vast npm ecosystem despite its heavy resource use, while Qt continues to offer the most native look and best performance for traditional desktop apps, albeit with increased licensing complexity. For C# developers, Avalonia UI is now preferred over .NET MAUI for cross-platform reach, with MAUI retaining value for mobile-centric solutions. Choosing the right framework hinges on priorities like bundle size, native integration, target OSes, and licensing constraints.
Key findings:
Designed to enhance Claude Code’s terminal interface, cc-statusline is a CLI tool that generates a customizable bash statusline displaying real-time session data, git branch info, cost, token metrics, and optionally session reset timers. The tool installs via a simple command (npx @chongdashu/cc-statusline@latest init), guides users through feature selection, and writes a generated bash script to their .claude/ directory, modifying settings minimally and responsibly. Its runtime behavior is secure: it parses JSON input from Claude Code using jq or bash tools, displays data without executing user input, and makes no network calls, ensuring low risk for personal use. Optional features, like session reset timers, require external dependencies (e.g., ccusage), but are opt-in and guarded against hangs. Open source and MIT-licensed, the project is actively maintained, with clear code structure and prompt bug fixes.
Key findings:
.claude/settings.local.json) poses no user risk but highlights hygieneccusage) for reset timer is separate; most users won’t need itC# GUI application development today is defined by a mix of legacy MVVM patterns, modular architectures, and modern, feature-centric folder structures across frameworks like WPF, WinUI 3, .NET MAUI, and Avalonia UI. While classic layer-based MVVM is still widely used for its familiarity, contemporary projects increasingly favor feature folders, vertical slice architecture, or clean architecture for improved scalability, testability, and developer onboarding. Multi-project splits (core logic + UI) are now recommended by Microsoft and embraced in flagship apps like Files, while community favorites like Avalonia are pioneering cross-platform design patterns. Generally, feature-focused organization and clean separation of concerns are seen as best practices, and pragmatic teams start simple, evolving their structure as the app grows.
Key Findings:
This README uses cogapp to automatically generate project descriptions.
A GitHub Action automatically runs cog -r -P README.md on every push to main and commits any changes to the README or new _summary.md files.
To update locally:
# Run cogapp to regenerate the project list
cog -r -P README.md
The script automatically:
_summary.md file existsllm -m {MODEL} with a prompt that creates engaging descriptions with bullets and links_summary.md to avoid regenerating them on every runTo regenerate a specific project’s description, delete its _summary.md file and run cog -r -P README.md again.