Claude Project: A Home for Your Coding Standards, Snippets, and Client Conventions

What This Builds

A Claude Project loaded with your own coding standards, a library of PHP and JavaScript snippets you've written and reused, and a short doc of per-client conventions (naming patterns, folder structures, quirks specific to how each client's site is set up). Instead of re-explaining your naming conventions or hunting through an old project for a function you know you already wrote, you open the Project and ask. Custom theme and plugin work stops drifting in style from project to project because there's a single reference every new build gets checked against.

Prerequisites

• Pro account ($20/month), since the free tier caps the number of Projects you can create
• A rough sense of your own coding conventions, even if you've never written them down formally
• A handful of snippets or functions you've reused across more than one project
• Total ongoing cost: $20/month, the same subscription tier you'd want for any serious coding help from Claude

The Concept

A Claude Project is a workspace that remembers things between conversations, unlike a regular chat that starts blank every time. You upload files once. Every new chat inside that Project can see them without you re-pasting anything. Think of it as a shared reference binder that sits next to you while you work: your standards doc, your snippet library, and your notes on each client's setup, all in one place Claude can search when you ask it a question.

Build It Step by Step

Part 1: Write down what's currently only in your head

Most freelancers have coding conventions they follow without ever writing them out. Before building the Project, spend 20 to 30 minutes turning that into a short document:

• Naming conventions (function prefixes, CSS class patterns, file naming)
• Preferred code structure (how you organize a custom plugin, where custom functions live in a theme)
• Formatting preferences (tabs vs. spaces, how you comment code, how you structure a WordPress hook)
• Anything you actively avoid (inline styles, deprecated functions, specific plugins you won't build on top of)

This doesn't need to be exhaustive on day one. A rough first pass you refine over time works better than waiting until it's perfect.

Part 2: Collect your reusable snippets

Go back through two or three recent projects and pull out functions, snippets, or small utilities you've written more than once: a custom WooCommerce hook, a reusable ACF field setup, a sanitization function, a common enqueue pattern. Save these into a single text file with a short comment above each one explaining what it does and when to use it.

Part 3: Create the Claude Project

1. In Claude, click New Project in the left sidebar
2. Name it something you'll recognize at a glance, like "Dev Standards" or "[Your business name] Build Reference"
3. In the custom instructions field, describe how you want Claude to use the uploaded material, for example:

This Project holds my coding standards, a library of reusable PHP and JavaScript snippets, and notes on conventions specific to individual clients. When I ask for help writing or reviewing code, check it against my standards document first. When a task resembles something in my snippet library, point me to the existing snippet before writing a new one from scratch. If I mention a specific client, check the per-client conventions file for anything relevant to that project before answering.

1. Under Knowledge, upload your standards document and your snippet library file from Parts 1 and 2

Part 4: Add per-client conventions as you go

Rather than trying to document every client up front, add a short conventions note for each active client as you start or revisit their project: their theme's folder structure, any naming quirks inherited from a previous developer, plugins they specifically want avoided, hosting environment notes relevant to code (PHP version, caching setup). Keep each one brief, a paragraph or two per client is enough for Claude to reference usefully.

Part 5: Use it in daily work

Open a chat inside the Project (not a regular Claude conversation) whenever you're writing or reviewing custom code. Ask it directly to check your snippet library first: "Before writing this, check if I already have something like it in my snippets." Over time this becomes the default way you start any custom code task.

Real Example: Reusing a Snippet Instead of Rewriting It

Setup: Your Project holds a standards doc (function prefix rc_, no inline styles, hooks live in a dedicated includes/hooks.php file) and a snippet library including a reusable ACF-to-WooCommerce field sync function you wrote for a previous client.

Input: "I need to sync a custom ACF field to a WooCommerce product's short description on save for a new client's site. Check if I have something like this already."

Output: Claude finds the existing sync function in your snippet library, flags that it was written for a slightly different field type, and adapts it to the new client's field setup rather than writing a fresh function, using your rc_ prefix and hook file convention automatically.

Time saved: What would mean either rewriting the function from memory or digging through an old project's files becomes a two-minute lookup and adaptation.

What to Do When It Breaks

• Claude ignores the uploaded standards and writes generic code → check that you're working inside the Project chat, not a regular conversation; uploaded files only apply inside the Project. If you are inside it, make the custom instructions more directive: "Always apply my standards document before answering, even if I don't mention it."
• Snippet library gets too large to be useful → split it into multiple smaller files by category (WooCommerce, ACF, general utilities) instead of one long file. Claude searches shorter, well-labeled files more reliably than one sprawling document.
• Per-client notes go stale → add a habit of updating a client's conventions note right after you notice something new about their setup, rather than trying to remember to do it later.
• You hit your plan's Project limit → archive Projects for clients or code areas you're no longer actively working in rather than deleting them, so you can restore them later if that work picks back up.

Variations

• Simpler version: Keep the standards doc and snippet library as plain files in a folder you paste into a regular Claude chat when needed. No Project setup, but you retype less context than starting from a blank prompt each time.
• Extended version: Add a "review" custom instruction that has Claude specifically check new code against your standards doc before you commit it, turning the Project into a lightweight code review step as well as a reference library.

What to Do Next

• This week: Set up the Project with whatever standards and snippets you can pull together in an hour, even if incomplete
• This month: Add per-client conventions for your active projects and start defaulting to the Project chat for all custom code work
• Advanced: Cross-reference this Project with your GitHub repos so snippets you save here match what's actually committed, keeping the library from drifting out of sync with your real codebase

Advanced guide for freelance web developer professionals. These techniques use more sophisticated AI features that may require paid subscriptions.

A note on client data: per-client convention notes should describe patterns, not secrets. Keep hosting credentials, API keys, database passwords, and customer or order data out of anything you upload to this Project. Naming conventions and folder structures are safe to store; login details and live client data are not.