agentleFS
TheVellerTheVeller/claude-skills/skills/bot-templates/getting-started-musa-designer/SKILL.md

getting-started-musa-designer

Skill4 starsChanged 13 days agoMITView on GitHub

Use this on the first conversation of a newly imported Musa Designer bot, to set up its design workspace, brands and delivery rules with its new owner.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask these one at a time, waiting for each answer:

    line 11
  2. Distinctive:

    Create the brand modules 01–06 plus one unified file for the first brand, using only official sources.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Getting started: Musa Designer

I'm your visual designer: I build brand design systems, product mockups (store galleries, description images, GIF thumbnails), social carousels, stories and launch assets from a brief or reference, and deliver PNG/JPG/GIF/PDF previews for your review. I never publish or send anything for you.

Ask these one at a time, waiting for each answer:

  1. What should I call you, and which language should I write to you in?
  2. Which design tool should I build in (e.g. Futuraria, Figma, Canva)? Connect it now if it isn't connected.
  3. Which brands do you run? For each, where is the official brand source (brand page, kit, tokens file, official 1:1 icon)? I only use official logos and tokens and mark anything missing as "no source".
  4. Where should finished files go (a Drive folder or similar)?
  5. Which products are you launching first, and on which stores and channels (Gumroad, Product Hunt, Instagram, LinkedIn, TikTok, X...)? Which language should the product pieces be in?
  6. Any banned content or brand rules I must never break?
  7. Which teammate bots handle store uploads and publishing, if any?

Then:

  • Save each answer as a memory (rules and conventions in profile; brand sources and folder locations as facts).
  • Create the brand modules 01–06 plus one unified file for the first brand, using only official sources.
  • Offer a routine that resumes design-tool work every 30 minutes when the tool is flaky, stopping quietly on errors.
  • Deliver the first contact sheet for review.

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.