agentleFS
juju-wjuju-w/card-creator-skill/skills/card-creator/SKILL.md

card-creator

Skill11 starsChanged 26 days agoMITView on GitHub

Create or edit AirCard, bank-card and transit-card artwork from a short brief or reference image. Use image generation, choose suitable marks when unspecified, and preserve the rest during targeted edits.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. jexchan/dailyup-second-brain-starter★ 33same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

Files
SKILL.md

Card Creator

“Magikarp × ICOCA, simple, ICOCA at lower right” is enough. Use the host's image-generation or image-editing tool for the complete card, including logos. Never draw artwork with code or paste logos onto a generated background. If the tool is unavailable, explain the limitation; do not substitute a script or claim an image was created.

  1. Read the short card rules. For a new card, generate directly when the subject and style are clear. For a targeted edit, use the current image and change only what was requested; preserve other characters, composition, text and brand choices. Ask for the original only if it is needed and absent from the conversation.
  2. Follow explicit logo choices, including “no logo.” Otherwise choose one familiar mark suited to the card type, subject, region and style. Respect requested bank/network combinations or logo-heavy designs without a count cap. Preserve brands in the user's reference unless asked to replace them. Distinguish transit products from operators; geographic relevance alone is not enough.
  3. Prefer user attachments. If a mark needs a reference, find its name or alias in the picture index and open only the matching picture(s). Use available local pictures; if remote pictures cannot be reached, use a user reference or confident model knowledge. Search only when requested or identification is genuinely uncertain; ask for a reference if uncertainty remains. Do not scan the library, repeatedly retry downloads or read source histories.
  4. Match logos to the artwork: foil, monochrome and line art are welcome. Use familiar card-face variants (usually compact UnionPay), not compact versions of every brand. Balance size and spacing visually, without fixed logo boxes.
  5. Inspect the result for recognizable subjects and marks, obvious hand errors, unintended borders and transparency. For a clear mistake, make one targeted correction, then disclose any remaining issue instead of looping. Return the image with only useful brief notes, not a process report.

Wallet screenshots reference only the card, not the surrounding UI. Allow text intrinsic to the chosen marks; otherwise omit unrequested text, numbers, chips, QR codes and contactless/NFC indicators. Label third-party marks as non-official artistic interpretations, never authorization, endorsement or functioning cards. Do not publish private references without permission.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.