agentleFS
Sign inStart free
jhy0285jhy0285/monofield/skills/creative-director/SKILL.md

creative-director

Skill6 starsChanged 5 months agoApache-2.0View on GitHub

AI creative director with recursive self-assessment: 20+ methodologies (SIT, TRIZ, Bisociation, SCAMPER, Synectics), 3-axis evaluation calibrated against Cannes/D&AD/HumanKind, 5-phase process from brief to presentation.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    When this skill is invoked inside MonoField, treat it as the design-flow director, not as a single polish checklist.

    line 27
  2. Very specific:

    Search across every available MonoField resource, not only this skill: skills, plugins, MCP servers and templates, connected connectors, …

    line 36
  3. Distinctive:

    When the design target or aesthetic bar is ambiguous, present a small guided UI-style choice set or form with a recommended default.

    line 43
  4. Distinctive:

    If the best resource is not configured yet, explain why it is needed and guide setup.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 11 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

creative-director

Curated from @smixs.

What it does

AI creative director with recursive self-assessment: 20+ methodologies (SIT, TRIZ, Bisociation, SCAMPER, Synectics), 3-axis evaluation calibrated against Cannes/D&AD/HumanKind, 5-phase process from brief to presentation.

MonoField orchestration mode

When this skill is invoked inside MonoField, treat it as the design-flow director, not as a single polish checklist.

  1. Define what "good-looking" means before changing pixels: audience, product goal, brand posture, style references, information density, typography, palette, motion tone, asset needs, and explicit anti-patterns such as generic AI gradients, empty cards, vague copy, and template symmetry.
  2. Inspect the current target: HTML/page element, browser tab, design file, active design system, attached image, or project folder.
  3. Search across every available MonoField resource, not only this skill: skills, plugins, MCP servers and templates, connected connectors, design files, active browser/context, and user-provided assets.
  4. Match resources into a staged workflow. Typical lanes are critique, style-direction selection, visual asset generation, motion, data/proof grounding, implementation polish, responsive/accessibility hardening, and final verification.
  5. When the design target or aesthetic bar is ambiguous, present a small guided UI-style choice set or form with a recommended default. Continue the workflow after the choice instead of stopping at a generic question.
  6. If the best resource is not configured yet, explain why it is needed and guide setup; otherwise use the closest configured alternative and mark the tradeoff.

Source

How to use

This catalogue entry advertises the skill in MonoField so the agent discovers it during planning. To run the full upstream workflow with its original assets, scripts, and references, install the upstream bundle into your active agent's skills directory:

# Inspect the upstream README for exact paths
open https://github.com/smixs/creative-director-skill

Then ask the agent to invoke this skill by name (creative-director) or with one of the trigger phrases listed in this skill's frontmatter.

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.

Reviews can't be read right now.

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.

Check your setup, free