user-thoughts.SKILL

Overview

Across sessions and across agents, project decisions and user constraints are easy to lose. user-thoughts persists those decisions into a project-local mdbase so any future agent can recover the user's intent without re-deriving it from scratch.

Persistence needs the user’s explicit memory/capture authorization; discussing architecture or a preference alone does not authorize cross-session storage. Existing opt-in scope persists, but a file flag is not a substitute for user authorization.

The skill records user intent. It does not replace normal task execution. If the user says, "make the button red," the agent should both make the change and record the preference when persistent project memory is useful.

When to Use

Use this skill when the user states or revises:

• Project rules, constraints, preferences, or requirements.
• Architecture, tech-stack, data-model, deployment, or workflow decisions.
• UI/UX direction, copy standards, visual preferences, or design rationale.
• Backlog items, planned work, rejected options, or decisions that future agents should inherit.
• A direct command beginning with /user-thoughts or /ustht.