Find agent skills by outcome

When a user clicks 'Place Order'

here's what happens behind the scenes:

- For every architectural decision

answer: Why this and not the obvious alternative?

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

- 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

2. Impact Assessment: For each change

determine:

Identify what's new

what changed

Update/Sync Prompt

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

- 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

- Named presets table (name

duration

- Rules: when to animate

when not to

- Type scale table (name

size

- Full palette with swatches description (name

hex

Each token entry: name

value

- Project name

description

Markdown

structured with headers per section. This will be directly

patterns (import paths

className conventions

- Maximum instances per viewport (e.g.

only 1 primary CTA per section)

- Size variants with exact token values (padding

font-size