
Personal Memory System
Use to design a Markdown personal memory system: capture→distill→retrieve, templates, weekly review, and privacy redaction.
Find prompts, then open a guide if you need the workflow behind them.
14 prompts for “system”

Use to design a Markdown personal memory system: capture→distill→retrieve, templates, weekly review, and privacy redaction.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Start a beginner design.md: principles, tokens, and component notes — system-doc literacy so teams share one source of truth.
Start a design.md for a small project: tokens, components, and do/don't notes — documentation literacy for agents and humans.
Build a beginner design-handoff checklist so engineers get sizes, states, assets, and open questions without tool automation.
Turn a rough product idea into a one-page beginner PRD: problem, users, scope, and non-goals.

Build a personal plant care system with watering schedules, care logs, and seasonal reminders.

You are a skill author. Turn a messy workflow into a reusable system skill another agent can run without asking follow-up questions.When to use- The user wants a repeatable work instruction, not a one-off answer.- The task will be run again with different inputs.Steps1. Name the skill in verb-object form.2. Write a one-sentence job statement: what it does and for whom.3. Define the trigger: when an agent should pick this skill.4. List typed Inputs: name, type, required/optional, and an example value.5. List Outputs: exact artifacts and their format.6. Write the Steps as an ordered, deterministic chain; add at least one worked Example with a short input and the expected output.7. Add Constraints: what the agent must never do (ask for missing required inputs instead of guessing; do not invent sources).Output format (markdown)# <Skill name>One-sentence job.## When to use- ...## Inputs- name (type, required|optional) - example## Outputs- ...## Steps1. ...## Examples### Input...### Output...## Constraints- ...

Expand empty, loading, and error UI states into a beginner card — product literacy so screens do not die on happy-path only.
Create a design↔eng handoff card: specs, states, and open questions — beginner literacy for smoother handoffs.
Turn a fuzzy agent request into a beginner task brief: goal, tools allowed, stop conditions, and acceptance checks.
Check a personal page or form for everyday accessibility basics — contrast, labels, and plain language.
Showing 12 of 14
Scroll for more
Skills are not one-shot prompts — they are reusable instruction packages (trigger, input, output) for writing, research, and coding.
A practical three-layer system for Midjourney, Flux, and Grok Imagine so revisions stay controllable.