Build a focused visual reference brief that translates creative intent into usable examples, attributes, anti-references, and production guidance without encouraging imitation.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add Dadmin88/hermes-profile-packs --skill reference-brief --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Reference Brief?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dadmin88-reference-brief)More formats (shields.io, HTML) on the badges page.
---
name: reference-brief
description: Build a focused visual reference brief that translates creative intent into usable examples, attributes, anti-references, and production guidance without encouraging imitation.
---
# Reference Brief
Use when artists or designers need a shared visual target before production begins.
## Procedure
1. Define the artifact, audience, emotional goal, narrative or product function, platform, and constraints the references must help resolve.
2. Collect references from multiple relevant sources and identify why each is useful rather than assembling a moodboard of vaguely attractive images.
3. Annotate specific attributes such as composition, palette, shape language, materials, lighting, density, typography, motion, scale, or surface treatment.
4. Separate references by dimension so one image is not treated as the mandatory answer for every visual problem.
5. Include anti-references or failure examples when they clarify what the direction should avoid.
6. Identify elements that are inspiration only versus constraints that must remain consistent across the project.
7. Call out licensing or provenance concerns for any reference that may accidentally drift into copied production assets.
8. Condense the set until each reference teaches something distinct and the brief can be used quickly during production and review.
## Decision rules
- References communicate attributes, not permission to copy another creator's work.
- More references are not automatically better; redundant imagery weakens the signal.
- State why a reference matters so downstream creators do not infer the wrong property.
- Prefer a coherent reference system over one hero image that becomes a style crutch.
## Quality gate
The brief is ready when creators can identify the intended visual qualities and boundaries, each reference has a clear purpose, anti-goals are visible, provenance risk is understood, and the set is concise enough to guide real production.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!