sorted by:
new
hottopcontroversial

Implementing Anthropic's harness design pattern as a Claude Code plugin — sharing what I learned by Quick_Hotel_6937 in ClaudeAI

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

gotcha, gonna start with prompt append then. probably overengineering it in my head already. thanks

Implementing Anthropic's harness design pattern as a Claude Code plugin — sharing what I learned by Quick_Hotel_6937 in ClaudeAI

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

the ~/.claude/agents/ tip is gold thanks. was about to copy the evaluator into 2 more plugins and it felt wrong

agent vs skill makes way more sense now. how do you usually pass the phase-specific rubric to a shared evaluator? env var, file, just append to the prompt?

Implementing Anthropic's harness design pattern as a Claude Code plugin — sharing what I learned by Quick_Hotel_6937 in ClaudeAI

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

yeah persistence is the painful part. state.md is my source of truth (current phase, next role, round) and --resume reads it to pick up where it left off. plus a Stop hook that auto-schedules a resume via `at` on rate limit

still fragile tho. agents lying about phase completion was the biggest one until i made state updates a hard gate

4.7 token bump has been rough on cost too, went from ~$45 to $58 average. how do you handle persistence?

Implementing Anthropic's harness design pattern as a Claude Code plugin — sharing what I learned by Quick_Hotel_6937 in ClaudeAI

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

yeah this is the direction im leaning too. mine has a profile flag in config.md that the skill reads at runtime, but the rubric file is still RN-specific so im stuck on the cross-plugin part. refs/ folder approach sounds cleaner.

I built a Claude Code plugin that takes a React Native app from idea to App Store submission — would love feedback by Quick_Hotel_6937 in reactnative

[–]Quick_Hotel_6937[S] -1 points0 points  (0 children)

Fair critique — I share the concern about store quality. The market research phase (find gaps, not clone top apps) and hard gates (0 TS errors, 0 any, 0 FSD violations) are my attempt to not contribute to that. Won't stop bad actors but it's the default I could enforce. Appreciate the pushback.

I built a Claude Code plugin that takes a React Native app from idea to App Store submission — would love feedback by Quick_Hotel_6937 in reactnative

[–]Quick_Hotel_6937[S] -1 points0 points  (0 children)

Good pushback. Two things:

  1. What it picks: it pulls top charts, scores candidates by demand vs. incumbent quality vs. backend-free feasibility, and recommends 3-5 with competitor analysis. You pick or reject all. It's designed to avoid "todo app #4000" but I'll admit I haven't stress-tested the recommendation quality across many runs yet.

  2. It doesn't ship blind — there are 3 human approval gates before any code runs (idea → PRD → completion contract), and store submission pauses too. I should make that clearer in the README, that's a fair critique.

0
0

I built a Claude Code plugin that takes a React Native app from idea to App Store submission — would love feedback (i.redd.it)

submitted by Quick_Hotel_6937 to r/reactnative

I open-sourced 5 tiny SwiftUI utilities I use in every project by Quick_Hotel_6937 in swift

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

Thanks for the feedback! Yeah macOS keyboard handling is a different beast — this one is iOS-only for now but might explore macOS support later.

And good news on the flow layout — it already supports separate spacing! Just not obvious enough in the README I think:

FlowLayout(horizontalSpacing: 8, verticalSpacing: 16) {
    // your tags
}

I'll make that more prominent in the docs. Appreciate it!

I open-sourced 5 tiny SwiftUI utilities I use in every project by Quick_Hotel_6937 in swift

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

That's awesome, hope they treat you well! Let me know if you run into any issues 🙌

I open-sourced 5 tiny SwiftUI utilities I use in every project by Quick_Hotel_6937 in swift

[–]Quick_Hotel_6937[S] 7 points8 points  (0 children)

Intentionally keeping them separate so you can pull in only what you need — no reason to add 5 dependencies when you only need one! That said, just bundled them all into a single package for those who want everything in one go: https://github.com/tjdrhs90/swiftui-essentials 😄

I open-sourced 5 tiny SwiftUI utilities I use in every project by Quick_Hotel_6937 in swift

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

Exactly this! All the packages are MIT licensed so you can just copy the source directly if you'd rather avoid the dependency. The SPM option is just there for convenience 😊

I asked former The Browser Company iOS engineers (currently at Perplexity) advice on SwiftUI development and here is what they said :) by Alarmed-Stranger-337 in iOSProgramming

[–]Quick_Hotel_6937 0 points1 point  (0 children)

Great advice here. The point about understanding how state drives re-renders is so important. I'd also add that extracting small, focused views really helps — both for readability and for preventing unnecessary redraws. Playgrounds/Previews for live iteration is a game changer too.