u/Alternative_One_4804

It’s 40°C where we are right now, but the heat isn't what worries me most: it’s the invisible UV exposure.

With three young kids, guessing whether the UV index is at a safe 2 or a dangerous 9 isn't an option, and bad sunburns early in life double the risk of skin damage later on.

I tried using standard weather apps, but they hide the UV index under layers of forecasts, menus, and ads. I needed to see peak UV risk instantly without digging around.

So I built a simple, no-frills tool. You open it and immediately get two things:

1. The exact, real-time UV risk level.
2. A straightforward reapplication countdown based on that UV strength.

No clutter, no bloat, no sign-ups. Just the UV facts you need when you're outside with your family.

Sharing it here in case it helps keep your kids safe this summer too. Protect their skin, check the UV index, and don't forget the hats! ☀️🧴👶

https://uvindex.pixari.dev

It’s 40°C where we are right now, but the heat isn't what worries me most: it’s the invisible UV exposure.

With three young kids, guessing whether the UV index is at a safe 2 or a dangerous 9 isn't an option, and bad sunburns early in life double the risk of skin damage later on.

I tried using standard weather apps, but they hide the UV index under layers of forecasts, menus, and ads. I needed to see peak UV risk instantly without digging around.

So I built a simple, no-frills tool. You open it and immediately get two things:

1. The exact, real-time UV risk level.
2. A straightforward reapplication countdown based on that UV strength.

No clutter, no bloat, no sign-ups. Just the UV facts you need when you're outside with your family.

Sharing it here in case it helps keep your kids safe this summer too. Protect their skin, check the UV index, and don't forget the hats! ☀️🧴👶

https://uvindex.pixari.dev

It’s 40°C where we are right now, but the heat isn't what worries me most: it’s the invisible UV exposure.

With three young kids, guessing whether the UV index is at a safe 2 or a dangerous 9 isn't an option, and bad sunburns early in life double the risk of skin damage later on.

I tried using standard weather apps, but they hide the UV index under layers of forecasts, menus, and ads. I needed to see peak UV risk instantly without digging around.

So I built a simple, no-frills tool. You open it and immediately get two things:

1. The exact, real-time UV risk level.
2. A straightforward reapplication countdown based on that UV strength.

No clutter, no bloat, no sign-ups. Just the UV facts you need when you're outside with your family.

Sharing it here in case it helps keep your kids safe this summer too. Protect their skin, check the UV index, and don't forget the hats! ☀️🧴👶

https://uvindex.pixari.dev

Skill e plugin per Claude Code (e, con ZIP, Claude Cowork/Desktop) orientati alla pratica giuridica in Italia: metodo, citazioni, civile, lavoro, privacy/GDPR. Contenuti originali in italiano; architettura ispirata a claude-for-legal e claude-fuer-deutsches-recht.

Spent the last few months wiring Claude Code into the rest of my dev workflow, not just the editor. So it picks up tickets, writes code, runs a review pass, and puts up an MR for me to look at. Plus a persistent knowledge layer so it doesn't start every session from zero.

If I had to pick one thing I got right: the agent is not what runs the workflow. Plain Python handles the mechanical stuff (API calls, git, tests). The agent only gets invoked when something actually requires judgment.

I started by letting the agent do everything. It read the configs, made API calls through tool use, managed git, kept track of its own state. Slow, expensive, and it would lose its place every so often. Once I split the mechanical work out into plain Python, the workflow phases got about 10x faster and failures actually became debuggable.

The flow for a single ticket now goes like this:

1. Orchestrator (Python): fetch the ticket, search a local knowledge wiki for related decisions, set up a worktree, assemble a context brief for the agent.

2. Claude Code: takes the brief, writes the code.

3. Validation (Python + a separate review agent): tests, lint, code review pass. If anything fails, hand it back to the agent, retry up to three times.

4. Ship (Python): write a proposal into a dashboard, wait for me to approve it, then push and open the MR.

The agent only runs in step 2 and the retry loop in step 3. Everything else is deterministic.

A few governance choices that ended up mattering more than I expected:

- The system never executes irreversible actions (merge, close ticket, send a message) without an explicit human approval. It creates a proposal that I have to click on.

- A separate review agent, configured with no edit or write permissions, runs the code review pass. Splitting review and implementation into two isolated contexts caught a class of issues the implementation agent kept missing on its own.

- The wiki tags facts as verified, inferred, or human-provided. Without that tagging, agents end up treating their own past hallucinations as truth.

Things I'm still wrestling with:

- Anything spanning multiple repos. The agent loses coherence across services.

- Tickets that are too vague. Output looks fine, but is often wrong.

- Over-engineering. It adds error handling and abstractions for hypothetical needs.

- Long-running sessions. Earlier context falls out of effective attention.

Would love feedback, especially from people who have built something in this space. What did you keep, what did you throw out, and where do my decisions look wrong to you?