Skip to content

drobins25/craft / skills/creative-spark

creative-spark

Verified

This skill should be used when the user asks to "brainstorm", "explore options", "get creative", "what if we...", or selects "Let's get creative" during story or cycle creation. NOT for a bare vague feature idea where generating options would mean inventing the premise first - that routes to /craft:riff (riff first, options after). Generates 3-4 creative options with trade-offs, visual direction for UI stories, and wireframes.

references/cross-domain-patterns.md

View on GitHub
# Cross-Domain Creative Patterns

A curated collection of proven cross-pollinations - cases where software designers stole brilliantly from other domains. Use these as creative ammunition, not a recipe book. The goal is to spark unexpected connections, not to pattern-match.

Read this file when generating creative options that need non-software inspiration.

---

## From Architecture & Wayfinding

**Progressive disclosure as spatial sequence.** Architects design buildings so you discover rooms in a deliberate order - a narrow corridor opens into a grand atrium. The compression-release pattern creates emotional impact. Applied to UI: compress information density before a reveal moment. Settings screens that feel like walking through rooms, not scrolling through forms.

**Desire paths.** Architects observe where people actually walk (worn grass = desire path) and then pave those paths. Applied to UI: track where users actually click, what they skip, what they repeat - then reshape the interface around real behavior, not assumed behavior. The UI that adapts to use patterns rather than forcing a predetermined flow.

**Threshold moments.** Doorways, bridges, and gates mark transitions between spaces and prepare you emotionally for what's next. Applied to UI: transition screens, loading states, and mode switches that acknowledge the user is moving between contexts. Not just a spinner - a moment that says "you're entering something different."

## From Film & Cinematography

**Pacing and rhythm.** Films alternate tension and release, speed and slowness. A long establishing shot followed by a quick cut creates impact. Applied to UI: vary the density and tempo across a flow. A data-dense dashboard followed by a spacious detail view. A rapid onboarding sequence followed by a slow, deliberate first-use moment.

**Sound design layers.** Film uses ambient, foretelling, and stinger layers to manage awareness without breaking immersion. Applied to UI: ambient indicators (color shifts, subtle motion) for background awareness, rising visual urgency for building importance, sharp visual stingers (red flash, shake) only for genuine alerts.

**The reveal shot.** Hiding information and then revealing it creates delight. The camera pans to show something the audience didn't expect. Applied to UI: progressive reveal of features, easter eggs, or content that rewards exploration. Stats that count up. Features that appear when you need them, not before.

## From Game Design

**Juice and feedback loops.** Games make every action feel satisfying through immediate, slightly exaggerated feedback - particles, screen shake, sound, numbers flying. Applied to UI: make completions feel like achievements. A checkbox that celebrates. A progress bar that has weight and momentum. The difference between "task done" and "TASK DONE."

**Skill progression and mastery.** Games start simple and layer complexity as the player demonstrates mastery. Applied to UI: progressive feature revelation based on user behavior. Power-user features that appear after the user has demonstrated they'd use them. The UI that grows with you rather than dumping everything on day one.

**Environmental storytelling.** Games tell stories through the environment - a broken door, a flickering light, scattered papers - without explicit narration. Applied to UI: let the interface state tell the story. An empty state that feels like possibility, not absence. A busy dashboard that feels like momentum, not chaos. The UI communicates through its own visual state.

## From Editorial & Typography

**Information hierarchy through contrast.** Great editorial design creates clear reading order through size, weight, and spatial contrast - not through labels or instructions. Applied to UI: if you need a label that says "most important," the visual hierarchy has failed. Size, weight, position, and contrast should make priority self-evident.

**The editorial grid.** Newspapers and magazines use grids that create rhythm while allowing breakout moments - a photo that spans columns, a pull quote that interrupts the flow. Applied to UI: dashboards and feeds that have a regular rhythm but allow hero moments to break the grid and demand attention.

**White space as content.** In editorial, what you leave out is as important as what you put in. Applied to UI: empty space isn't wasted space - it's breathing room that makes the content you do show feel more important. Density isn't always the answer.

## From Industrial & Product Design

**Affordance and tactility.** Physical products communicate how to use them through shape, texture, and weight. A door handle's shape tells you to pull or push. Applied to UI: interactive elements should feel interactive before you click them. Hover states that invite. Drag handles that look grabbable. The difference between a flat rectangle and a button.

**Material honesty.** Good product design lets materials be what they are - wood looks like wood, metal feels like metal. Fake materials feel cheap. Applied to UI: glass effects that feel like actual glass (with real refraction and depth), not a blur filter. Shadows that respond to a consistent light source. Visual metaphors that commit fully or not at all.

**The satisfying click.** Physical products invest in the feel of interactions - the click of a well-made switch, the weight of a quality door. Applied to UI: micro-interactions that have the right amount of resistance and feedback. A toggle that has spring physics. A drag that has momentum. A delete that has gravity.
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: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall