gracefullight/pkgs / .agents/skills/oma-design
oma-design
UnverifiedDefine or review a visual system, DESIGN.md, or redesign direction. Use for typography, layout, color, motion, and interaction design decisions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.1 KB |
| examples/design-context-example.md | markdown | 2.3 KB |
| examples/landing-page-prompt.md | markdown | 4.8 KB |
| reference/accessibility.md | markdown | 4.4 KB |
| reference/color-and-contrast.md | markdown | 3.7 KB |
| reference/component-patterns.md | markdown | 5.7 KB |
| reference/motion-design.md | markdown | 7.9 KB |
| reference/responsive-design.md | markdown | 3.6 KB |
| reference/shader-and-3d.md | markdown | 5.0 KB |
| reference/spatial-design.md | markdown | 2.8 KB |
| reference/typography.md | markdown | 2.6 KB |
| reference/visual-hierarchy.md | markdown | 9.6 KB |
| resources/anti-patterns.md | markdown | 8.4 KB |
| resources/asset-strategy.md | markdown | 3.0 KB |
| resources/checklist.md | markdown | 5.6 KB |
| resources/design-md-spec.md | markdown | 8.3 KB |
| resources/design-tokens.md | markdown | 3.9 KB |
| resources/error-playbook.md | markdown | 3.9 KB |
| resources/execution-protocol.md | markdown | 14.5 KB |
| resources/getdesign-fetcher.md | markdown | 13.2 KB |
| resources/prompt-enhancement.md | markdown | 9.2 KB |
| resources/redesign-protocol.md | markdown | 3.7 KB |
| resources/stitch-integration.md | markdown | 3.8 KB |
resources/asset-strategy.md
View on GitHub# Asset Strategy: Images, Logos, and Visual Material
Landing pages and portfolios are visual products. A text-only page with
fake-screenshot divs is slop, not minimalism. Even a restrained editorial
page needs at least 2-3 real images (hero, one product/lifestyle shot,
one supporting image).
## Source Priority (in order)
1. **Image generation first.** If an image-generation path is available,
use it — in the oma ecosystem, route to the `oma-image` skill
(Codex gpt-image-2 / nano-banana / Pollinations). Generate
section-specific assets at the right aspect ratio: hero photography,
product shots, texture backgrounds, mood images. Do not skip this
because hand-rolled CSS feels faster.
2. **Real web images second.** When no generation tool is available:
- `https://picsum.photos/seed/{descriptive-seed}/{w}/{h}` for
placeholder photography. The seed should describe the section
(e.g. `oma-cookware-kitchen`), not be random.
- Actual stock or brand URLs when the brief provides them.
- Open-license sources (Unsplash direct URL, Pexels) if explicitly allowed.
Never emit guessed/unverified Unsplash URLs — they break.
3. **Last resort: tell the user.** Do NOT fill the page with hand-rolled
SVG illustrations or div-based fake screenshots. Leave clearly labeled
placeholder slots (`<!-- TODO: hero product photo, 1600x1200 -->`) and
report at the end: "This page needs real images at: [placements]."
## Logo Walls ("Trusted by" / "Used by")
- Use real SVG logos, never plain text wordmarks styled in a row:
- **Simple Icons**: `https://cdn.simpleicons.org/{slug}/{hex}` or the
`simple-icons` npm package (most known brands)
- **devicon** for tech-stack logos
- Invented brand name → invented mark: generate a simple monogram
(one letter in a circle, two-letter ligature, abstract glyph) as inline
`<svg>` matching the page style.
- Logos must render in both light and dark mode (single-color theme
variable, or white-on-dark / black-on-light variants).
- **Logo-only rule**: a logo wall is logos and nothing else. No industry
or category labels under each logo. Brand name goes in alt text.
- The logo wall lives in its own section directly BELOW the hero,
never inside the hero.
## Product Previews
Div-based fake screenshots are banned: no fake task lists, fake dashboards,
or fake terminal windows built from styled `<div>` rectangles. If you need
to show a product:
- Use a real screenshot URL if one exists
- Generate one via the image tool
- Use a real component preview (an actual mini-version of the UI on the page)
- Or skip the preview and use editorial photography
A hero of "text + gradient blob" is a placeholder, not a hero.
## Hand-Rolled SVG
- Icons: always from a library (see component guidance); never draw icon
paths from scratch. One icon family per project, standardized strokeWidth.
- Decorative illustrations: strongly discouraged as default. Acceptable only
when the brief explicitly asks, the mark is a single simple geometric
shape, and quality is assured.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |