Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Packaging Designer

ASecurity

Design product packaging with shelf impact, structural basics, regulatory requirements, and dielines.

2 stars
0 votes
7 copies
42 views
Added 9/29/2026
ai-agentsrustgoaws

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill packaging-designer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Packaging Designer?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Packaging Designer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-packaging-designer/badge)](https://www.skillsdirectory.com/skills/aicodedecode-packaging-designer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: packaging-designer
description: Design product packaging with shelf impact, structural basics, regulatory requirements, and dielines.
category: creative-design
---

## Overview

Packaging is a salesperson, a billboard, and a legal document in one — it has
about 3 seconds to win
attention on a shelf or thumbnail, then must communicate clearly, comply with
regulations, and
survive shipping. This skill covers packaging design from shelf strategy and
structural basics
through labeling requirements to print-ready dielines.

## When to use

- Designing packaging for a new product

- Redesigning existing packaging for shelf impact

- Understanding dielines, bleeds, and structural design

- Navigating labeling regulations (nutrition, warnings, claims)

- Preparing packaging files for printers

## Core concepts

- - - **The 3-second shelf test.** At 10 feet (or as a thumbnail), only three
  things register: brand
  block, product identity, and variant. Design the "billboard" layer first;
details are for the
  hand.
- - - **Hierarchy of the pack.** Brand → product name → variant/flavor → key
  benefit → supporting
  claims → legal. Each layer serves a different distance: shelf, arm's length,
in-hand reading.
- - - **Structure affects design.** Box, pouch, bottle, tube — each has panels,
  seams, and viewing
  angles that constrain the design. Get the dieline early; design to the
structure, not onto it.
- - - **Claims and compliance.** "Organic," "natural," nutritional panels,
  allergen warnings, net
  weight placement — regulated differently by category and country.
Non-compliant packaging gets
  pulled from shelves; verify with legal, not just the designer.
- - - **Unboxing is marketing.** The opening experience (tissue, inserts,
  messaging inside the lid)
  turns customers into photographers. Design the inside, not just the outside.
- - - **Sustainability signals.** Material choices and recyclability messaging
  increasingly drive
  purchase. Design honestly — greenwashing destroys trust faster than no claim
at all.

## Practical workflow

1. 1. 1. **Define the shelf context.** Where does it sell (grocery shelf,
   boutique, Amazon thumbnail)?
   Who are the neighbors? What's the category's visual language — and how will
you stand out within
   it?
2. 2. 2. **Get the structure.** Obtain or create the dieline: dimensions,
   panels, glue flaps, folds.
   Mock it up physically (even in paper) — flat designs lie about 3D reality.
3. 3. 3. **Design the billboard layer.** Brand block, product name, variant
   differentiation
   (color-coding system for flavors/sizes). Test at thumbnail size and from 10
feet.
4. 4. 4. **Build the information layers.** Benefits, claims, usage,
   ingredients/nutrition, legal — in
   reading order. Keep the front clean; relegate detail to side/back panels.
5. 5. 5. **Handle compliance.** Required panels, font minimums for legal text,
   allergen and warning
   placement, barcode quiet zones, net quantity rules. Check category-specific
regulations for your
   markets.
6. 6. 6. **Prototype physically.** Print at 100%, cut, fold, and assemble.
   Check: does it stand? Do
   panels align? Is text readable at arm's length? Does the variant read from
across the room?
7. 7. 7. **Prepare printer files.** CMYK, correct dieline on a separate layer,
   3mm+ bleed, outlined
   fonts, spot colors/foils/varnishes specified, barcode as vector. Get a
physical proof before the
   full run.

## Common pitfalls

- - - **Designing flat.** Beautiful flat artwork that fails on the 3D structure
  — text wrapping into
  folds, key art on the glue flap. Always mock up.
- - - **Front-panel clutter.** Trying to say everything on the front. The front
  sells; the back
  informs. Ruthless prioritization.
- - - **Variant confusion.** Flavors/sizes that look identical at a glance cause
  mispicks and returns.
  Variant differentiation must survive the 3-second test.
- - - **Non-compliant claims.** Marketing claims the legal team hasn't cleared.
  "Clinically proven"
  without proof is a lawsuit, not a selling point.
- - - **Unreadable legal text.** Tiny, low-contrast mandatory text that fails
  regulations. Know the
  minimum sizes; they're not suggestions.
- - - **Ignoring the thumbnail.** E-commerce packaging lives as a 200px image.
  If the design only
  works at full size, it's designed for a world that no longer exists.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →