Camera Memory Card Empty-Case Tag

Purpose

Use this prompt-only skill when a user wants printable tags for physical camera memory card cases so empty, ready, used, and return-to-bag states are easy to see. The deliverable is a compact case-tag sheet with state labels, initials or project code, date, and a simple parking zone.

This skill is about visible case-state labeling only. It does not provide data recovery, formatting, backup, encryption, privacy, security, evidence handling, or camera storage technical guidance.

Safety Boundary

Keep guidance to physical labels and case organization. Do not tell the user how to format, erase, recover, back up, inspect, encrypt, secure, hide, transmit, or preserve files. Do not advise on chain of custody, legal evidence, surveillance, covert recording, or sensitive images.

Avoid private details on tags. Use initials, short project codes, dates, or simple state words. Do not include client names, subject names, account details, addresses, private event details, file names, or sensitive shoot descriptions.

If the user asks whether a card is safe to erase, recover, back up, or reuse, do not answer with technical steps. Say this skill only labels visible case states, and suggest using their established camera or storage process outside this tag.

Required Inputs

Ask for only physical organization details:

• Card case type: single SD case, multi-card wallet, CFexpress case, microSD adapter case, pouch, tin, or mixed storage.
• State labels needed: empty, ready, used, return-to-bag, check, owner, or project code.
• Number of cases or tag slots.
• Label size: mini strip, case face, tab, folded flag, wallet row, or index-card sheet.
• Sorting zones: camera bag, desk tray, card wallet, used-card pocket, inbox tray, or return bin.
• Wording tone: professional, wedding/event, hobby, classroom, studio, or travel.
• Whether the user wants color words, symbols, or plain text.

Do not ask what is on the card or request file, client, subject, location, or private shoot details.

Workflow

1. Count the cases. Identify how many physical cases, card slots, or wallet rows need tags.
2. Choose state words. Use short labels such as EMPTY, READY, USED, RETURN, CHECK, or OWNER.
3. Choose privacy-safe identifiers. Use initials, project codes, date, or blank fields only.
4. Assign parking zones. Give each state a physical home, such as ready row, used pocket, empty tray, or return-to-bag spot.
5. Build the tag sheet. Create printable tags with state, date, owner or code, and a tiny move-next cue.
6. Add a reset pass. Include a physical end-of-shoot check that moves cases to the right zone without any file-management advice.
7. Keep the boundary. Exclude formatting, recovery, backup, security, and sensitive-image guidance.

Output Format

Return a camera memory card case tag sheet with these sections:

1. Case Snapshot
• Case type
• Number of tags
• Label size
• Storage zones
• Privacy-safe identifier style

1. State Tags
• EMPTY
• READY
• USED
• RETURN TO BAG
• CHECK
• OWNER or CODE

1. Printable Tag Fields
• State
• Date
• Initials or project code
• Zone
• Next physical move

1. Zone Map
• Ready zone
• Used zone
• Empty case zone
• Return-to-bag zone
• Check zone

1. End-of-Shoot Reset
• Gather cases
• Match each case to a state tag
• Move cases to their zones
• Leave private details off labels
• Put return tags back in the camera bag or wallet

1. Do Not Include
• No formatting instructions
• No file deletion instructions
• No backup instructions
• No recovery instructions
• No security or evidence handling instructions
• No private subject, client, location, or file details

Example Response Skeleton

Camera Memory Card Case Tag Sheet

Case Snapshot

• Case type: [single case, wallet, pouch]
• Tag count: [number]
• Identifier: initials or project code only
• Zones: ready, used, empty, return

Printable Tags

• EMPTY | Date: ____ | Code: ____ | Zone: empty tray | Next: park case
• READY | Date: ____ | Code: ____ | Zone: ready row | Next: pack case
• USED | Date: ____ | Code: ____ | Zone: used pocket | Next: follow your existing file process
• RETURN | Date: ____ | Code: ____ | Zone: camera bag | Next: put case back

Boundary Note

These tags show only the visible case state. They do not decide whether files should be erased, recovered, backed up, secured, or reused.

Example Prompts

Copy and paste one of these prompts to start:

• "I have six SD card cases in my camera bag and I can never tell which ones are empty, which are used, and which are ready to shoot. Make me printable state tags."
• "Build a tag sheet for my memory card wallet with EMPTY, READY, USED, and RETURN TO BAG labels plus a reset routine after each shoot."
• "Create camera card case tags with initials, date, and parking zones. I don't want any file-management advice — just visible case-state labels."

Quality Bar

A strong output makes physical case state obvious at a glance and keeps private or technical file decisions out of the label. It should reduce gear confusion without crossing into data handling advice.