Design Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
Map POI Icon Attribution Boundaries
POI icon sets such as Maki solve map symbols, not map data, tiles, style, basemap providers, place labels, or interaction attribution.
Map symbols are one layer of visual encoding. Agents must govern icon set, sprite, map style, geodata, tile provider, legend, and accessible labels separately instead of treating icon license as map license.95%Resource Licensingfigma / licenseFigma Community License Intake
Figma Community is not one open-source repository; every file, plugin, widget, paid resource, and slide template needs per-resource license and redistribution review.
An asset library cannot treat 'from Figma Community' as a license. Downloading, duplicating, commercial use, modification, redistribution, and RAG/training reference are different questions.95%Frontend Implementation3d / three.jsWeb 3D Asset Runtime Pipeline
A Three.js page is not just a canvas; 3D assets need source licensing, glTF optimization, texture compression, loading states, interaction goals, fallbacks, and verification evidence.
Web 3D combines design, assets, runtime, and performance budgets. Agents can safely generate 3D experiences only after governing model source, geometry complexity, texture format, fallback path, and accessible explanation.95%Resource Licensingavatar / placeholderDeterministic Avatar Placeholder Governance
Avatar generators such as Boring Avatars and DiceBear work well for identity placeholders, but seed, style, license, private inputs, and accessible names must be recorded; generated avatars are not real likenesses or brand assets.
The value of a deterministic avatar is stable object recognition, not real identity. It combines visual distinction, privacy, licensing, accessible labeling, and cross-project reuse boundaries.95%Resource Licensingpattern / texturePattern and Texture License Boundaries
Patterns, textures, and background generators must distinguish code license, exported-asset license, attribution, modification rights, and redistribution boundaries instead of treating free generation as unrestricted intake.
One resource can contain tool code, sample patterns, exported SVG, material files, author attribution, and platform terms. The asset library must record the actual reusable-asset layer.95%Resource Licensingbrand-logo / trademarkBrand Logo Use Boundaries
Brand logos should be used only for real brand references, integrations, payment methods, customer or partner proof, or authorized collaboration. Confirm trademark and brand guidelines, avoid implied endorsement, do not alter shape or color casually, and provide accessible names.
A brand logo is not an ordinary icon. The code license of an open-source project, aggregator, or SVG package usually does not replace trademark, brand-guideline, endorsement-context, and usage-scope judgment.95%Resource Licensingicons / licenseIcon Set License, Trademark, and Accessibility Governance
Icons are not arbitrary decoration; primary icon sets, aggregated icons, brand logos, and icon-only controls need separate license, trademark, import, and accessibility rules.
Icon governance keeps symbols visually consistent, legally reusable, screen-reader understandable, tree-shakable, and prevents brand logos from becoming free decoration or implied endorsement.95%Resource Licensingfonts / licenseWebfont License and Loading Governance
Font intake is not only visual choice; it must confirm per-font licensing, delivery method, privacy constraints, CJK size, fallback, and loading performance together.
A font is both a brand asset and a runtime dependency. Agents should recommend a font only when its license is traceable, loading surface is controlled, fallback is stable, and privacy boundary is clear.95%Resource Licensingvideo / motionStock Video Hero and Background Governance
Free stock video can make heroes feel more real, but each use must confirm item license, likeness/trademark/property rights, attribution, poster, pause control, reduced motion, and mobile performance.
Background video is not moving wallpaper. It belongs in production only when it serves first-viewport signal, brand tone, or story evidence without weakening readability, accessibility, licensing, or performance.95%Resource Licensingattribution / licenseAsset Attribution Surface Contract
License metadata should not live only in the catalog. CC BY, custom-licensed maps, photos, illustrations, Lottie files, and similar assets need readable, nearby, traceable attribution, license links, change notes, and commercial-use risk in the UI, export, or source notes.
Attribution is part of interface information architecture, not only an asset-catalog field. Any resource whose license requires credit needs a surface that users can find, reviewers can audit, and agents can trace.95%Resource Licensinggenerated-assets / provenanceGenerated Asset Provenance Record
AI-generated assets have provenance too: tool, model, prompt, source references, edit history, rights risks, and reuse boundaries must be recorded together.
An asset library cannot treat AI generated as a license or source explanation. Reuse depends on input rights, depicted subject, edit chain, verification signals, and usage context.94%Resource Licensinglicense / assetsAsset License Metadata Record
Asset-library intake must record license, commercial-use judgment, attribution needs, download method, and RAG keywords at the specific resource level, not just the platform name.
The value of an asset library is not volume. It is legal reuse, traceability, downloadability, and accurate agent retrieval. Aggregators and marketplaces especially require per-resource license decisions.93%