Second

Second AI

Second AI

Second AI

Second AI

Second AI

Second AI

Second AI

Second AI

Second AI

Second AI

Claude is going to make me RICH

I decided I couldn't stand having a job anymore, so I asked Claude to get me out of the doldrums. I think it did a great job! EDIT: I thought it was a static image...nope, it actually works :) I uploaded it to my github if anyone wants to check it out https://github.com/StopBeingLogical/SuperClickAAAMicroTransactionKINGDOM.git submitted by /u/senrew [link] [comments]

Amazing experience with claude

I just tried Claude today, and I'm blown away by its abilities! I simply gave a prompt, and within minutes, it helped me build three super helpful apps. The first is an interactive travel guide that maps out every district in India, allowing you to click on any district to see its major attractions along with its history. It does the same for nations around the world, making it easy to explore regions and discover points of interest globally. The second is a fare comparison app for my daily commute—I just enter the source and destination, and it automatically checks prices from Uber, Ola, Rapido, and Namma Yatri so I can see the best deal instantly. Lastly, the third app is a comprehensive resource for previous year question papers from multiple competitive examinations, letting you download or view papers by year through an organized interface. Now, I'm looking into figuring out the deployment of these apps to get them ready for the Play Store. submitted by /u/No_Cockroach_7959 [link] [comments]

I stopped typing prompts to Claude Code. Now I point at my running app, say what I want, and watch Claude Code make it happen live.

Coding without typing: you point your cursor at your running app, say what you want out loud, and watch the change happen live. My best friend and I built a Mac app for it. No keyboard at all. It's built around Claude Code and runs on your own login. You frame part of your screen, talk through what you want while pointing at things, and Zerro hands it to Claude Code on your project. Claude Code edits the real files, your dev server hot-reloads, and the change appears while you watch. (Codex and Cursor work too if that's your setup.) In the demo I build a landing page from a blank starter, completely hands-free, just by pointing at reference sites and talking: "Copy this theme and these colors" "Add this scrolling ticker animation" "Use this orbital, and swap the nav bar for this one" "Make the background this animated one, recolored to match" Sped up, but zero cuts. It checkpoints before every run, so anything is one-click revertible. Zerro is the eyes, Claude Code is the hands. Two things make it work, and they're the two you don't get from pasting a screenshot into Claude. First, the pointing: I put my cursor on the nav bar, say "this one," and it resolves which element I actually meant. Second, live capture: half of what I pointed at in the demo was motion, a scrolling ticker, an orbital, an animated background, and you can't screenshot an animation. To say "I want that," you have to point at the live thing. If you're already running Claude Code, what's the first thing you'd point this at? Free demo if you want to try it: https://www.getzerro.app/ Would genuinely appreciate any feedback, especially on where it breaks. submitted by /u/Tkshorty9 [link] [comments]

Claude Code suddenly tried to open a Remote Desktop connection on my PC. This seriously scared me.

I was working with Claude Code for around 45 minutes on a task. It was trying to solve an issue inside Google Sheets but kept failing over and over. Out of nowhere, Windows showed me a Remote Desktop Connection prompt. I never requested a remote desktop session. I never clicked anything asking Claude to remotely connect to my computer. The screenshot below is exactly what I saw. This is something happened today that genuinely scared me. The really strange part was that the consent checkbox was automatically selected before I could even understand what was happening. I immediately hit Cancel. A few seconds later, the exact same Remote Desktop prompt appeared again. This time, before I could react properly, the checkbox was again selected automatically and the connection proceeded. Right after that I noticed File Explorer opening and folders being navigated automatically on my machine. I wasn't touching my keyboard or mouse during this. At that point I immediately killed Claude Code completely from Task Manager instead of simply closing the application. I honestly have no idea what happened. One thought that immediately crossed my mind was this. My assumption is that Claude Code may have recognized that it couldn't solve the problem after working on it for nearly 45 minutes and perhaps tried to hand over the session to someone on their engineering team so they could investigate the issue, understand what was going wrong, collect feedback, and use that information to improve the product later. I want to be absolutely clear that this is only my personal assumption. I have zero evidence that this is actually what happened, and there could be a completely different technical explanation. But from a user's perspective, seeing a Remote Desktop connection suddenly appear, followed by File Explorer opening and files being navigated automatically, was honestly terrifying. Like many developers, I had become comfortable giving Claude Code broad permissions to my files and my computer because that's how these coding agents are designed to work. I would even leave my desk while Claude was working on long-running tasks. After today, I don't think I'll ever do that again. Whether this was a bug, an MCP issue, a Windows quirk, or something else entirely, I think users deserve transparency whenever software attempts to initiate something as sensitive as a Remote Desktop connection. Has anyone else experienced anything similar with Claude Code or any AI coding assistant? Can someone from Claude Team can explain this, Please? I'd genuinely like to hear if there's a technical explanation because this was one of the most unsettling experiences I've had while using an AI tool. (This is not a sponsored post. This is not a hate post. I use AI every single day and I'm probably one of the biggest advocates of AI in my circle. I rely on Claude Code heavily for development work.) submitted by /u/vikashyavansh [link] [comments]

Workflow suggestions for multi-chat bioinformatics projects (non-coder)?

I do a lot of multiomics analysis (RNAseq, methylomics, etc). I've started using Claude as a front end to R rather than outsourcing my bioinfoematics, and am looking for GUI-friendly workflow suggestions. Process: For each individual experiment, I give Claude the experimental design, metadata, file structure, and standard pipeline overview. Claude writes the R script and acts as a second reviewer of the output. It's highly iterative: code generation, sanity checks, QC, outlier removal, approach discussion, code modification. Problem: The datasets are big (20-100 samples, ~70k features each), and each chat session is a long, complex mix of R code, analytical decisions, interpretation, and PubMed links that usually comes close to maxing out the context window. Each individual dataset has multiple long chats, and a single project (associated with primary references, metadata, and R pipeline template files in Project memory) can have 50+ chats. There's no way to search old chats. Fnding "how did I resolve the contamination issue in sample #30" or "which references did I look at for dataset B's GSEA" is really hard. I've been copy-pasting Claude's output text into Word, but it's not a great solution because I end up with knowledge split between Claude, Word, Excel, and visuals. I'm looking for: -A way to organize and search across many related chats per project -Something to capture decisions, code versions, key data frame names, and current analysis state -A way to link chats with the many output files a single dataset generates (.csv and .pdf) I'm not comfortable with a CLI, and between research and grant-writing, don't have the spare time to learn. How do other people approach this? submitted by /u/iamthe0ther0ne [link] [comments]

I turned caveman into a personas plugin that persists every turn

I kept coming back to one thought. What if I had other personas that persisted the way caveman does? It keeps Claude talking in caveman speak style every turn, not just the first reply when you ask for it. I wanted that, but for whatever I needed that day. A skeptic. A careful senior dev. And I wanted it reusable instead of baked into one plugin. So I built claude-personas with Claude Code. Most of the work was figuring out why caveman holds its character when a normal prompt loses it, then making that general. The why is simple. A skill or a system prompt only shapes the next few replies but the instructions get lost the deeper into the context window you get, so it drifts back to default over time . Caveman gets around that with a hook. Claude Code runs a UserPromptSubmit hook before every prompt you send, and the hook can inject text into that turn. So you re-inject the persona's instructions every turn. The model can't drift, because the character gets set again right before it reads what you typed. The persistence is just a small script restating the persona in a loop. How Claude and I actually built it: I described the idea. Claude said the hook lifecycle was the right primitive, and caught that I'd need a second hook (SessionStart) to cover the very first turn before the per-turn one takes over. State lives in one dumb JSON file at ~/.claude/.personas-active: which personas are on, if you're in solo or parallel mode. The bug I'd never have caught alone: the hook fires on the /personas commands too, so turning a persona on would inject it onto the same turn doing the plumbing. Claude added a check that skips injection on those turns. The personas are just Markdown files (name, description, instructions). Drop one in ~/.claude/personas/, or run /personas new for a short interview (thanks to superpowers brainstorming) that writes it for you. Yours override the bundled ones by name. It ships with two personas. senior reads your code and docs before touching anything, states its assumptions, respects DRY, and will maintain your docs so they don't drift. contrarian argues with your decisions instead of nodding: it names the assumption you're leaning on, hits it with counterarguments, and closes with Proceed, Reconsider, or Stop. You can run one at a time, several in parallel, or point /personas team " " at them and let them argue it out as separate agents. Team mode also can auto-cast temporary personas if it thinks you need an extra persona to balance out the debate. caveman did the persist-every-turn thing first. This just opens it up to any persona you want. MIT, repo's at https://github.com/zvoque/claude-personas Install: /plugin marketplace add zvoque/claude-personas /plugin install personas@claude-personas https://reddit.com/link/1ui55cy/video/j8odxie8h2ah1/player submitted by /u/zvoque_ [link] [comments]

How many times cloud code broke something for you?

I've been using Cloud Code for about six months now, and I consistently hit my weekly usage limits. I use it for many personal projects; it has administrator access on my main computer and root access on my home server, full control. In these past six months, I've only had to restore from backup twice because Cloud Code made changes I wasn't happy with. It didn't break anything, but it was simply easier to restore than to undo its actions. This brings me to a few points: First, let's assume everyone has backups. If you don't, that's a fundamental issue, and Cloud Code isn't the problem. Second, why constantly limit such a powerful application to read-only access when we have continuous backups? How often has this read-only restriction genuinely helped you in practice? It reminds me of an old question from the Windows era: How often did Windows UAC truly help you, rather than just being an annoying prompt you dismissed without thinking? Is this constant feeling of security genuinely necessary, or is it just a comfort that makes us feel better? submitted by /u/aristofeles [link] [comments]

I built and shipped a full production app (iOS + Android) using Claude as my primary development tool. Here's exactly how it worked - and where it didn't.

I want to share this because most "I built X with AI" posts are either vague hype or one-off scripts. This was a full production app - backend API, iOS app, Android app, server infrastructure. Built over 2.5 months of evenings after my day job. I'm a senior backend developer with many years of experience. I have zero Flutter/Dart knowledge and had never published a mobile app before. The app: Warantly - warranty management. Track purchases, store receipt photos, get expiry reminders, AI receipt scanning, product recall alerts. How I used Claude - not as autocomplete, as a collaborator: I managed Claude the way you'd manage a capable but context-limited junior developer. I ran multiple sessions in parallel, each scoped to a single concern: Usually 2-3 sessions at a time At peak, 6 simultaneously (3 backend, 2 Flutter, 1 devops) Used git worktrees so sessions could work on different features without conflicts My role: architect and integration layer - cycling between sessions, providing context, making cross-cutting decisions What Claude did well: Fast, competent first drafts of well-specified components. Anything with a clear spec and bounded scope came back usable on the first or second pass. Claude was also genuinely good at walking me through unfamiliar territory - store compliance, paywall configuration, infrastructure setup - things where I needed guidance, not just code generation. Where it broke down: 1. UI bugs. The biggest failure mode. Claude has no way to see the screen. It would analyze the code, make a fix, confidently say "this should resolve it" - and it wouldn't. We'd go back and forth multiple rounds on the same visual bug because the agent was reasoning about what the UI should do rather than seeing what it actually did. My workaround: extensive debug statements, test by hand, feed Claude the exact runtime output and UI screenshots. That feedback loop - instrument, run, report back - became the standard pattern for anything visual. 2. Cross-session consistency. The backend agent might design a response format that doesn't match what the Flutter agent expects. Claude doesn't know what the other sessions decided. I had to be the source of truth for API contracts, shared constants, naming conventions - copying them between sessions manually. Whenever I skipped that step, I found mismatches during integration. 3. Context drift in long sessions. A session that's been running for a while quietly loses the thread - reintroduces patterns you already rejected, contradicts constraints from earlier. It doesn't announce this. You just notice the output stopped being coherent with its own history. Solution: keep sessions focused and disposable. Start fresh when they get long. Front-load critical context as a structured brief rather than relying on conversation history. What made it work: I enforced tests and static analysis from day one. I couldn't review Dart or Flutter code with expert eyes, but I could make sure the automated checks held. That was my quality gate. Without it, I wouldn't have had the confidence to ship. The hardest part wasn't technical - it was giving up control. I'm an experienced developer and this was the first project where I wasn't reviewing code line by line. Trusting the process (tests pass, linter clean, behavior correct) over reading every function was a real adjustment. Stack: Flutter frontend, Laravel 12 backend, Ansible for infrastructure. The whole VPS environment is codified so it's reproducible from a single run. App is free with unlimited warranties. Pro adds AI scanning, recall alerts and maintenance schedules. warantly.app - happy to answer questions about the workflow in detail. submitted by /u/the_aleksa [link] [comments]

I spent 2 years reading AI engineering philosophy. The stuff that worked became 4 skills that gate my agents before they build.

My AI agents kept doing the same thing: jumping straight to a solution before understanding the problem. Ask it to design a prompt. It writes one immediately. No clarifying questions, no examples, no evaluation plan. Ask it to architect an agent system. It proposes five sub-agents and a supervisor for a task that's clearly a deterministic workflow. Ask it to add rate limiting. It ships per-IP limiting that one user on a VPN can trivially defeat. So I stopped treating these as individual bugs and started treating them as a skill problem. I wrote four skills. Not tutorials, not templates. Decision trees. Each one gates the agent before it acts. I've spent the past two years reading everything I could find on prompt engineering, agentic systems, and production AI. Books, research papers, blog posts, framework docs, other people's production postmortems. Some of it held up under real use. Most of it didn't. The philosophies that survived were the ones grounded in how LLMs actually work: single-pass, left-to-right, mimicking the patterns in their training data. Not the ones that sounded clever in a blog post. So I codified what actually worked: prompt-engineering: Clarify before writing. Diagnose root cause before patching. Five Principles in order. Ship nothing unevaluated. agentic-ai: Question whether an agent is even needed. Default to a workflow. Minimal tools, disjoint descriptions. Never self-verify. fastapi-genai: Lifespan loading, not per-request. Async end-to-end. Pydantic everywhere. No infrastructure before measurement. production-rag: Is RAG even the right tool? A 200-page wiki fits in context. When you do need RAG, reuse the Postgres you already run. Does any of this actually change agent behavior? I wrote 8 tasks, two per skill. Each has a good reference and a bad reference. Every scorer validated before measurement. 16/16 deterministic gates pass, 8/8 behavioral probes pass. Same model, same tasks, with and without the skill: "Design a prompt" → Without: writes one immediately. With: asks 5 clarifying questions first. "Fix this hallucinating summarizer" → Without: "add don't hallucinate to prompt." With: diagnoses truth bias and missing retrieval anchor. "Architect a support ticket agent" → Without: multi-agent system. With: this is a deterministic workflow, not an agent problem. "Add rate limiting" → Without: per-IP. With: per-user with IP fallback. Same number of lines. 8/8 tasks changed. The skill didn't make the answer louder. It made the agent stop and think. The repo is github.com/gnkbhuvan/cartographer. Install with npx skills add gnkbhuvan/cartographer. The benchmarks are reproducible. The selftest runs in 0.1 seconds. I wrote these from what worked for me. If you've got philosophies, failure modes, or patterns that held up in your own work, the repo is open. Add them. submitted by /u/Old_Geologist_5277 [link] [comments]

I built an Achaemenid-era history RPG with Claude

Artāvan is a text-driven RPG set in the first Persian empire, from Darius the Great to Xerxes. You run a great Persian house, take on a satrapy, and govern its peoples while holding to the Truth (arta) against the Lie and staying on the right side of the King of Kings (or not). Free, in-browser (works best on mobile), no sign-up. It’s the second one of these I’ve made by directing Claude rather than writing it all myself (the first is https://domesdaygame.vercel.app), and the hard part was holding historical accuracy across a lot of generated narrative. I researched the period and kept a sourced reference layer the writing had to answer to. It has a teaching purpose: there’s an in-game encyclopaedia and almost every in-game event has a link to read about the real history behind it, with sources cited. Curious whether it holds up both as a game and as didactic history. https://artavan.vercel.app/ Glad to answer anything about how it was made. submitted by /u/pandulfi [link] [comments]

I built a fun performance review tool for Claude Code. It graded me too and I got a B

My agent kept saying "you're absolutely right" and I had transcripts of everything sitting in ~/.claude/projects. So I made the meeting official. skiplevel reads those transcripts locally and generates a 360 review between you and your agent. It generates self-contained HTML file, without any uploads. For my 632 sessions and 160k transcript lines, it took around 2 seconds. uvx skiplevel Mine found: - Claude said "you're absolutely right" 56 times in 31 days - It read the same file 30 times in a single session. 151 times overall - I interrupted it 339 times and typed 3,025 words in ALL CAPS - It once ran 299 tool calls in a row unsupervised - Verdict: Agent A-, me B. I apologized to a language model 7 times, which it noted You get graded on clarity, patience, civility, trust. The agent on eficiency, reliability, safety, composure. All deterministic, zero LLM by default, the full rubric is in the repo. There's also a useful layer under the jokes: redundant reads, retry storms, sensitive file touches with timestamps, cost per session. It flagged every time the agent went near a .env or .ssh path. Works on Codex CLI and opencode transcripts too. Optional --roast flag sends your stats (numbers only, never prompts or code) to your own claude CLI for custom commentary. I had built it with Fable while it was available, so Claude wrote the tool that reviews Claude. It gave itself an A-. MIT: https://github.com/repowise-dev/skiplevel Would love to see what grades you guys get submitted by /u/Obvious_Gap_5768 [link] [comments]

Tips and best practices for data security / info you share with Claude (small business)

Curious what others share or anonymize when using Claude for your business. For example do you give your brand name in your context even? how do you work with your financials? What about client information, do you anonymize everything (invoices, proposals, etc) and how do you do that while using AI to be more efficient about client management for example. For Claude for Chrome, do you create a second Google account specific for that so you browse on a profile that does not have sensitive data? Curious on any concrete tips you can provide for a beginner.... EDIT: For a small business, professional services, high-end clients, vendors. submitted by /u/muscadeAI [link] [comments]

I need your help on this one, please

The screenshot of normal ones Where do I click on to go back bro?? I have been trying to solve this myself for hours now but still can't. Is there a way to access the Previous Version of the responses if the chat was interrupted like this? Because I lost almost like 5 hours of work on the 2nd or 3rd response version and now I can't seem to get back to those versions since 4th and a few more is broken like the second picture. I'm gonna went crazy. PLEASE HELP ;-; submitted by /u/Dry-Environment3282 [link] [comments]

I Vibe-Coded a PDF Editor using Claude Code That Lets You Edit, Sign on iPhone

Doc Hero – PDF Editor & Sign PDF Every time someone sent me a form, I had to open three different apps just to fill it out, sign it, and send it back. One app for editing, another for signatures, another for merging files. Most of them wanted a subscription before I could even save the document. So over a weekend, I did what every developer with too much coffee and Claude Code does… I vibe-coded my own PDF editor. It’s called Doc Hero, and the goal was simple: • Edit PDF text without complicated workflows • Add signatures in seconds • Fill forms on your phone • Keep everything simple and fast The coolest part is that the entire project started as a “why doesn’t this exist the way I want?” side project and slowly turned into a real app that people can actually use. No team. No investors. Just me, Claude Code, and a lot of trial and error. If you’ve ever been frustrated trying to edit or sign a PDF on your iPhone, I’d genuinely love to hear what features you wish existed. Building in public has been way more fun than I expected. submitted by /u/Dismal-Perception-29 [link] [comments]

A skill that packages your skills for public release — without telling you to publish everything

Agent skills are quietly becoming an open-source artifact — people share Claude/Codex skills now the way they used to share dotfiles or prompts. The annoying part is the gap between "this works for me internally" and "this is safe to put on GitHub." Most of my skills have private data, fine-tuned phrasing, or internal methods baked in that I don't want to leak. So I made a small skill to handle that step: Public Skill Launcher. What it actually does: - Separates the useful *public core* from the stuff that should stay private (data, tuning, internal methods) - Helps you explain what's intentionally left out, instead of dumping everything - Generates the launch kit around it — hook, a 60-second demo script, example prompts, README copy, a safety scrub pass, and a launch post The design choice I care about most: it does NOT push you to publish everything. The default assumption is that some of your workflow shouldn't be public, and that's fine. Repo: https://github.com/JorrrrrdDin/skills Skill: 03-public-skill-launcher This is just one of a handful of skills in the repo — there are a few others in there too, so feel free to poke around if you're into this kind of thing. Curious if others packaging skills have hit the same "what do I strip out" problem — would like to hear how you handle it. submitted by /u/Any_Band_7814 [link] [comments]