suchuanyi

5 ms·

1.
by suchuanyi 8mo ago
If you're using BMAD (Breakthrough Method for Agentic AI Development), you know the pain: every story requires running through create → develop → test → review → fix → update status. For an Epic with 8 stories, that's potentially
2.
by suchuanyi 1y ago
I built a virtual pet that lives in your Claude Code status line and reflects your AI usage patterns. The pet's energy decays over time (~3 days from full to death), and you feed it by consuming tokens through Claude Code. As e
3.
by suchuanyi 1y ago
I built ccshell to solve the constant problem of forgetting shell command syntax. Instead of searching Stack Overflow for "how to batch rename files with timestamps" or "compress videos while maintaining quality", yo
4.
Build a Decentralized Blog with Planet and ENS(medium.com)
1 points by suchuanyi 1y ago|0 comments
5.
by suchuanyi 1y ago
If you’re on a Pro account, it’s common to hit the usage limit in the middle of a long-running task. Claude Code will tell you you’re out of quota, and the reset time might be something like 3 AM. If you’re asleep by then, you miss the chan
6.
Claude Code Pro Limit? Hack It While You Sleep(github.com)
141 points by suchuanyi 1y ago|88 comments
7.
by suchuanyi 1y ago
Fair concern — but I’d argue it’s not really ‘vibe-coding’ the tests. With Playwright MCP, the AI uses structural page data and ref_ids captured at runtime, which leads to highly stable and reproducible interactions. It’s not guessing — it’
8.
by suchuanyi 1y ago
I get where you’re coming from — a lot of LLM-based UI testing tools today do feel flaky or unpredictable. But Playwright MCP works quite differently from what you’re describing. It doesn’t rely on AI guessing or using fragile selectors. Wh
9.
Stop Writing Brittle Playwright Tests: Why YAML-Based Testing Is the Future(medium.com)
6 points by suchuanyi 1y ago|8 comments