reference-synthesis
Skill4 starsChanged 3 months agoMITView on GitHub
Combine multiple inspiration sources into an original product-specific direction using a reference matrix, required transformations, AIgent pattern mapping, and an influence ledger.
In this repository26 other files it gives its agents.
- aigentSkill
- aigent-3d-scroll-systemSkill
- aigent-asset-gallery-systemSkill
- aigent-business-sitesSkill
- aigent-designSkill
- aigent-landing-page-polishSkill
- asset-provenance-auditSkill
- cinematic-asset-gallerySkill
- cinematic-site-qaSkill
- cinematic-studioSkill
- cinematic-web-directorSkill
- creative-asset-directorSkill
- design-forensicsSkill
- design-resolverSkill
- gsap-scroll-choreographySkill
- hyperframes-videoSkill
- inspiration-originality-auditSkill
- modular-scroll-pageSkill
- publish-siteSkill
- remotion-web-assetsSkill
- spline-web-sceneSkill
- threejs-web-sceneSkill
- video-asset-pipelineSkill
- video-scrub-deckSkill
- visual-design-criticSkill
- web-3d-asset-pipelineSkill
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
- Distinctive: line 8
Use this after Design DNA exists for two or more references.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Reference Synthesis
Use this after Design DNA exists for two or more references.
Principle
One source may influence one or two design dimensions. It must not silently determine the whole site.
Dimensions:
structure
typography
material
motion
interaction
mediaCommand
node scripts/inspire.mjs compose \
--brief design-intelligence/example-brief.json \
--refs source-a,source-b,source-cOverride an assignment only when the user has a clear reason:
--assign structure:source-a,typography:source-b,motion:source-cRequired synthesis
For each dimension, record:
- source
- extracted principle
- required transformation
- excluded source expression
- target-product reason
Then map the result to the smallest existing AIgent systems and runtimes.
Do not copy
- source copy, claims, logos, marks, icons, photographs, video, 3D models, or audio
- exact section order
- exact typography pairing and scale
- exact animation timing, keyframes, camera path, or transition sequence
- source HTML, CSS, JavaScript, shaders, or private implementation
Completion
Before implementation, produce:
reference-matrix.jsoninfluence-ledger.jsonDIRECTION.md- mapped AIgent patterns
- original asset briefs
- mobile and reduced-motion transformations
- originality-audit threshold
The design should feel intentionally informed by several references and unmistakably authored for the target product.
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.

