与「ReFa」相关的搜索结果

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

Have been working closely with @dinkin_flickaa to completely refactor how images and videos are handled on 𝕏. Media now opens and closes fluidly, regardless of whether it’s a video, image, profile picture, etc. Makes a big difference to overall feel.

有第三方测试说，回归的Fable 5跟六月发布时不是一个水平了。 BridgeMind用BridgeBench重测7月1日版本：【Debugging】86.2→25.9，【Refactoring】73.6→38.4，【Hallucination】75.9→61.7。 据说是新护栏太频繁，很多任务转给Opus 4.8代打了。这掉分幅度，你们怎么看？

just sent my first prompt to Fable 5 > it instantly routed the task to Opus 4.8 > which spawned Sonnet 5 sub agents > that burned 30% of my weekly limit > and handed me slop this thing used to build full open words and refactor entire codebases in one shot WHAT DID YOU DO ANTHROPIC

Been iterating on @tomosman's loop. This one's winning: /goal produce a verified, code-derived behavioral spec for this web platform, captured in one canonical spreadsheet that carries every feature from spec -> tested -> fixed -> verified. Why: we need a single source of truth that maps every feature to its expected behavior *as the code implements it*, so that gaps and bugs surface and the platform can be driven to a known-good state. The spreadsheet is the source of truth. Work on the current repo. Do Phase 0 and Phase 1 under this goal; when the spec is complete, switch into the /loop below to drive testing and remediation. Keep moving through phases without stopping, except at a real checkpoint (defined below). Phase 0 - Plan (first): Detect the stack, the feature surface (routes, pages, components, API endpoints, background jobs, auth, settings…), and the test infra that already exists (unit/integration/e2e, browser automation, seeds/fixtures, a runnable dev server). Propose (a) how you'll inventory features, (b) the spreadsheet schema, and (c) how you'll test in the loop given what's available. Proceed once the plan holds. Phase 1 - Catalog & spec: Read the code and, for every feature, write a user story + the expected behavior as implemented, citing the file/function. Where the code is ambiguous, or behavior is undefined, log an open question - don't guess. Record every feature as a row in the canonical spreadsheet (create with the xlsx skill). Exit: every discoverable feature has a row. One row, concretely: | Area | User story | Expected behavior (from code) | Status | Defects | Type | Notes / source | |---|---|---|---|---|---|---| | Auth | As a returning user I want to log in with email+password so I can reach my dashboard | `POST /api/login` validates via bcrypt, sets httpOnly session cookie, 302 -> `/dashboard`; bad creds -> 401 + inline error | Spec'd | - | - | `api/auth/login.ts`, `LoginForm.tsx` | Canonical artifact: exactly one .xlsx, updated in place across every phase and loop iteration - never fork into per-phase or per-iteration files. Status flows Spec'd -> Tested-Pass / Tested-Fail -> Fixed -> Verified. The main thread is the single writer. Agentic execution: - Delegate breadth to subagents: fan feature discovery and per-area testing across subagents so the main thread stays focused. - Verify by running, not claiming - report real command/test output; state skips and unknowns plainly. - Checkpoint (pause, ask, end the turn) only for a destructive/irreversible action, a fix needing a genuine product decision, or input only I can give. Otherwise, keep going. - Self-check at each phase/loop boundary via a fresh-context subagent: re-verify the spreadsheet against the code (Phase 1) and against actual results (each loop pass). /loop Quality cycle - once the spec is complete, iterate test -> fix -> re-test until clean. Each iteration, in order: 1. Test: exercise every user story not yet Verified against the running app, preferring the strongest method available (browser/e2e automation > existing suites > documented static check only where execution truly isn't possible). Record actual pass/fail in the same spreadsheet; log every defect with its type (functional/logistical or UX). No app-behavior changes in this step. 2. Fix: think hard about root cause, then fix every functional/logistical and UX defect logged this iteration - cause, not symptom. Scope: only logged defects; no new features, no unrelated refactors. Update each row's status. 3. Re-test: re-run every story touched by a fix using the same method; set Verified, or back to Tested-Fail with notes if the fix didn't hold. Exit when all user stories are Verified and no open functional/UX defects remain. Safety cap: if a story is still failing after 3 full iterations, stop, leave it Tested-Fail with root-cause notes, and report it rather than looping further.

＼ReFa BEAUTY SHOWCASE／ -My Favorite Edition- 毎日の美容習慣を豊かに彩るReFaアイテム あなたのReFaにまつわるエピソードを教えてください。 WEEK3 2026.6.22 - 6.28 【テーマ】自分への‘‘美容投資’’として続けてみたいのはどれ？ 🎁お題に沿ったコメントも併せて記載で当選確率UP！💖 ①本アカウントをフォロー ②該当アイテム番号とキーワード 「わたしのリファ」をつけて引用リポスト 【応募締切】6.28 23:59 毎週参加で当選確率ダブルUP⭐ 是非皆様のエピソードとともにご応募お待ちしております。 ▼詳細はこちら

现在用 Obsidian、Logseq 这类 Markdown 笔记工具的人不少，写文章、记代码片段、整理读书笔记都靠它们。 但这套工作流跟 AI 编程工具其实是脱节的，想让 Claude Code 看一下你某个主题的笔记，得手动复制粘贴；想让它把整理过的内容写回笔记库，更没门。 一堆 Markdown 文件躺在硬盘上，AI 工具就在隔壁，两边愣是不通气。 refactoringhq/tolaria 这个项目就是冲着解决这件事来的。 Tauri + React + TypeScript 写的桌面笔记应用，Mac/Windows/Linux 三端全有，最近 star 数一路涨得很猛。 一句话概括：它给笔记和 AI 编程工具之间打了一条直通车。

＼ReFa BEAUTY SHOWCASE／ -My Favorite Edition- 毎日の美容習慣を豊かに彩るReFaアイテム あなたのReFaにまつわるエピソードを教えてください。 WEEK2 2026.6.15 - 6.21 【テーマ】疲れた日に‘‘自分をリセット’’したいときに選ぶのは？ 🎁お題に沿ったコメントも併せて記載で当選確率UP！💖 ①本アカウントをフォロー ②該当アイテム番号とキーワード 「わたしのリファ」をつけて引用リポスト 【応募締切】6.21 23:59 毎週参加で当選確率ダブルUP⭐ 是非皆様のエピソードとともにご応募お待ちしております。 ▼詳細はこちら

＼ReFa BEAUTY SHOWCASE／ -My Favorite Edition- 毎日の美容習慣を豊かに彩るReFaアイテム あなたのReFaにまつわるエピソードを教えてください。 WEEK1 2026.6.8 - 6.14 【テーマ】朝の準備でいちばん頼りになるのは？ 🎁お題に沿ったコメントも併せて記載で当選確率UP！💖 ①本アカウントをフォロー ②該当アイテム番号とキーワード「わたしのリファ」をつけて引用RP 【応募締切】6.14 23:59 毎週参加で当選確率ダブルUP⭐ 是非皆様のエピソードとともにご応募お待ちしております。