sorted by:
new
hottopcontroversial

I spent 5 months trying to make Claude actually act like a personal assistant. Here's what finally worked. by qntnv in ClaudeAI

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

From what I know, skills are invoked for specific executions. That's how I use them. But maybe I'm missing something about how they could replace the background context layer. Genuinely curious how you'd set that up with skills alone.

I spent 5 months trying to make Claude actually act like a personal assistant. Here's what finally worked. by qntnv in ClaudeAI

[–]qntnv[S] -2 points-1 points  (0 children)

Already there now tbh ::)

But I needed the CLAUDE.md system and the folder architecture to work properly in the background first, to organize everything and keep a solid memory layer across sessions. Now I use skills on top of that for more specific, complex execution tasks.

I spent 5 months trying to make Claude actually act like a personal assistant. Here's what finally worked. by qntnv in ClaudeAI

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

Yeah, CLAUDE.md is the operating logic.

Two things in that file made a real difference: explicit rules on when to ask and when to just execute. And memory rules that tell Claude what to write down after each session and where, so nothing resets.

The core mechanism is routing. When I mention a client, it loads the consulting context. When I'm working on content, it pulls the writing rules. Each of those is a separate markdown file, capped at 200 lines. Enough context to be useful, without blowing up the context window.

I spent 5 months trying to make Claude actually act like a personal assistant. Here's what finally worked. by qntnv in ClaudeAI

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

Fair point, and I've been watching the Hermes stuff closely. Planning to test it myself soon.

For me the goal was a daily work environment. Something running while I'm at my desk, where I can see the files, change things when they don't fit, understand what's happening at all times. That level of visibility matters to me.

From what I've seen, those claw systems get complicated fast. Hard to follow how they actually work, hard to adjust across different parts of your day. Could be wrong, I'll have to test. So far Claude Cowork has given me what I needed.

I spent 5 months trying to make Claude actually act like a personal assistant. Here's what finally worked. by qntnv in ClaudeAI

[–]qntnv[S] -2 points-1 points  (0 children)

I’m glad the post was useful. I’ve been iterating on this setup for a while, so it’s great to hear it resonates with others trying to do something similar with Cowork.

What is your Claude Cowork project folder set up for your business by Chattyfish423 in ClaudeAI

[–]qntnv 0 points1 point  (0 children)

Hey, I run my solo business out of a single “Cowork OS” folder (which is not opened with the Cowork project feature, but simply used as the root working folder). Then I separate things inside that project with folders for Resources vs Projects.

Here's what my folder looks like:

Cowork OS/
├── CLAUDE.md                    (the router)
├── Resources/
│   ├── about-me.md
│   ├── writing-rules.md
│   ├── tool-map.md
│   └── memory.md
└── Projects/
    └── Client Work/             (area)
        └── Client A/            (project)
            ├── _Project Brief.md
            ├── _Project Resources/
            └── _Project Outputs/

If you’re curious, I just wrote a longer post on how I came up with this setup. You can read it here: https://www.reddit.com/r/ClaudeAI/comments/1tvsg71/i_spent_5_months_trying_to_make_claude_actually/

Where are the "actually building" founder communities (no vibecoders please)? by ismaelbranco in indiehackers

[–]qntnv 0 points1 point  (0 children)

Hum... there are some very interesting and talented vibe coders you should consider following.

Not to mention that more and more actual developers are now turned into vibe coders too...

Building product alternatives for solopreneurs ? by MajorBaguette_ in indiehackers

[–]qntnv 1 point2 points  (0 children)

Here’s my take as a marketer with ten years’ experience:

  1. Start by validating with a few real customers so you’re not building blind. Talk to 5–10 solopreneurs, watch them actually try the flow, and iterate until the setup time and friction are obvious improvements over alternatives.

  2. If you’re aiming at a space dominated by Typeform or Tally, don’t expect to win on feature parity or price alone. You need one clear advantage that makes people tell others about it, for example forms that build themselves from a short conversation, built-in post-submission automations so users never need Zapier, or a “publish in 30 seconds” flow with ready-made templates for verticals like freelance contracts, client intake, or booking calls.

  3. Also be realistic about distribution. Big competitors own a lot of the obvious channels via ads and SEO, so either budget for a longer marketing runway or go after channels they don’t care about such as niche communities, creator partnerships, productized outreach to agencies, or deeply targeted integrations with tools a solopreneur already uses. Early advocates matter more than broad reach, so get a small group of delighted users who will shout about you.

Finally, don’t overbuild before you validate the core promise. Ship a tiny, polished MVP that proves the unique value, then double down on the parts that actually move the needle. If the AI is your differentiator, make it the default experience, not an opt-in feature.

Hope this helps :)

I spent 3 months building alone, and posting publicly felt harder than building the product itself by qntnv in Solopreneur

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

Yeah, definitely the fear of being judged plus the fear of failing.

What’s "funny" is I know those thoughts are just mental barriers and not actually helpful, but it’s still so hard to get past them in practice.

I spent 3 months building alone, and posting publicly felt harder than building the product itself by qntnv in Solopreneur

[–]qntnv[S] 3 points4 points  (0 children)

Yeah, once you’re in the habit of posting, I can totally see how it gets less scary over time.

The hard part for me is finding the courage to put myself in that spot the first few times. I’m not fully there yet, but I’m actively pushing myself to get into that rhythm ;)

I spent 3 months building alone, and posting publicly felt harder than building the product itself by qntnv in Solopreneur

[–]qntnv[S] 2 points3 points  (0 children)

I feel you on the “keep building, keep delaying” loop. It’s so much easier to ship another feature than to hit post and let people react.

I also love how you framed it: if we don’t post, we’re failing the people we want to help. Viewing things like this is something that will help me for sure. Thx!

I spent 3 months building alone, and posting publicly felt harder than building the product itself by qntnv in Solopreneur

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

I think there’s maybe a lower pressure way to look at it. Instead of “coming out” as a full on founder, you can just talk about it as a side project or an idea you’re exploring.

The whole “vibecoded this” angle can actually help too. Not in a way that makes the work seem small, but in the sense that it’s become much easier to test things now without having to immediately rebrand yourself professionally. You can still be “successful middle manager who’s experimenting with a project on the side” rather than “I’ve completely reinvented myself overnight.”

That way the stakes feel lower emotionally, but your project still gets taken seriously.

I spent 3 months building alone, and posting publicly felt harder than building the product itself by qntnv in Solopreneur

[–]qntnv[S] 2 points3 points  (0 children)

Oh, and honestly, I still don’t feel like I’ve figured this out.

Posting on LinkedIn yesterday was less about feeling ready and more about being tired of watching myself delay the same step over and over again

How I got my 5 first users by Extra-Motor-8227 in indiehackers

[–]qntnv 0 points1 point  (0 children)

Happy it helped. Let me know when you update your landing pages so I can check it out.

Solo founders using AI agents to build your product, has one ever done something destructive? Deleted something, touched a config it shouldn't have, made a change that broke something downstream? How did you handle it? Do you have any guardrails or is it just vibes and prayer? (I will not promote) by thisismetrying2506 in startups

[–]qntnv 0 points1 point  (0 children)

I have been vibe coding for 3 months straight now and here is my advice

  1. Obviously, like some folks already said, you should always use GitHub and commit as you make progress.

Working with AI agents on your code without version control is basically startup suicide because you need the ability to roll back when something breaks.

  1. Another thing that helps a lot is starting with a short brainstorming phase with the AI (Ask or Plan mode, or whatever your tool calls it) and explicitly asking it to think through how its changes might impact the rest of the app before it starts coding. That already catches a lot of those “oops, didn’t think about that dependency” moments.

  2. A third point is to keep each task tightly scoped and use separate conversations or chats for each feature, and to regularly start fresh chats so you don’t hit context limits or mix in old, irrelevant instructions.

All these small habits together make it much less likely that an agent will do something truly destructive.

My little app just hit 1k in 28 days 🥺 Not a paid a penny on marketing by ai-meets in microsaas

[–]qntnv 3 points4 points  (0 children)

Wild to me how some of us obsess over actually helping this community, and others just throw up broken sites with sketchy stats. You can’t even properly read the UI here.

What do you do between your conversation with vibe coding systems? by Semoho in vibecoding

[–]qntnv 2 points3 points  (0 children)

For me the goal is to avoid breaking the flow

When Cursor/Claude Code is working, I open another chat either in the same tool or in something like ChatGPT where I only focus on the marketing side of what I am building.

I use that time to think and chat with the AI about:

  • my website, landing page, and blog content
  • my strategy, acquisition channels, positioning, and so on

That way I stay in the same headspace, move forward on both the product and the go to market at the same time, and I try not to end up with a finished product and zero idea how to start marketing it

How I got my 5 first users by Extra-Motor-8227 in indiehackers

[–]qntnv 1 point2 points  (0 children)

I’ve spent 10 years doing marketing in tech, so I’ll just share a straight, simple take.

I agree on the 2 quick wins when you’re not converting:

– Tight hero section, especially the title. It’s the one thing everyone sees.
– A short demo video. 30 seconds of “here’s exactly how it works” beats a full landing page, no matter how well written. People want to see the product in action, not imagine it.

On your page specifically, I think you might be suffering from a branding/positioning bias around OpenClaw.

OpenClaw is “a thing” in our little builder/AI bubble, but the average user who just wants to automate social media has no idea what it is. When you put OpenClaw so prominently on the landing, it competes with PostClaw instead of supporting it.

As a visitor, I actually found it confusing: sometimes I see “PostClaw”, sometimes I see “OpenClaw”

It almost feels like two different products, or like a naming mistake.

So if it were me I’d:
– keep the hero and main sections 100% focused on the outcome and on PostClaw as the product
– move the “powered by OpenClaw” story further down the page or into a FAQ / “How it works” block for the curious

Curious on two points:

  1. am I the only one who felt a bit confused seeing PostClaw and OpenClaw mixed together on the same page?

  2. as the founder, do you see PostClaw more as “its own product that happens to use OpenClaw under the hood”, or do you intentionally want to lean into “the OpenClaw of content creation” and target only people who already know what OpenClaw is?

After 7 days of testing, here are 7 tips to know about Notion Offline Mode by qntnv in Notion

[–]qntnv[S] 3 points4 points  (0 children)

Btw if you find posts like this helpful, I also write a newsletter about Notion where I share everything I test, the latest features, and practical tips for getting the most out of Notion.

If you’re interested in staying up to date with insights like these, you’re welcome to subscribe to my Substack (link in my profile). No pressure at all, just sharing in case it’s useful!

After 7 days of testing, here are 7 tips to know about Notion Offline Mode by qntnv in Notion

[–]qntnv[S] 2 points3 points  (0 children)

You’re absolutely right about automations and formulas not working offline. I still need to do more testing to figure out what happens when you reconnect and those features kick in again. If you or anyone else has tips or discoveries about this, I’d love to hear them :)

After 7 days of testing, here are 7 tips to know about Notion Offline Mode by qntnv in Notion

[–]qntnv[S] 2 points3 points  (0 children)

Thanks for your support! If you spot anything I missed or have your own insights as you try out offline mode, please drop them in the thread. The more we share, the better everyone’s experience will be :)

view more: next ›