semiotics
Semiotics
Concept of the skill
Semiotics is the discipline of designing and auditing the multi-channel sign systems through which an interface communicates with its users. Its primitives are signifiers (perceivable forms — icons, colors, shapes, positions, words, interaction cues) and signifieds (the concepts, states, actions, or judgments those forms point to), and its working vocabulary comes from four sources: Peirce's icon/index/symbol trichotomy (a sign resembles, causally connects to, or arbitrarily conventions its referent), Saussure's signifier/signified dyad, Barthes' denotation/connotation/myth layers, and Norman's affordance theory (real affordance, perceived affordance, signifier, anti-affordance). The skill applies these models across visual surfaces (color, shape, position, iconography) and textual/code surfaces (function names, API endpoints, error messages) under one governing rule: one signifier should point clearly to one intended signified within a given system context. Its central insight is that every interface element is already communicating whether the designer intended it to or not, so the job is to make that communication intentional and coherent rather than to leave it to aesthetic intuition. Sign drift — a gear icon that means different things on different pages, a green badge that connotes "good" while the metric worsens, a disabled button that still looks clickable — is not a cosmetic quirk; it is a sign failure that imposes inference cost on the reader and compounds into distrust of the whole surface.
Coverage
Semiotic analysis as the study of sign systems in software interfaces and communication. Covers:
- Foundational models — Peirce's icon / index / symbol trichotomy; Saussure's signifier / signified dyad; Barthes' denotation / connotation / myth layers
- Visual semiotics for interfaces — color as sign (denotation + connotation, with the never-color-alone rule), shape and position as sign channels (top-left, top-right, bottom-right, circle, triangle, pill)
- Iconography as a sign system — consistency, metaphor clarity, pairing rules, system coherence; common breakdowns (icon polysemy, opacity, cultural collision, obsolete metaphor)
- Affordance theory — real affordance, perceived affordance, signifier, anti-affordance; the rule that disabled states need a strong anti-affordance
- Code and API semiotics — naming, variable, endpoint, and error-message signs; the rule that vague names like
processData()are signifier failures even when the implementation works - Semiotic-coherence audit — the checklist for reviewing a surface across color, icon, affordance, and cross-surface consistency
The skill operates above microcopy execution and color-token math, and below formal ontology. It owns the question "what does this sign communicate to a user?", not "what should the button say?", "what hex value is this?", or "what class hierarchy do these things belong to?".