agentleFS
timscheueraitimscheuerai/gtm-architecture-template/.agents/skills/brand-review/SKILL.md

brand-review

Skill2 starsChanged 2 months agoMITView on GitHub

Review a rendered graphic or visual system for message clarity, identity consistency and export quality; make fixes when requested.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read brand/BRAND.md, the asset brief and only the supporting context needed to assess the work.

    line 11

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

Workspace: all context paths below (identity, audience, strategy, voice, brand, raw, output, index, log, workspace preferences and context scripts) resolve from context/ in the kit root. Read both the root AGENTS.md and context/AGENTS.md. Skill-local references/ and flowchart scripts/ resolve from this skill directory.

Review the visual

Read brand/BRAND.md, the asset brief and only the supporting context needed to assess the work. If the brand guide is blank, review clarity and execution; do not invent brand-compliance failures.

Inspect the actual rendered artifact at the intended size and a small viewing size. With only a screenshot, distinguish visible findings from checks requiring editable source.

Assess:

  • Meaning: the takeaway, reading order, truthful relationships and evidence.
  • Identity: consistency with approved rules, where rules exist.
  • Craft: text size, line breaks, alignment, spacing, contrast, clipping and connector collisions.
  • Delivery: dimensions, loaded fonts, linked assets and editable/export files when supplied.

Give the few highest-impact findings with a location, effect on the reader and concrete correction. Separate functional defects, conflicts with adopted rules and subjective preferences. Avoid numerical quality scores without a defined rubric.

Review is report-only unless fixes were requested. For fixes, stay within the asset's scope, preserve user edits, rerender and inspect the result. Reviewing a single asset does not authorize global brand changes, Notion edits or publication.

Lead with the assessment and state inspection limits.

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.