OpenParable
Skip to content
← Back to skills

Maggie Design

Design
maggie-design

Maggie Design is an Agent Skill for design published in the MaggieAppleton/maggieappleton.com-V3 repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Maggie's personal design philosophy — minimalist, progressive, and dynamic. Use when designing or reviewing UI components, pages, or interactions to keep the interface spare, let users learn by doing, and favour live, animated, progressively-disclosed components over labelled and static ones.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/MaggieAppleton/maggieappleton.com-V3/blob/HEAD/.claude/skills/design-and-ui/maggie-design/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/maggie-design, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Maggie Design

My personal design philosophy. The core is: minimalist, progressive, and dynamic. Interfaces should feel spare, teach through interaction, and behave like live, responsive widgets rather than static documents.

Strip the labels

  • No unnecessary labels or instructional text. Avoid "click here", "touch here", and similar hints. Users learn by interacting, not by reading on-page instructions.
  • Avoid redundant labels. A calendar component shouldn't have a visible "Calendar" label. When in doubt, omit the label.
  • Prefer tooltips for secondary labels or guidance. Use an icon or compact control with a tooltip instead of adding more text directly on the page.
  • Use labeled buttons only when necessary. Otherwise minimise text to reduce visual clutter.

Progressive disclosure

  • Start with a minimal amount of information on the page, and reveal more as users interact or go deeper.
  • Components should start simple and small, then expand or reveal more details as the user interacts.

Dynamic, alive components

  • Use natural, organic animations so components can grow, shrink, and shift to accommodate additional information or changing data.
  • Aim for a fluid, live-widget feel — similar to how iOS components feel dynamic and alive.