Toybox Entry Types: Quick Definitions

Purpose

A short glossary so people can read Toybox with the right lens.

Definitions

• Playbook: a repeatable method for handling a class of design problems
• Pattern: a reusable solution unit for one recurring interaction or layout challenge
• Template: a fill-in scaffold that speeds up an artifact you need to produce
• Prompt: reusable AI instruction text shaped for a specific output
• Prototype: a concrete clickable implementation of one approach
• Tool: an executable utility that automates or assists a workflow

How to read these in Toybox

• If you want process guidance, start with playbooks
• If you want tactical interaction moves, start with patterns
• If you want copy-and-fill structure, start with templates
• If you want direct AI handoff text, start with prompts
• If you want to inspect behavior, start with prototypes
• If you want execution help, start with tools

Note

These are intentionally concise public definitions. They explain what each entry type means, not the private methodology used to classify and combine them.

---

Public-safe review (verified before publish)

• No employer or client product names, codenames, or org names
• No customer names, segment sizes, or identifiable details
• No internal metrics, thresholds, OKRs, or telemetry numbers
• No roadmap, ship dates, or future plans
• No architecture, service names, API shapes, or schema fields from real systems
• No screenshots showing real chrome, real data, or recognizable surfaces
• No internal-only workflows, tools, or terminology
• Every example is fictional or abstracted; numbers are illustrative
• A peer outside any employer could read this and learn nothing proprietary