majiayu000/spellbook / skills/illustrated-gallery
illustrated-gallery
VerifiedArt-direct complete illustrated websites and write project-specific image-generation prompts. Use when the user requests Illustrated Gallery, a gallery-inspired visual style, or $illustrated-gallery. Covers visual direction, original artwork, and page-wide composition; not a fixed website clone, standalone image task, or generic dashboard skill.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.2 KB |
| agents/openai.yaml | config | 350 B |
| references/art-direction.md | markdown | 3.2 KB |
references/art-direction.md
View on GitHub# Directions for original illustrated websites
Use these examples to explore a suitable direction, not to select a rigid theme.
Mix qualities when useful. Keep each project's actual subject and user task in view.
No direction requires a specific image, image count, palette, or animation.
| Direction | Visual language | Possible subjects | Page composition |
| --- | --- | --- | --- |
| Editorial field notes | Warm paper, ink, one strong accent; serif display type with clear sans-serif body | Maps, objects, spatial metaphors tied to the topic | An illustrated opening, numbered features, marginal labels, dense readable index |
| Material laboratory | Charcoal or chalk, ceramic, glass, metal; controlled studio light | Routing tracks, calibration instruments, modular assemblies | Split image and copy, process studies, compact resource rows, contrasting reading area |
| Graphic print studio | Flat shapes, limited bold colors, halftone or cut-paper texture | Symbols and scenes derived from the product's purpose | Asymmetric posters, generous labels, modular sections, clear navigation |
| Quiet photographic archive | Natural light, restrained color, documentary textures | Actual user assets or clearly conceptual still-life scenes | Image-led chapters, small captions, wide whitespace, restrained typography |
| Computational exhibition | Monochrome with a selective accent, precise line work, measured rhythm | Spatial networks, fields, topology, meaningful abstract structures | Large diagrams or artwork, compact annotations, structured reading and discovery sections |
| Expressive illustrated journal | Ink, gouache, pencil, or mixed-media marks with human texture | Project-specific stories, places, objects, or processes | Varied image scales, editorial columns, chapter dividers, legible supporting text |
## Turning a direction into prompts
Begin with the section's role. For a routing library, an architectural branching
track could express choices; for an archive, a layered collection of objects may
express discovery. Those are examples of reasoning, not reusable default subjects.
Select a medium and consistent material or color relationships. Specify where
copy will sit, which detail must remain visible on mobile, and what the image must
not imply. Keep actual labels and controls in HTML. Use the available generation
tool, inspect its output, and revise the prompt based on what the image needs.
Avoid superficial variations: the same image recolored into several palettes is
not several visual directions. A direction should change composition, texture,
type relationships, and the way the content is organized, not merely hue.
## Extending the direction below the hero
- Discovery pages: group entry points by use case, distinguish selected material
from the full index, and keep search, category state, and empty results clear.
- Learning pages: use chapter rhythm, annotated illustrations, and readable steps.
- Portfolios: vary work-image scale and connect each image to a real project.
- Product pages: show the workflow and useful evidence without fabricated metrics.
Create enough visual variation to guide reading without making every section a
new theme. Art direction must improve the main content, not displace it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |