DanLogo · Concrete 建筑感
A silent volume, opened by a single subtraction; where light enters, there its name resides.
The architecture-oriented direction of the danlogo series. It defines temperament and quality, not shape, color, or craft. The idea comes from minimalist architecture centered on Tadao Ando: honest materials, pure geometry, light that is let in. It was reverse-engineered from two solutions within the EonPoint family (White·Fold) in cases/, but each new brand must grow its own form from itself.
Core composition: Silent mass (primary) × Light (secondary). Light enters the mass through a single measured subtraction (slit, hole, courtyard, cut, recess) or a face that receives light, making it visible; the position, proportion, shape, light, and thickness of that single subtraction is its name. One gesture, multiple layers: The subtraction is done only once, but it should generate several faces, layers, or a rhythm within the mass so there is something to see at second glance (references/style-dna.md Gene 2).
Four formal languages (four ways light enters the mass; one primary per project): Mass·Void, Facets·Light & Shadow, Arc·Layering, Module·Order—their respective aesthetics, architectural and artistic precedents, and twelve methods can be found in philosophy.md, creative-methods.md, and exemplars.md. This style is industry-agnostic: Phase 1 selects the formal language based on the user's desired aesthetic, not their industry.
Read First
Before starting any project, read the first three style chapters in order; Chapter Four is read at Phase 6:
references/philosophy.md— Intellectual coordinates: why design this wayreferences/style-dna.md— Style genes, knobs, and touchstones: what temperament it looks likereferences/creative-methods.md— Creative methods and anti-homogenization: how to come up with new things each timereferences/style-extension.md— Style extension: what systems, scenarios, and presentations look like (Phases 6–8)
Read references/exemplars.md (reference works) and cases/index.md (already-used motifs) only after Phase 2 has listed candidate motifs—use them to cross off rote answers and motifs that conflict. Reading them first will lead you astray. Full case studies should only be read when you need a reference for "how far to go," and even then borrow only methods, not forms. Other files are read at their corresponding phase (see table below).
Three Levels of Requirements
| Level | Content | Changeable? |
|---|---|---|
| Quality gates (series-wide) | references/quality-gates.md | Every project must pass |
| Style genes (this style) | style-dna.md + philosophy.md self-check | Follow by default; if the user explicitly requests changes, comply and record in decisions.md |
| Creative freedom zone | Motif, formal language, intensity, warmth, color, material, composition | Derive anew for each project; at least two "knobs" must be clearly different from all existing cases |
Three reminders:
- First and foremost, a shape. A logo must first be read as a thing or an image, with a silhouette and a face; not as a variation of a letter, word, or punctuation mark, nor as a sign made of a few lines (
quality-gates.md"How to judge graphic presence"). - Judge by temperament, not by elements. The specific shapes, colors, and crafts in the cases are that brand's answers, not prescriptions of this style.
- Architecture is a method of construction, not a subject. The logo does not depict a building; it itself is something built, something opened by light. A single subtraction is core, but a casual small opening does not count—you must be able to articulate its position, proportion, shape, light, and thickness; leaving only a hole with nothing to see at second glance also does not count.
Nine Phases
See references/workflow.md for details, numbering conventions, and exit criteria. Each phase ends with the user's explicit confirmation; the user may revert, add, modify, or merge at any time.
| Phase | What To Do | Output per Round | Read |
|---|---|---|---|
| 1 Brief | User provides info; AI asks for missing gaps in one pass (≤10 questions) | Brief card | workflow.md |
| 2 Concept | Deconstruct name, excavate motifs | 5 concept cards, may be modified, added, or merged | creative-methods.md, philosophy.md |
| 3 Prototype | Diverge into graphic forms for each locked concept; form only, use black and white first | ≥3 prototypes per concept + initial cross-check | style-dna.md, craft.md |
| 4 Graphic | Refine: construction rules, optical corrections, small-size version, construction diagram | Refined graphic | craft.md, quality-gates.md |
| 5 Final | Custom type and color done together | 2–3 "type + color" combinations per graphic + full cross-check | craft.md, style-dna.md |
| 6 System | Combinations, color variations, white space, minimum size, forbidden usage, animation | Full set SVG/PNG | deliverables.md, style-extension.md |
| 7 Scenarios | Select 6–10 scenarios per industry | Scenario mockups | deliverables.md, style-extension.md |
| 8 Presentation | Presentation document + speaker notes + source package + cross-check re-verification | Presentation | deliverables.md, style-extension.md, adapters/ |
| 9 Summary | Proactively ask if this project should be used to refine the skill | Modification suggestions; write in after user approval | workflow.md section 9 |
Throughout the Entire Process
- Project archive: One folder per project and one
decisions.mdfile (first line:skill: danlogo-concrete v<version>), recording what was shown each round, user's verbatim feedback, what was locked or rejected. When taking over an existing project, read it first. - Structure first: Review in black and white before Phase 5; when this style declares that color is structure, color-aided reviews may begin from Phase 3, but monochrome version must still hold.
- Rejected means go back, don't add: Change motif or prototype, do not add decoration to the original.
- Cross-check three times: Initial at prototype, full at final, recheck before presentation (
quality-gates.md). - Judge by rendered images: Always judge whether something looks good based on rendered images, including a 16px small version.
- Communication: Use the user's language. Start each round with one sentence saying what was done, then list schemes with numbers and a one-sentence rationale, give one recommendation and reason, ask: lock, modify, or continue? For short feedback, first consult
references/feedback-playbook.md. - Client materials only in the project folder, not written into the skill.
When Multiple danlogo Styles Coexist
If the user names a specific style, use that skill. If the project's decisions.md specifies which skill to use, follow that. If neither is specified and multiple danlogo styles are installed, list the installed styles, ask the user to choose, then start.
Tools and Files
scripts/: General tools—geometry and SVG generation (geom.py), multi-image comparison viewer (sheet.py), SVG to PNG conversion (render.sh). Seescripts/README.mdfor instructions. Copy tosrc/in the project when used.adapters/for-claude.md,adapters/for-codex.md: Differences across AI tools in viewing images, making presentations, previewing web pages.evals/briefs.md: Test briefs for verifying that this skill does not turn every brand into the same thing.
Five files in references/ marked with danlogo-core (workflow, quality-gates, craft, deliverables, feedback-playbook) are shared chapters across the danlogo series, consistent across all styles; the four chapters exclusive to this style are philosophy, style-dna, creative-methods, and style-extension: the first three govern the logo itself, the fourth governs the aesthetic of the system, scenarios, and presentation, so that the entire design originates from the same temperament as the logo.