agentleFS
XakkiXakki/ai-agents-skills/skills/design-brand-build/SKILL.md

design-brand-build

Skill6 starsChanged 3 months agoMITView on GitHub

Develop or review a brand identity, name, guidelines or approved visual asset family. Use for brand systems, naming and asset adaptation. RU: бренд, логотип, фирменный стиль.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Use the actual project/runtime interfaces for conversion, review and output.

    line 17

≈ “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

Brand identity

Use for developing or refining a brand system, assessing a brand guideline, selecting a name, or adapting approved brand assets. Determine which task is requested, the audience, intended applications, supplied references, constraints and decision authority. Distinguish known business facts from proposed strategy; do not invent claims, affiliations, provenance or an owner's approval.

For iterative work, present meaningfully distinct directions when useful, review each at its intended size and context, and record exactly what the owner chooses before assuming a direction is approved. Preserve approved source assets and unrelated work. Do not publish, send, replace a canonical asset or update a live surface without authority for that exact action.

  • For naming, including candidate screening, read naming.
  • For adaptations, exports and source-to-distribution integrity, read asset production.
  • For a guideline review or authorized publication, read review and publication.

Use the actual project/runtime interfaces for conversion, review and output; do not assume a specific agent, converter, visual style, deployment target or artifact format. Report the checks actually performed and any limitations.

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.