DEV Community: Poorvith M P

I Built a Privacy Scrubber So My Prompts Stop Leaking Data to AI Models

Poorvith M P — Mon, 06 Jul 2026 06:00:54 +0000

I Built a Privacy Scrubber So My Prompts Stop Leaking Data to AI Models

Tags: #privacy #javascript #webdev #buildinpublic

Every prompt you send to an AI model is a potential data breach waiting to happen. That sentence sounds dramatic until you've actually watched someone paste a client NDA into ChatGPT to "just summarize the key terms real quick." Names, deal values, jurisdiction clauses, signatures — all of it, sitting on a third-party server the moment you hit enter. Nobody meant any harm. That's exactly the problem: the leak isn't malicious, it's just convenient.

I kept seeing this pattern everywhere — in my own workflow, in coworkers' Slack messages ("hey can you check this contract with GPT"), in random Twitter threads. So I built something to stop it before it happens, and I want to walk through why and how.

The problem, in three parts

Corporate IP leakage. Internal docs, proprietary code, product roadmaps — the moment they're pasted into a prompt, you've lost control of where that text lives and who (or what) gets trained on it.
Regulatory risk. Paste patient notes into a chatbot and you've potentially violated HIPAA. Paste a client's legal filing and you're in murkier territory with privilege and confidentiality obligations. Most people don't even realize they've crossed a line until it's already crossed.
Plain old data leakage. Emails, phone numbers, addresses, ID numbers — PII sitting in plaintext, sent to a server outside your control, with no undo button.

The solution: scrub before you send, not after

The core idea is simple: nothing sensitive should ever leave your browser. So the whole thing runs client-side, no exceptions. The flow looks like this:

[ Paste your prompt ]
        |
        v
[ Regex-based PII scan ]   <-- runs entirely in-browser
        |
        v
[ Placeholder replacement ]  e.g. "John Smith" -> "[PERSON_1]"
        |
        v
[ Scrubbed prompt ready to send to any AI model ]
        |
        v
[ Vault export ]  <-- encrypted mapping saved locally,
                       so you can restore real values later

You paste your text, the scanner flags anything that looks like a name, email, phone number, ID, or address, and swaps it for a neutral placeholder. You get a clean prompt to send wherever you want, and a local "vault" file that holds the placeholder-to-real-value mapping — so if the AI's response references "[PERSON_1]," you can decrypt and restore it back to the real name afterward, entirely on your machine.

What's under the hood

Nothing fancy, and that's deliberate. It's vanilla JavaScript — no framework, no build step, no bundler to fight with. That keeps the whole thing auditable: you can open the source file and read every line of what's touching your data, instead of trusting a black box. For exports, it uses jsPDF to generate a clean scrubbed-prompt PDF, and localStorage handles session recovery so you don't lose your work if you accidentally close the tab mid-scrub.

What's next

Regex gets you far, but it has ceilings — it'll miss context-dependent PII and occasionally flags things it shouldn't. Next up is NER-based detection (named entity recognition) to catch more nuanced cases without turning this into a server-side tool that defeats the entire point. After that: a browser extension so scrubbing happens inline wherever you're typing, and eventually a lightweight API for teams that want this baked into their internal tooling without every employee needing to remember to run it manually.

Try it

The app is live, the code is open, and I'd genuinely rather hear "this missed X" than have people quietly stop trusting it. Link to the live app and the GitHub repo are below — open an issue if something breaks or if there's a PII pattern I haven't accounted for.

[Live app link https://aiscrubber.vercel.app/] · [GitHub repo link https://github.com/prvthmpcypher/aiscrubber]

Why I Built a Portfolio Generator That Gives You the Files, Not a Subscription

Poorvith M P — Sun, 05 Jul 2026 10:28:06 +0000

Every "portfolio builder" I tried had the same pitch: sign up, drag some blocks around, and then — right when you're happy with it — hit a paywall. Custom domain? Pro plan. Remove the watermark? Pro plan. Export your own HTML? Absolutely not, that's the whole business model.

And even if you pay, you're still locked into their hosting. Your portfolio — the thing meant to represent you — lives on someone else's infrastructure, behind someone else's uptime guarantees, subject to someone else's pricing changes next year.

That's the problem I wanted to kill: trials that convert to fees, lock-in disguised as convenience, and hosting you don't control for a site that's supposed to be the one asset you fully own.

The Core Decision: No Server, No Hosting, No Accounts

So the design constraint I set for myself from day one was blunt: everything runs client-side. No backend, no database, no login, no "your data lives on our servers." You open the page, build your portfolio in the browser, and click download. Out comes a ZIP file with clean, static HTML/CSS/JS — a real website you can drop into GitHub Pages, Netlify, Vercel, or a $2/month shared host. No dependency on my app ever staying online for your site to keep working.

This wasn't just a philosophical stance — it also happens to be the only architecture that fully removes the incentive to gate features behind a subscription. If there's no server cost per user, there's nothing to monetize by throttling you. The tool is either useful enough that people star it and use it, or it isn't. That's the whole business model, and I'm fine with that.

The Block Library

The builder works on a simple mental model: your portfolio is a stack of self-contained blocks, and you arrange, configure, and reorder them visually. The usual suspects are there — Hero, About, Projects, Skills, Contact, Footer — each with enough configuration to not look like a template clone.

The one I'm most proud of is the GitHub Feed block. Point it at your username and it pulls your pinned repos (or most recently active ones) directly at build time, rendering them as project cards with language, stars, and description — no manual copy-pasting your project list every time you ship something new. For a lot of developers, their GitHub activity is their portfolio; this block just stops pretending otherwise.

Under the Hood: Wizard → Schema → HTML → ZIP

The architecture is intentionally boring, because boring is reliable:

The wizard collects a JSON schema. Every choice you make in the UI — block order, content, colors, fonts — gets serialized into a single JSON object. Nothing is hidden in component state that can't be reconstructed; the schema is the source of truth for your entire site.
builder.js compiles the schema into HTML/CSS strings. No frameworks bundled into the output, no virtual DOM shipped to your visitors. Each block type has a corresponding template function that takes its slice of the schema and returns plain markup and scoped styles. The output is what you'd write by hand if you had the patience.
JSZip bundles the result into a downloadable archive. HTML, CSS, any assets, all packaged into a proper folder structure — ready to unzip and deploy, not a single unstyled file you have to untangle.
FileSaver.js triggers the actual download. The moment you click "Export," the browser hands you a .zip and the tool's job is done. You now own a static site with zero runtime dependency on me.

The nice side effect of this pipeline: since the schema is just JSON, saving and loading a project locally, or eventually syncing it, is trivial — it's all just serialization, no format lock-in.

What's Next

A few things on the roadmap:

PDF export — same schema, different renderer, so you can hand a recruiter a resume-style PDF built from the same content you used for your site.
More blocks — a Spotify Now Playing block for people who want a bit of personality on their site, and a blog RSS block so your latest posts show up automatically instead of going stale the day after you publish.

The goal is the same as it's always been: more ways to represent yourself accurately, none of which require anyone's permission or subscription to keep working.

Try It https://portfoliogen-cyan.vercel.app/

The whole thing is open source. If you build a portfolio with it, I'd genuinely like to see it. If something breaks, or a block you want doesn't exist yet, open an issue — and if it's useful to you, a star helps more than you'd think for a solo project like this.

15 Claude Skill Files That Run Business Ops — What They Are and How to Use Them

Poorvith M P — Sun, 28 Jun 2026 06:30:32 +0000

If you've used Claude for work, you've probably copy-pasted the same prompt more than once.

The problem: every new conversation, you start from scratch. The role, the output format, the edge cases, the tone — all lost. You rebuild it every time.

Claude skill files fix this. Here's exactly what they are, how they work, and 15 pre-built ones for business productivity.

What Is a Claude Skill File?

A Claude skill file is a structured .md file you drop into Claude Projects as a project instruction.

Once it is in there, every conversation in that project starts with Claude already knowing:

What role to play
What workflow to follow step by step
What the output format should be
How to handle edge cases

You are not prompting. You are deploying a specialist.

The difference in output quality is significant. A good skill file is the difference between Claude giving you a generic response and Claude giving you a professional deliverable.

The Skill File Format

Every skill file has this structure:

---
name: [skill-name]
description: [one sentence — when Claude should activate this skill]
---

# [Skill Name]

[Role definition — who Claude becomes in this skill]

## Process
1. [Step one]
2. [Step two]
3. ...

## Output Format
[Exact structure of what Claude will output]

[Domain-specific frameworks, examples, and guidance]

The description field in the header is the trigger — it tells Claude Projects exactly when this skill is relevant. The ## Process section is the workflow. The ## Output Format section eliminates Claude improvising its structure.

How to Set One Up

Go to claude.ai → New Project
Click Project Instructions in the left sidebar
Paste the full contents of the .skill file — or drag and drop the file
Start a conversation in that project
Claude immediately works as that specialist

That's 30 seconds of setup. After that, the skill is there every time you open that project.

Why Skill Files Beat Prompts

Prompt	Skill File
Rewritten or re-pasted every session	Loaded once, persistent across all conversations
You have to remember the format	Claude outputs the correct format automatically
No role continuity between sessions	Claude maintains the specialist role
Easy to forget edge cases	Edge cases are built into the file
Generic output unless you specify everything	Specific, professional output from the first message

Once you use a skill file for a few sessions, going back to raw prompts feels like a downgrade.

15 Claude Skill Files for Business Productivity

Here is a breakdown of each one, what it does, and when to use it.

Operations

Business Plan Outliner
Give it your business idea. It outputs a complete lean business plan: problem statement, solution, market analysis (TAM/SAM/SOM), competitive landscape, business model, go-to-market strategy, 12-month financial projections, and key milestones. Also includes a "5 questions a business plan must answer" framework and a financial projections reality check.

Best for: founders with an idea they need to pressure-test, anyone preparing to pitch or launch.

SOP Writer
Describe any process verbally. It outputs a formal Standard Operating Procedure with numbered steps, decision points (if/else branches), role assignments, exception handling, and quality checks. Structured for delegation and compliance.

Best for: anyone building a team, scaling a process, or preparing for handoff.

Meeting Summariser
Paste raw meeting notes, a transcript, or a rough bullet list. It outputs a structured summary: key decisions made, action items with owners, key discussion points, and next steps. Cuts meeting documentation time from 30 minutes to 2 minutes.

Best for: anyone who runs or attends meetings and needs clean records.

Client and Finance

Client Proposal Writer
Give it a project brief — what the client wants, your approach, timeline, and price. It outputs a professional, conversion-optimised proposal with executive summary, scope of work, deliverables, timeline, investment breakdown, and terms. Structured to win projects.

Best for: freelancers, agencies, consultants, anyone who needs to propose to clients.

Invoice and Payment Writer
Give it the project details, invoice amount, and payment terms. It outputs professional invoice copy and a complete 3-email late-payment sequence — the initial reminder, the follow-up, and the final notice — each calibrated to maintain the client relationship while actually getting you paid.

Best for: freelancers and consultants who lose money on late payments.

Negotiation Coach
Describe any negotiation — salary, vendor contract, deal terms, partnership. It coaches you through BATNA analysis (your best alternative), opening position strategy, concession planning, talking points, and psychological tactics. Gives you a pre-negotiation brief you can actually use.

Best for: anyone preparing for any negotiation of real consequence.

Contract Clause Explainer
Paste any contract clause or section. It explains what it means in plain English, what the practical implications are, whether the term is standard or one-sided, and what to push back on or negotiate. Not a lawyer, but a translator.

Best for: freelancers and founders reading contracts without legal support.

Strategy and Goals

OKR Designer
Give it your company or team goals for the quarter. It outputs a complete OKR framework: inspiring objectives (qualitative), 3–5 measurable key results per objective, a check-in cadence, and a grading guide (0–1.0 scoring). Structured the way OKRs are actually meant to be used.

Best for: founders, team leads, anyone setting goals they actually want to measure.

Decision Framework
Give it a difficult decision. It applies four structured frameworks simultaneously: Pros and Cons, 10/10/10 thinking (how will you feel about this in 10 minutes, 10 months, 10 years), Regret Minimization (which choice will you regret less), and Second-Order Thinking (what are the downstream effects). Gives you a clear recommendation with reasoning.

Best for: any significant decision where you are stuck or second-guessing.

Productivity Audit
Describe your current workflow, daily schedule, and work habits. It identifies bottlenecks, time drains, and inefficiencies in your system, then gives you a specific action plan with implementations you can start immediately. Treats your workflow as a system with inputs, outputs, and failure points.

Best for: anyone who feels busy but not productive.

Weekly Review System
Guides you through a structured weekly review: wins from the week, incomplete tasks and what to do about them, what worked and what did not, lessons learned, top 3 priorities for next week, and scheduling those priorities into your calendar. Structured as a conversation, not a form.

Best for: knowledge workers who want consistent weekly reflection without it taking an hour.

People and Hiring

Job Description Writer
Give it a role's requirements — responsibilities, skills needed, team context, and what you are actually looking for. It writes a compelling, bias-reduced job description that is specific enough to attract qualified candidates and honest enough to filter out mismatches.

Best for: founders and team leads writing JDs for the first time or the fifth time.

Feedback Giver
Share a piece of work — a document, design, code, presentation, or process. It delivers structured feedback using the SBI framework (Situation, Behavior, Impact): what specifically happened, what the effect was, and what to do differently. Honest without being vague or harsh.

Best for: anyone who needs to give feedback and wants it to actually help.

Investor Pitch Deck Writer
Give it your startup description — what you do, who you are for, why now, what you have built so far. It writes a complete pitch narrative slide by slide: problem, solution, market, product, traction, team, business model, ask. Includes speaker notes for each slide and the key data points to include or find.

Best for: founders preparing to raise or present to any investor audience.

Tools

Notion Database Architect
Describe your workflow and what you need to track. It designs an optimal Notion database structure: which tables to create, how to relate them, which rollups and formula fields to add, which views to build (board, gallery, timeline, calendar), and where automations would help. Structured as a build plan you can follow step by step.

Best for: anyone building in Notion who keeps redesigning their workspace.

Where to Get All 15

I have packaged these 15 skill files as a Gumroad download — all 15 .skill files in one zip, with a README explaining how to use each one.

₹599 (~$7.2 USD). Instant download.

→ https://poorvith.gumroad.com/l/business-claude-skill

This is the Business and Productivity pack. Part of a larger collection — 100 Claude skill files across 7 categories including Developer Tools, Marketing and Growth, Design and UI/UX, Writing and Content, Education and Learning, and Personal OS.

Building Your Own

If you want to build a skill file for something specific, the format above is all you need.

Start with one workflow you repeat more than once a week. Write:

The role Claude should play
The step-by-step process
The output format

That is a skill file. Drop it in Claude Projects. Refine it over a few sessions.

The compound effect builds fast — every skill file you add is permanent leverage on every similar task going forward.

Built by Poorvith M P — pre-college dev building AI tools and selling them. Find more at poorvith.gumroad.com.