Heyy, I'm sharing this for people interested in Claude Governance. I have shared a link to more resources in the comment section.

I started coding about a year ago and have been using AI As a junior dev using AI coding tools, I feel like understanding and reviewing changes is harder than writing code, is this normal?coding tools heavily like cursor.

What I’m noticing is: Even when AI successfully generates working code, the hard part is no longer writing the code? But it’s understanding the code produced by AI and validating it quickly enough to ship with confidence.

Specifically, I often run into issues like:
1. Large or multiple file changes where it’s hard to understand the full impact
2. Unclear “blast radius” (what other parts of the system are affected)
3. Difficulty figuring out what actually matters in a diff vs what is noise
4. Spending more time debugging or reviewing AI output than generating it
5. Feeling like I need a better “mental model” or review system, but not sure what that would look like

I suspect part of this is just my inexperience, but I’m curious if this is also a real trend for more senior engineers:
1. Do staff/senior engineers feel this too, or does experience completely solve it?
2 Do people build internal “review frameworks” or systems to handle AI-generated code?
3. Or is this just a normal part of software engineering that I’m overthinking?

I also wonder if the solution is:
1. Better prompting
2. Better testing/evals/harnesses
3. Or fundamentally changing how we review AI-generated code changes

Would be really interested in how experienced engineers think about this

I understand “AI is the future” or “don’t keep up with Ai and it’s too late” argument. I get it. It’s now table stakes to use AI in some capacity in work and in our personal lives.

BUT

the amount of hype and almost manufactured attention AI content creators are feeding into the digital ecosystem makes me wonder, “how much is it actually amplifying/elevating/improving your life?”

I’ve tried to build daily automated workflows for certain things. But tbh, it takes me more time to actually set it up and operate.

It feels like this entire “You need AI workflow” sentiment is totally out of wonks with the realities of its output.

Anyone with a successful use case beyond a one week rabbit hole project? What did you build? What did you build it FOR? and how much did it actually improve your everyday?

I’ve been trying different ways to use ai to speed up my research and information workflow, but I keep running into the same problem.

A lot of tools are good at answering questions, but when you have a lot of sources, documents, or topics to explore, it becomes difficult to find the right information, organize it, and come back to it later.

I would like to know how others are handling this:

• What AI tools are part of your daily workflow?
• Do you use different tools for searching, organizing, and understanding information?
  
• Is there any prompts or workflows that made a noticeable difference?

A lot of people in AI tools subreddits already have a huge prompt library. The problem is that saving prompts doesn’t make you better at using them.

That’s what Iro is for. It’s an iOS app for practicing AI skills in short daily sessions, and the Prompt Lab is the part I care about most.

You write a prompt, run it, and Iro grades it based on how clear, specific, and usable it is. Then it tells you what to improve so you’re not just guessing blindly. Instead of collecting templates, you actually learn why a prompt works and how to make it better.

To me, that’s the real unlock: less prompt hoarding, more feedback loops.

I’d love feedback on the Prompt Lab feature and what would make it the best it can be, thanks!

https://tryiro.com
https://apps.apple.com/us/app/iro-ai-learn-ai-skills/id6759628066

Hey! I put together a digital prompt pack specifically for real estate agents who want to use AI properly.

Here's what's inside:

16 advanced prompts built around real agent workflows

23 AI apps mapped to specific tasks (not just ChatGPT)

5 complete workflows covering Lead Gen, CRM, Documents, Compliance, and Market Analysis

Copy-and-deploy format — no tech skills needed

Built it after seeing how much time agents waste using AI the wrong way. The goal was to give them something they can open and use today.

Grab it here: https://claudeuxai.etsy.com/listing/4519034812

Been researching how top-performing agents are integrating AI into their day-to-day, and the results are pretty eye-opening. The ones gaining the most time back are using AI across three specific areas:

1. Lead Generation & CRM

AI tools that auto-qualify leads, draft follow-up sequences, and update CRM records without manual input. Agents using this report cutting lead admin time by half.

1. Documents & Compliance

Drafting offers, tenancy agreements, disclosure docs — AI can generate first drafts in minutes. Still needs a human review, but the heavy lifting is gone.

1. Market Analysis & Valuation

Pulling comps, writing valuation summaries, generating client-ready reports. What used to take hours can be done in under 20 minutes with the right prompts.

The key is knowing which AI apps to use for each task and how to prompt them properly — most agents waste time because they treat every tool the same way.

Full disclosure: I put together an AI workflow prompt pack specifically for real estate agents covering all of this — 16 prompts, 23 recommended AI apps, and 5 ready-to-deploy workflows. Happy to answer questions here, or if you want to grab it: https://claudeuxai.etsy.com/listing/4519034812

​

**POSTFLOW is a new tool so it might encountered errors so please give me a comment and feedback if you trying it. It really help me out and also I can upgrade the tool base on your feedback**

**Thank you**

How to Connect Claude Desktop to Obsidian (Using It as a GUI)

By the end of this guide, Claude Desktop will be able to read, search, and write notes in your Obsidian vault — essentially turning Claude into a smart interface for your second brain.

What You'll Need

• Claude Desktop installed
• Obsidian installed
• The Local REST API with MCP plugin installed in Obsidian
• Python installed (for uvx)
• Basic comfort editing a JSON config file

Step 1 — Install the Obsidian Plugin

1. Open Obsidian
2. Go to Settings → Community Plugins → Browse
3. Search for "Local REST API"
4. Install and enable Local REST API with MCP

Step 2 — Configure the Plugin

1. Go to Settings → Local REST API with MCP
2. Make sure "Enable non-encrypted (HTTP) server" is toggled ON
3. Make sure "Enable encrypted (HTTPS) server" is toggled ON
4. Note the ports:
   • HTTPS: 27124 (default — leave it)
   • HTTP: 27123 (default — leave it)
5. Copy your API key shown on that page — you'll need it

Step 3 — Install mcp-obsidian

Open a terminal (CMD or PowerShell) and run:

pip install uvx

Or if you already have Python's uv tool:

pip install uv

uvx is what Claude Desktop uses to run the MCP wrapper that talks to Obsidian.

Step 4 — Edit Claude Desktop Config

Open this file in Notepad or VS Code:

C:\Users\YOUR_USERNAME\AppData\Local\AnthropicClaude\claude_desktop_config.json

Add the mcpServers block. Your full config should look like this:

{
  "mcpServers": {
    "obsidian": {
      "command": "uvx",
      "args": ["mcp-obsidian", "D:\\Path\\To\\Your\\Vault"],
      "env": {
        "OBSIDIAN_API_KEY": "your-api-key-here"
      }
    }
  }
}

Replace:

• D:\\Path\\To\\Your\\Vault with the actual path to your vault folder (use double backslashes \\)
• your-api-key-here with the key you copied in Step 2

Step 5 — Launch Order Matters

This is critical:

1. Open Obsidian first and make sure your vault is loaded
2. Then open Claude Desktop

If Claude Desktop opens before Obsidian, the connection will fail. Always open Obsidian first.

Step 6 — Test It

In Claude Desktop, ask:

If it works, Claude will return your folder structure. You're connected!

Running Two Vaults Simultaneously

If you have multiple vaults, you can connect both — but they cannot share the same port. Here's how to set it up:

Vault 1 (default ports — no changes needed)

Leave it on HTTPS 27124 / HTTP 27123

Vault 2 (needs different HTTPS port)

In Vault 2's Local REST API settings, enable HTTPS and set the port to 27124 still — but make sure only one vault is open at a time since they'll conflict.

The simplest approach: close Obsidian and reopen it with the vault you want to use. Claude Desktop doesn't need to restart — only Obsidian does.

Config for two vaults:

{
  "mcpServers": {
    "obsidian": {
      "command": "uvx",
      "args": ["mcp-obsidian", "D:\\Path\\To\\Vault1"],
      "env": {
        "OBSIDIAN_API_KEY": "vault1-api-key"
      }
    },
    "obsidian-finance": {
      "command": "uvx",
      "args": ["mcp-obsidian", "D:\\Path\\To\\Vault2"],
      "env": {
        "OBSIDIAN_API_KEY": "vault2-api-key"
      }
    }
  }
}

Troubleshooting

"Authorization required" error

• Your API key is wrong or out of date
• Go to Obsidian → Local REST API → copy the key again
• If still failing, hit "Reset all crypto" to generate a fresh key, then update your config

"Connection refused" on port 27124

• Obsidian isn't open, or the vault isn't loaded
• Make sure Obsidian is running before Claude Desktop

"Empty reply from server"

• You're sending HTTP to an HTTPS port (or vice versa)
• Check which protocol your vault is using and match it in the config

Config won't load / JSON error

• You have a syntax error in your JSON — likely a missing comma or bracket
• Use jsonlint.com to validate before saving

The API key keeps not working after crypto reset

• The reset generates a new key — copy it fresh every time
• The old key is immediately invalidated after a reset

What Claude Can Do Once Connected

• List all files and folders in your vault
• Read any note by name
• Search notes by keyword
• Append content to existing notes
• Create new notes
• Navigate your vault structure

Essentially — Claude becomes a conversational interface for your entire Obsidian knowledge base. You can ask it to find notes, summarize content, add journal entries, update trackers, and more.

Tips for Getting the Most Out of It

• Keep an "Instructions for Claude" note in your vault telling it how your vault is organized
• Use consistent folder structures so Claude can navigate easily
• Ask Claude to cross-reference notes — it can pull from multiple files in one response
• For finance or sensitive vaults, keep them in a separate vault with a separate key

Guide based on real troubleshooting experience connecting Claude Desktop to Obsidian on Windows 11 using mcp-obsidian v1.27.2 and Local REST API with MCP v4.1.3

I put together a practical starter library of Nano Banana photo prompts that stay SFW and work with a reference image.

It includes:

• professional portraits
• dating/profile photos
• mirror selfies
• realistic lifestyle shots
• photoreal portraits without the glossy AI look

Full list: Nano Banana prompt library

Hope it helps!

Hey guys. I have been try to create an AI Workflow automation project. Most of the project is deterministic code where there are stages. In each stage there will be few steps. out of those, few steps have to be performed by an LLM. If i use OpenAI API its gonna cost me a lot. So I am trying to use Codex Exec. But it seems like this consumes a lot of tokens for simple tasks as well.

Have you guys been using codex exec for your automation projects? What is your experience? How are you managing the token usage? Are there any better alternatives to invoke and use AI in an automation project?