Skip to content

Kk Exhibition Planner Skill

Exhibition pre-planning Skill that turns client materials into structured exhibition outlines.

Install: git clone https://github.com/sunzhaokai95/kk-exhibition-planner-skill

Works with Claude Code · 22 GitHub stars

Install

$git clone https://github.com/sunzhaokai95/kk-exhibition-planner-skill

Install command taken from the project's README or registry entry. Always review code before running it.

🧭 KK Exhibition Planner Skill

English | 简体中文

A Claude Code Skill for exhibition pre-planning. It turns scattered client materials, spatial constraints, and audience goals into a structured exhibition outline that can be discussed, copied, and further developed.

🎯 What It Is

KK Exhibition Planner works like a navigation system for exhibition pre-planning. When curators face a pile of client notes, space information, audience requirements, and content fragments, it does not jump straight to a slogan. Instead, it identifies the project type, collects structured information, analyzes the essence of the project, derives a theme, selects a narrative route, and then produces a standard exhibition outline.

It is designed for the messy middle of exhibition planning: moving from “too much material and no clear direction” to “a theme, a structure, and an outline ready for design development.” It is suitable for curators, exhibition designers, museum professionals, cultural tourism planners, and teams that need to organize exhibition requirements into a pre-planning outline.

🌱 Why It Exists

I am a curator, which means I often receive a pile of client materials and a deadline that sounds like “we need to see a proposal next week.” Over the years, I realized that the most valuable and hardest-to-teach part of exhibition planning is the concept: deriving what an exhibition is really about from a company, a city, a history, or a cultural resource. This step is often explained as “look more, think more, find the feeling.” KK Exhibition Planner is the lightweight open-source version of the method I have built through years of project work. It does not handle space planning or visual design; it keeps only the most universal and most easily blocked part: from materials, to theme, to exhibition outline. For experienced planners, it is an accelerator. For newcomers, it is a practical mentor that does more than say “find the feeling.”

✨ Core Features

Feature Description
6-step exhibition planning workflow Moves from project identification to information collection, project analysis, theme derivation, outline generation, and optional concept deck copy.
Guidance for three project types Covers enterprise showrooms, museums/cultural venues, and cultural tourism/theme venues, each with its own checklist and planning logic.
Five narrative route methods Supports pyramid, ladder, parallel, scatter, and multidimensional narrative structures.
HTML brief form generation Uses a local Python script to generate brief-form.html, making project information easier to collect and paste back into the assistant.
Three concept deck frameworks Provides audience-driven, concept-analogy, and breakthrough-positioning page flows for concept derivation decks.

🧩 Workflow

flowchart TD
  A["Step 1 Identify Project Type"] --> B["Step 2 Collect InformationGenerate HTML Brief Form"]
  B --> C["Step 3 Digest MaterialsProject Analysis"]
  C --> D["Step 4 Pre-planning DerivationFrom Essence to Theme"]
  D --> E["Step 5 Generate Exhibition Outline"]
  E --> F["Step 6 Generate Concept Deck CopyOptional"]

Similar plugs

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…

Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.

Explore related