Back to database

Hilary Gridley's AI use case

Writer and operator at Independent

Runs a personal life-automation system from Claude Code, using terminal workflows, iPhone Shortcuts, Obsidian, and Cursor to plan her day, capture tasks, manage preferences, automate returns, and create anonymized demos.

The problem

What was broken before AI

Life admin rarely arrives in a clean project-management format. A task pops up while you are walking around. A return requires a label, a deadline, and a drop-off plan. Preferences live in your head until you have to explain them again. Productivity systems can become another thing to maintain, especially when they require constant sorting, tagging, and manual cleanup.

What changed

What the use case made possible

Hilary uses Claude Code as a flexible command center for small personal workflows. iPhone Shortcuts let her capture tasks quickly. Obsidian gives her a place for notes and context. Claude Code can plan the day, organize personal preferences, help with returns, and build little utilities without needing a polished app. The system stays useful because it is shaped around the moments when life actually creates friction.

Why this matters

Why this use case is worth studying

Hilary’s workflow is valuable because it avoids the fantasy of a perfect life system. Instead of building one giant dashboard, she uses AI to handle small moments of friction as they appear. That makes the setup feel more human: capture the thing quickly, keep the context nearby, and let the tool do enough organizing that you can move on with your day.

Use this when

When this pattern applies

Use this pattern when life admin keeps leaking out of normal productivity tools. It works especially well for small recurring problems that are personal, annoying, and not quite worth a full app: capture, planning, reminders, returns, preferences, and tiny household workflows.

Exponential Builder analysis

01

Build from friction, then stop.

Hilary’s setup shows that useful AI systems often begin with one repeated annoyance, not a grand productivity redesign. The discipline is knowing when a tiny helper has solved enough of the problem.

02

Capture has to live where the task appears.

Phone shortcuts, notes, and terminal workflows matter because life admin rarely waits until you are sitting inside the right app. AI becomes more useful when the handoff from real life to system is almost immediate.

03

Personal context is the real interface.

Preferences, routines, deadlines, and notes give Claude Code something grounded to work with. The leverage comes from keeping that context close enough to reference without turning it into a database you have to babysit.

Who this is for

Best fit

People who dislike rigid productivity systems

Operators managing lots of small personal tasks

Parents or caregivers juggling scattered reminders

Writers or knowledge workers already using notes

People comfortable trying lightweight shortcuts or scripts

Anyone who wants personal automation without building a full app

What to avoid

Mistakes and warnings

Where this pattern can go wrong if you copy it too literally.

Do not build a giant productivity system before solving one real problem.

Avoid automations that require more upkeep than the task itself.

Keep private context in places you understand and trust.

Make capture fast enough that you will actually use it.

Review personal or financial actions before letting a workflow move too far on its own.

Public workflow preview

The shape of the workflow

A high-level look at how the use case works, with the reusable pattern made clear.

01

Start with the real friction

Hilary looks for small life-admin moments that are annoying enough to repeat, like planning the day, capturing a task, or handling a return.

02

Keep capture close to the moment

iPhone Shortcuts make it easy to send a task or note into the system before it disappears.

03

Give Claude useful personal context

Preferences, notes, and routines live in files the assistant can reference when helping.

04

Build tiny tools instead of one giant system

Claude Code can create scripts, helpers, and workflows around one problem at a time.

05

Keep the system flexible

The setup works because it can change as life changes, rather than demanding that every task fit a rigid structure.

Copy the pattern

The reusable idea

Pattern in one sentence

Use AI to build small, forgiving tools around the life-admin moments that actually create friction.

Reusable idea

Hilary’s use case is a reminder that personal automation works best when it starts with annoyance, not architecture. Pick the small thing you keep forgetting, retyping, explaining, or putting off. Give AI just enough context to help with that one moment. If it works, keep it. If it adds more maintenance than relief, throw it away.

Steal this workflow

Use the “one annoying loop” template:

1

Pick one life-admin task you keep delaying, forgetting, or re-explaining.

2

Write down where it starts: phone, email, notes, calendar, shopping flow, return label, or daily planning.

3

Create the fastest capture point you will actually use, such as a shortcut, quick note, or command.

4

Make a short context file with the preferences, constraints, deadlines, links, and privacy boundaries Claude should reference.

5

Ask Claude Code for one helper only: a checklist, script, filing flow, planning routine, or tracking template.

6

Test it in the exact moment the task usually happens.

7

Keep it if it reduces effort. Simplify or delete it if it creates another place you have to maintain.

Suggested prompt

“I want to turn one recurring life-admin annoyance into a small personal workflow, not a full productivity system. The problem is: [describe the recurring annoyance]. It usually starts in: [phone/email/notes/calendar/shopping/returns/daily planning]. My relevant context and preferences are: [paste or summarize]. The output should land in: [Obsidian note/task list/calendar/file/etc.]. Privacy boundaries: [what should not be exposed or automated]. Help me design the simplest workflow for this, including the capture step, the context file I should create, and one small Claude Code helper or checklist I can test this week.”

Field notes

Get new AI use cases in your inbox

A short weekly note on how real people are using AI to save time, make money, build tools, and run their lives.

No spam. Just useful AI use cases.

Related use cases

Keep exploring nearby systems.

Browse all