← all publishers

yuchi-chang

@yuchi-chang source repo

Report this profile Claim this profile

• 15 skills
• 0 followers
• 8 hours ago last updated

1. ▌
   Desktop Pet · yuchi-chang bundle

   把任何角色或動物的圖片變成互動式桌面寵物（桌寵）。分析圖片、自動去背、產生個性化設定，並啟動一隻會在桌面走動的透明置頂寵物，支援餵食、撫摸、呼喚主人、Ctrl+點擊召喚、拖曳等互動。當使用者提供圖片並想做成桌寵時使用。Turn any character/animal image into an interactive desktop pet with auto background removal, feeding, petting, call-owner and Ctrl+click summon. Use when the user provides an image and wants a desktop pet (e.g. "make a desktop pet from this image", "把這張圖做成桌寵"), or wants to launch/manage existing pets.
   0
   installs
2. ▌
   Fail Loud · yuchi-chang

   Use when writing error handling — try/catch blocks, fallback values, default parameters, retries, or any code path that handles failure
   0
   installs
3. ▌
   Durable Plans · yuchi-chang

   Use when planned work will outlive the current session — persisting a plan to disk, resuming work from an on-disk plan, or landing changes a plan file describes
   0
   installs
4. ▌
   Safe Refactoring · yuchi-chang

   Use when restructuring, renaming, moving, or extracting code that already works — before making the first edit
   0
   installs
5. ▌
   Surgical Changes · yuchi-chang

   Use when editing existing code — bug fixes, small features, or any change inside a codebase you didn't just write
   0
   installs
6. ▌
   Receiving Feedback · yuchi-chang

   Use when receiving code review comments, reviewer suggestions, or technical corrections — before implementing any of them
   0
   installs
7. ▌
   Verify Before Done · yuchi-chang

   Use when about to claim work is complete, fixed, or passing — before committing, opening a PR, marking a task done, or relaying a subagent's success report
   0
   installs
8. ▌
   Writing Solid Plans · yuchi-chang

   Use when designing or planning a multi-step feature, refactor, or spec before implementation begins
   0
   installs
9. ▌
   Escalate Dont Thrash · yuchi-chang

   Use when repeated attempts at the same problem keep failing without producing new evidence — before trying another variation of the last fix
   0
   installs
10. ▌
    Exploring Approaches · yuchi-chang

    Use when starting a new project or significant feature from a vague idea — before clarifying details or planning, especially when the user already has a preferred approach
    0
    installs
11. ▌
    Root Cause Debugging · yuchi-chang

    Use when encountering a bug, test failure, regression, flaky test, or unexpected behavior — before proposing or applying any fix
    0
    installs
12. ▌
    Clarifying Requirements · yuchi-chang

    Use when starting a new feature, component, or project whose requirements are underspecified or ambiguous — before designing or writing code
    0
    installs
13. ▌
    Schema Migration Safety · yuchi-chang

    Use when writing database schema migrations or changing tables, columns, indexes, or constraints on a system with real data
    0
    installs
14. ▌
    Writing Meaningful Tests · yuchi-chang

    Use when writing or modifying tests, adding mocks, or tempted to add test-only methods to production code
    0
    installs
15. ▌
    Measure Before Optimizing · yuchi-chang

    Use when asked to improve performance, or when about to optimize code believed to be slow
    0
    installs