Operational system · Case study

My AI workspace system

In daily use

A personal AI operating setup I designed in Claude. Custom Skills hold my tools and rules, Projects keep each work stream separate, and Google Drive follows one structure and one naming convention.

Built in
Claude
Skills
9 custom Skills
Drive
8 numbered root folders
Rule
I approve first

Problem

I use AI for the same kinds of work every week. Without a setup, each new conversation needs my tools, rules and file conventions explained again, and files end up wherever they were made.

My role

I designed the whole setup: the Skills, the Projects, the Drive structure and the naming convention. I use it every day.

How it works

Every request follows the same path. Nothing leaves the workspace until I approve it.

01 · REQUEST I ask for something 02 · SKILL One of 9 custom Skills Reusable instructions: my tools, rules and approval steps. coding-agent-prompt-builder job-application-tailor n8n-workflow-builder meeting-to-actions ea-daily-weekly-report diamond-pressure-content prompt-doctor drive-filer school-writing-coach 03 · DRAFT Claude prepares the work Inside a Project, organised by work stream. 04 · APPROVAL I approve Before anything is sent, submitted or filed. 05 · GOOGLE DRIVE 8 numbered root folders 00 Inbox → … → 07 Archive YYYY-MM Type - Descriptor (context) Nothing is deleted. It goes to Archive.
  • Skills. Each of the 9 Skills is a reusable instruction set that encodes my tools, rules and approval steps for one kind of work.
  • Projects. Projects are organised by work stream, so each stream keeps its own context.
  • Drive. Google Drive has 8 numbered root folders, from 00 Inbox to 07 Archive.
  • Names. Every file follows YYYY-MM Type - Descriptor (context).

Key decisions

  • I approve first. I approve before anything is sent, submitted or filed. This rule runs through every Skill.
  • Rules live in the Skill. My tools, rules and approval steps are written once in each Skill, so I don't restate them in every conversation.
  • One naming convention. Every file uses the same pattern, so I can find it by date, type and context.
  • Nothing is deleted. Files that are no longer needed go to the Archive folder.

What's done vs in progress

In daily use

  • 9 custom Skills.
  • Projects organised by work stream.
  • Google Drive structure with 8 numbered root folders.
  • One file naming convention.

In progress

  • Expanding the workspace.

Limitations

  • It is a personal system, built around how I work.
  • Nothing runs unattended. Every send, submission and filing waits for my approval.
  • Client names and private file names are left out of this page, so the diagram shows the structure, not real files.

Links