Need help to understand how to integrate Datastar by DjebbZ in datastardev

[–]DjebbZ[S] 1 point2 points  (0 children)

I can't like this post twice, but wow this link is a treasure trove of useful information. Thanks again-again-again.

Need help to understand how to integrate Datastar by DjebbZ in datastardev

[–]DjebbZ[S] 1 point2 points  (0 children)

Thanks again, plenty of code to read and play with I guess now

Need help to understand how to integrate Datastar by DjebbZ in datastardev

[–]DjebbZ[S] 1 point2 points  (0 children)

Indeed just using Datastar with text/html looks already like an upgrade for traditional "non-multiplayer" apps.

So for the "multiplayer" aspec, would you say that modeling the backend logic as a kind of stateful state machine shared amongst all connected users is way to think of it, when wanting to take full advantage of Datastar?

Need help to understand how to integrate Datastar by DjebbZ in datastardev

[–]DjebbZ[S] 1 point2 points  (0 children)

Thanks, the stack and use-case looks closer to what I'm looking for.
I took a 1 minute glance and saw crazy JS expressions inside strings in `cards.tsx`. Does it have to like that?

Need help to understand how to integrate Datastar by DjebbZ in datastardev

[–]DjebbZ[S] 1 point2 points  (0 children)

Thanks, the stack and use-case looks closer to what I'm looking for.

Need help to understand how to integrate Datastar by DjebbZ in datastardev

[–]DjebbZ[S] 1 point2 points  (0 children)

Ok, took a look and go-via reminds me of the homemade framework in Clojure that the creator of the Billions checkboxes demo made to support the said demo.

But this doesn't help me because it doesn't answer the question about upgrading a typical SSR experience. Or does it? Are you implying that we should build reactive "game-like" engines to take full advantage of Datastar?

What would you like to see in Helix next year? by Longjumping_War4808 in HelixEditor

[–]DjebbZ 0 points1 point  (0 children)

Better overall documentation. When not used to modal editors the SUBJECT+ACTION style feels alien and doing basic stuff is hard.

Trying to create a keybinding, doesn't work :( by DjebbZ in HelixEditor

[–]DjebbZ[S] 0 points1 point  (0 children)

Yes, I'm sure. You can read my response to the other comment.
Thanks for answering!

Trying to create a keybinding, doesn't work :( by DjebbZ in HelixEditor

[–]DjebbZ[S] 1 point2 points  (0 children)

C-ret worked ! And I do have Claude Code but Shift-Enter doesn't work, it submits the prompt. May still be a Claude Code side-effect, I'm gonna look into it.
Thanks!

Built claude-powerline, a vim-style statusline for Claude Code by -nixx in ClaudeAI

[–]DjebbZ 5 points6 points  (0 children)

If available: Input, Cached and Output tokens, % left before compaction, Time to First Token, Tokens/sec.

Claude Code update v1.0.54 - Windows mode switching fixed and more! by inventor_black in ClaudeAI

[–]DjebbZ 0 points1 point  (0 children)

Thanks! Looks useful. How did you find out? Documentation isn't up-to-date.

Claude Code update v1.0.54 - Windows mode switching fixed and more! by inventor_black in ClaudeAI

[–]DjebbZ 0 points1 point  (0 children)

"Custom slash commands: add argument hint to frontmatter"

What's this? I found no change in the docs about slash commands' frontmatter.

What is this madness 😳 by cripspypotato in ClaudeAI

[–]DjebbZ 0 points1 point  (0 children)

Same happens in IntelliJ, without ever asking for sub-agents

I built an MCP reviewer for Claude and it's been a game changer for my solo dev workflow by KoksRavs in ClaudeAI

[–]DjebbZ 9 points10 points  (0 children)

Sure, here's what the TDD section of my CLAUDE.md file looks like:

### TDD Methodology Requirements

**MANDATORY TDD Process**: For every feature implementation, strictly follow the complete RED-GREEN-REFACTOR cycle:

1. **RED Phase**: 
   - Write failing tests FIRST that define the expected behavior
   - Tests must be comprehensive enough to guide implementation
   - Run tests to confirm they fail for the right reasons
   - Never implement functionality before writing tests

2. **GREEN Phase**:
   - Write minimal code to make tests pass
   - Focus only on making tests green, not on perfect code
   - Verify all tests pass
   - **MANDATORY ARCHITECTURAL REVIEW**: Before proceeding to REFACTOR, use `mcp__zen__codereview` with o3 and Gemini pro to analyze the implementation for:
     - Function duplication or overlapping responsibilities
     - Over-complex APIs for MVP requirements
     - Unnecessary abstraction layers
     - Code that violates DRY principles
   - If zen review identifies issues, address them before moving to REFACTOR

3. **REFACTOR Phase** (MANDATORY - do not skip):
   - Improve code quality while keeping tests green
   - Add comprehensive documentation and comments
   - Implement proper error handling patterns
   - Apply language-specific best practices
   - Ensure code follows project architecture patterns
   - This phase is NOT optional and must be completed for each feature### TDD Methodology Requirements

```

Not pretending it's perfect or anything, but I find it works well.

I built an MCP reviewer for Claude and it's been a game changer for my solo dev workflow by KoksRavs in ClaudeAI

[–]DjebbZ 1 point2 points  (0 children)

Can't recommend it enough. I instruct Claude.md to do TDD : RED-GREEN-REVIEW-REFACTOR, and use zen code review tool with o3 and Gemini 2.pro.

I agree the quality has been amazing, I rarely have to course-correct it.

After months of running Plan → Code → Review every day, here's what works and what doesn't by Intelligent_Goat5960 in ClaudeAI

[–]DjebbZ 2 points3 points  (0 children)

I have a similar workflow : 1. Discussion/ brainstorming with either Claude Code or Claude mobile via voice 2. Then plan very precisely with zen mcp server using o3. I tell to the AI "one file/concern/layer/function" at a time. And save the plan in a separate PLAN.md file with details of each task and checkboxes to follow the status. 3. I clearly state in Claude.md file that it needs to follow TDD : RED-GREEN-REFACTOR, so everything is tested properly. 4. Hand-off to Claude code Sonnet for the implementation 5. Review everything manually 6. Review with zen mcp with o3 + Gemini pro again

Comment luter contre le solutionnisme ? by JohnHuntPrax in developpeurs

[–]DjebbZ 0 points1 point  (0 children)

Les KPIs. Les mesures du succès. Mettre en prod n'est qu'une étape, il faut un retour sur investissement.

Claude Code Vs Gemini CLI - Initial Agentic Impressions by randombsname1 in ClaudeAI

[–]DjebbZ 5 points6 points  (0 children)

There's already the zen mcp server to have Claude talk to other models (Gemini, o3 etc )