Kyoto design philosophy

Kyoto Design Philosophy

Overview

Kyoto is not a city of loudness. It is a city of intentional restraint — where every garden stone, every silence between temple bells, every corridor in a machiya townhouse was designed to create space for thought. The greatest builders of the PC, Internet, and AI eras were all shaped by this city. This skill encodes what they learned.

Use this skill as a decision filter — not a style guide, but a question framework that sits beneath every product decision GenPark makes.

---

The Three Pillars

① 間 (Ma) — Negative Space as Power

Definition: Ma is the Japanese concept of the meaningful pause between things — the gap between pillars, the silence in a tea ceremony, the whitespace on a page. It is not emptiness; it is intentional void.

Steve Jobs on Ma: The hallmark of every Apple product — the breathing room in iOS, the single-button remote, the unsaid feature — was Jobs applying Ma without naming it. He called it "editing ruthlessly." He meant: make space for the user.

Agent Design Application:

• Before generating output, ask: Does this moment require output, or does it require listening?
• An agent that pauses before acting signals intelligence. An agent that fills every silence signals anxiety.
• Build deliberate "Ma moments" into agent workflows: confirmation pauses, reflection steps, and explicit "I'm waiting for your intent" states.

Decision Test: If we removed this feature/response/element, would the product feel more powerful or less? If more — the removal IS the design.

---

② 守破離 (Shu-Ha-Ri) — Master, Break, Transcend

Definition: The three stages of mastery in Japanese martial arts and craft:

• 守 (Shu): Follow the rules exactly. Master the form.
• 破 (Ha): Break from the form intentionally. Adapt to context.
• 離 (Ri): Transcend the form. Create new rules from internalized mastery.

Boris Cheny on Shu-Ha-Ri: The machiya townhouse architecture of Kyoto embodies this — a standardized modular structure (Shu) that each family adapts over generations (Ha), eventually producing entirely new configurations (Ri) that still feel coherent.

Skill Architecture Application:

• Shu layer: Every GenPark skill starts as a standardized SKILL.md template. Agents follow it precisely on first execution.
• Ha layer: Users reshape, combine, and override skills based on their context. The system supports this without friction.
• Ri layer: Over time, agents generate new skills by synthesizing patterns they have observed. This is the goal state: the system writes its own craft.

Decision Test: Is this skill/feature/interaction at Shu, Ha, or Ri stage? Design accordingly — don't impose Ri thinking on a Shu-stage component.

---

③ 一期一会 (Ichigo Ichie) — This Moment, Once

Definition: "One time, one meeting." The tea ceremony principle that every gathering is singular — it will never happen again in exactly this configuration of people, season, light, and mood. Treat it accordingly.

Evan Zhao on Ichigo Ichie: Zoom's core design insight was that the human on the other side of the screen deserves to feel present, not processed. Every call is a one-time event. The interface should honor that.

Simon Last on Ichigo Ichie: Wabi-sabi — the beauty of imperfection and transience — is Ichigo Ichie applied to aesthetics. Products that age gracefully and feel authentic over time carry this quality.

Agent Interaction Application:

• Every GenPark session should begin with context-reading, not template-matching.
• Agents must incorporate: current timestamp, user's recent history, stated mood or urgency, and the specific phrasing of the request — not just keyword extraction.
• Responses should feel addressed to this person, right now — not generated for a persona.

Decision Test: Could this response/output have been generated yesterday for a different user? If yes, it lacks Ichigo Ichie. Rebuild it with present-tense context.

---

Usage Patterns

When Making Product Decisions

1. Run the Ma Test: What can be removed?
2. Run the Shu-Ha-Ri Test: What stage is this component at? Are we designing for the right stage?
3. Run the Ichigo Ichie Test: Is this designed for a specific person in a specific moment, or for an abstracted user?

When Reviewing Agent Skill Designs

• Check if the skill has built-in pause states (Ma)
• Check if the skill supports user customization without breaking (Ha)
• Check if the skill uses session context, not just stored templates (Ichigo Ichie)

When Writing GenPark Brand Copy

• Lead with scene, not feature
• Use negative space in sentences — short paragraphs, deliberate line breaks
• Reference the singular moment — "right now," "this session," "this problem"
• Never claim to be "the most powerful" — claim to be "the most precise"

---

Founder's Reference

"The most profound technologies are the ones that disappear." — Steve Jobs (1998)

"Design is not just what it looks like and feels like. Design is how it works." — Steve Jobs

"We want to remove all the things that prevent people from being able to connect." — Evan Zhao

These are all Ma statements. GenPark's north star: build the silence that lets the user's intelligence emerge.

---

Kyoto Design Checklist

Before shipping any feature, skill, or agent behavior:

• Ma: Have we identified what NOT to include?
• Ma: Does the agent know when to pause and wait?
• Shu: Is the baseline behavior standardized and learnable?
• Ha: Can the user reshape this without breaking it?
• Ri: Is there a path for this to evolve beyond its original form?
• Ichigo Ichie: Does this response/feature use present-context, not cached-persona?
• Ichigo Ichie: Would the output change meaningfully based on who is asking and when?

---

Distilled in Kyoto, May 2026. For GenPark.