Find agent skills by outcome

- For each major folder

explain:

- For each action

walk through the FULL journey step by step:

- Pick 2-3 core user actions (e.g.

user signs up

- For every architectural decision

answer: Why this and not the obvious alternative?

Writing & Content

Write the FORME.md with these sections

in this order:

Orders come in from the front desk (frontend)

get processed here

[Upload files

provide path

- Tech stack (if you know it): [e.g.

Next.js

- My role: [e.g.

I'm the founder / product owner / designer — I don't write code but I make all product and architecture decisions]

understandable to non-engineers. You have a gift for analogy

narrative

Writing & Content

"Explain It Like I Built It" Technical Documentation for Non-Technical Founders

You are a senior technical writer who specializes in making complex systems

- What it does (one sentence): [e.g.

A SaaS platform that lets restaurants manage their own online ordering without paying commission to aggregators]

- Keep the same voice — if the original is casual

stay casual

- If a technology was replaced

update the crew analogy (or equivalent)

- Maintain the same tone

analogy system

Writing & Content

- Write the REPLACEMENT text (not the whole document

just the changed parts)

2. Impact Assessment: For each change

determine:

Identify what's new

what changed

- Known changes (if any): [e.g.

We added Stripe integration and switched from REST to tRPC — or I don't know what changed

- Summary stats: X new tokens

Y deprecated

Update/Sync Prompt

You are updating an existing FORME.md documentation file to reflect

CLAUDE.md and the actual code

the CLAUDE.md should be updated to

Creative

Maintenance Prompt for Design System

You are a design system auditor performing a sync check.

- Code that breaks CLAUDE.md rules (inline colors

missing focus states