marketing-art-direction
Skill1 starsChanged 4 days agoMITView on GitHub
Define or refine marketing-site visual direction and translate it into implementable composition, typography, surface, narrative and responsive rules. Use for direction specifications or critique of a selected direction, not automatic redesigns or general dashboard UI.
In this repository21 other files it gives its agents.
- animation-vocabularySkill
- apple-chartsSkill
- apple-hig-componentsSkill
- apple-hig-foundationsSkill
- apple-hig-getting-startedSkill
- apple-hig-inputsSkill
- apple-hig-patternsSkill
- apple-hig-technologiesSkill
- apple-sheetsSkill
- batch-commitSkill
- fluid-interface-designSkill
- git-change-controlSkill
- improve-animationsSkill
- marketing-product-mediaSkill
- marketing-reference-forensicsSkill
- marketing-visual-qaSkill
- message-delivery-integritySkill
- production-verificationSkill
- product-marketing-personasSkill
- security-auditSkill
- systems-builder-writingSkill
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
- Distinctive: line 10
Create a product-specific visual language with engineering consequences.
- Distinctive: line 12
Read composition and type, material language and narrative decisions.
≈ “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.
Files
Marketing Art Direction
For suite navigation, read navigation systems and specify expanded states, destinations and phone behaviour—not only header labels.
Create a product-specific visual language with engineering consequences. Preserve the selected direction, brand and approved claims. Review or research does not authorize implementation.
Read composition and type, material language and narrative decisions. Use actual rendered reference evidence, not brand stereotypes. The material contract is mandatory, not a final decorative layer.
For a specification request, deliver a direction contract: intended perception, central visual mechanism, hierarchy, density, type roles, media jobs, surfaces, motion purpose, responsive recomposition and observable acceptance conditions. For a critique, evaluate the existing contract and propose only the refinements needed; do not require a new direction document automatically.
A palette, font pair and rounded card system are insufficient. Explain why each focal object exists, how it connects to the next chapter and what can be understood without reading every sentence. Compare equal viewport sizes and equivalent section jobs.
Make the design decisions: recommend a specific surface system and section presentation formats with reasons and rejected alternatives. Do not ask the user to choose a gallery, loop or scroll effect merely because several are possible. Ask only for missing authority, facts or genuinely consequential preference.
Do not convert generic anti-AI advice into bans on the user's preferred colours or serif type. Test whether each choice is doing meaningful work. Proposition, composition, material execution and media truth are separate acceptance gates; strength in one cannot compensate for failure in another. Refine those before micro-spacing.
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
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.

