Ran the same prompt through Hailuo H3 and Seedance 2.0. A queen riding a butterfly dragon over a flower field.

H3 wins on looks. Sharper light, cleaner color, more detail holding up in motion. Did not expect that going in. https://x.com/socialwithaayan/status/2084973029357154461

i3-style tiling for Windows, with YAML config, multi-monitor support, and a one-click installer. Also integrates with Zebar if you want a status bar. https://x.com/GithubProjects/status/2085010454536225075

A fully on-device iOS IDE that compiles and runs native Swift, Objective-C, C, and C++ apps without a cloud connection or jailbreak, even in airplane mode.

Explore it here:
https://www.opensourceprojects.dev/post/emexde https://x.com/GithubProjects/status/2085055743548596691

ESTE TIPO MONETIZÓ SU CANAL DE YOUTUBE EN 9 DÍAS SIN MOSTRAR LA CARA Y LO EXPLICA EN 17 MINUTOS

La barrera de entrada a YouTube siempre fue la misma: equipo, cara, experiencia, meses esperando que el algoritmo te vea.

→ Canal 100% con IA, sin aparecer en cámara
→ Monetizado en 9 días desde cero
→ Sin experiencia previa necesaria
→ El método completo en 17 minutos de video

🔖 guárdalo, no te arrepentirás.

开发系统最极致高效的Agents.md，没有之一：

# AGENTS.md

## Core Principles

- Choose the simplest implementation that fully satisfies the current requirements. Avoid unnecessary abstraction, configuration, indirection, or speculative extensibility.

- Make the smallest necessary change that fixes the root cause. Do not refactor unrelated modules or change strategy semantics unless explicitly requested.

- Grow the system in layers. Start from the smallest working end-to-end version and add new capabilities incrementally. Never replace a working system with unfinished complexity.

- Reuse existing project components before creating new ones. Prefer extending proven modules over introducing parallel implementations.

- Prefer well-maintained libraries when they reduce overall complexity or improve reliability. Do not reimplement common functionality without a clear benefit.

- Keep components modular with clearly defined responsibilities. Avoid unnecessary coupling between strategy logic, execution, accounting, replay, and infrastructure.

- Design for long-term maintainability once a feature or strategy has been validated. Do not over-engineer speculative ideas before evidence exists.

---

## Strategy Development

- Validate hypotheses with historical replay before introducing forward-only logic whenever historical validation is possible.

- Every trading strategy must progress through Replay → Shadow → Canary → Live. Do not skip validation stages.

- Base design decisions on measurable evidence rather than intuition. Optimize only after demonstrating that an edge exists.

- Treat every strategy as an independent contract. Do not silently alter frozen behavior without explicit authorization.

---

## Existing Systems

- Do not break running Shadow or Live systems for unrelated work.

- Preserve compatibility only when required by active production or validation workflows. Otherwise, remove obsolete code instead of accumulating compatibility layers.

- Reuse existing infrastructure whenever possible, including replay engines, accounting, execution, wallet management, order book handling, logging, monitoring, and daemon frameworks.

---

## Engineering Standards

- Prefer deterministic behavior over hidden automation.

- Fail loudly when assumptions are violated. Do not silently ignore errors or fall back to unexpected behavior.

- Keep configuration minimal. Introduce new configuration only when behavior genuinely needs to vary.

- Remove dead code instead of leaving unused paths behind.

- Write code that is easy to inspect, replay, test, and reason about.

- Keep implementation consistent with existing project architecture unless an architectural change is explicitly requested.

---

## Scope Discipline

- Implement only the requested scope.

- Do not introduce unrelated optimizations, redesigns, migrations, or feature expansions.

- Non-blocking findings outside the requested scope may be noted separately but must not be merged into the current task.

- Consider a task complete once its agreed acceptance criteria are satisfied. Treat subsequent improvements as separate work items.

Daddy's home. https://x.com/nikitabier/status/2085199604597858471