与「MUST」相关的搜索结果

开发系统最极致高效的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.

$RTX is more than a ticker. It’s a vision. It’s a world waiting to be built. It’s a brand waiting to be recognized. Today, $RTX officially launches the RTX Creative Mission, inviting creators around the world to shape the future of the RTX universe. Whether it’s memes, artwork, videos, animations, or storytelling—your creativity could become part of the $RTX identity. 🏆 US$10,000 worth of NVDAB rewards Create. Inspire. Define $RTX. 📖 Rules + Entry ↓ ⸻ 🧵 Thread 1 What should the future of $RTX look like? That’s for the community to decide. Create anything inspired by $RTX, including: • Memes • Posters & Visual Design • GIFs & Animation • Videos • Stories & World-building • 3D Art • Multilingual Content • Any original creative format Let’s build an identity that people recognize instantly. ⸻ 🧵 Thread 2 Your creation could become part of the $RTX brand. To enter, include: ✅ $RTX ✅ @fourdotmemezh ✅ @rtxonbnbchain ✅ #DefineThebSTOCKEra# AI-assisted work is welcome, but every submission must reflect meaningful human creativity and originality. Don’t just hold $RTX. Build $RTX. 🚀

Last night Apple briefly removed Telegram from the AppStore because a user had planted illegal porn in a public chat. Telegram was restored within hours. But I want to explain what happened — to warn other app developers and help protect online communities from similar attacks. Because Telegram quickly removes illegal content from public groups using all kinds of moderation tools, the attacker had to resort to a technical trick. He inserted AI-modified illegal content by editing an old message in an active group chat. As a result the content was effectively hidden from the group’s members, preventing them from seeing/reporting it. The attacker was a takedown extortionist: someone who demands ransom from group owners in exchange for not targeting their communities. These extortionists use automated accounts to plant illegal content in public groups and then report it directly to Apple, attempting to trigger the removal of legitimate communities whose owners refused to pay them. From a practical standpoint, illegal pornographic content in Telegram’s public groups is not a systemic problem. Our moderation is effective. The fact that attackers must resort to backdated, effectively invisible content and other technical tricks proves this. ⚠️ However, there are two important lessons here for app developers and online communities: — Extortionists have found a way to manipulate Apple into overreacting. Apple removed Telegram from the App Store before contacting us. This creates a potential systemic risk for every mobile app that hosts user-generated content. If an app used by more than a billion people can be removed from the App Store without prior warning, any app can be. — The tactics used by takedown extortionists are evolving, putting communities across social platforms at risk. Telegram has extensive experience identifying the tricks used by coordinated reporting gangs and protecting legitimate communities (even when doing so risks our own app being temporarily removed from the App Store). Other platforms may not be equally prepared. Stay vigilant! ☝️

Currently, @fourdotmemezh holds three RWA tokens, but only #RTX# fully supports the community. 0x2ec39b165e22944d2fee389219ee64e4924cffff Buying the other two is just a conspiracy. We must support the community. Today, @Fourdotmemezh opened a space to listen to our suggestions. If they want to regain their leading position, they can only do so by supporting the community's #RTX#. So let's unite!

BREAKING: Billionaire Whitey Basson says Elon Musk’s Starlink must launch in South Africa. 🇿🇦 He said that keeping @Starlink out of South Africa is discouraging businesspeople from investing in rural areas where there is no working communications infrastructure.

i built a way to generate full ai vlogs for youtube using seedance 2.5, without ever picking up a camera this was supposed to stay internal but f*ck it, i'm leaking the whole thing you give it a script or even just a topic and it comes back with a finished vlog, voiceover, b-roll, captions, ready to upload here's how it works: a custom claude skill breaks your script into scenes and writes timestamped storyboard prompts for each one, matched to pacing so nothing feels random. those prompts get fed into seedance 2.5, using its 30 second continuous generation and reference asset support to keep the visuals consistent across scenes instead of looking like ten unrelated clips stitched together. then it pulls in an ai voiceover that matches the tone of the script, stitches every scene together, and burns in captions automatically you're not filming, not voicing, not editing, not exporting from three different apps the whole thing runs start to finish and outputs a finished 16:9 vlog ready to post, and it costs a fraction of what an editor or camera setup would run you i'm sharing the full breakdown, which includes: the claude skill that handles scene breakdown and storyboard prompts the seedance 2.5 setup that keeps visuals consistent scene to scene the voiceover setup that keeps it from sounding robotic the exact workflow from script to finished vlog RT + reply "PROMPTS" and i'll send it over (must follow so i can dm)