semiotics

Diagnose misinterpretation risk in interfaces by analyzing signifier-to-signified mappings.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill semiotics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semiotics
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/semiotics
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill semiotics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Semiotics prevents users (and agents) from misinterpreting interface meaning by diagnosing sign-system failures across icons, color, affordances, and code/API naming.

Core Features & Use Cases

  • Signifier → signified audits: checks whether each visual/textual cue reliably points to the intended meaning within the same context.
  • Icon, color, and affordance coherence checks: detects icon polysemy, color denotation vs connotation drift, and missing anti-affordance for disabled states.
  • Cross-surface consistency review: evaluates whether the same concept is signed consistently across UI and code-facing surfaces (e.g., function and endpoint names).

Quick Start

Use the semiotics skill to audit an interface’s icon and color meaning drift by asking: "Audit our sign system for icon/color/affordance coherence and explain where users are likely to misread meaning."

Frequently Asked Questions about semiotics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit interface signs for icon and color misinterpretation risk?

To audit interface signs for icon and color misinterpretation risk, analyze signifier-to-signified mappings across your UI to detect icon polysemy, color denotation drift, and missing anti-affordances using structured semiotic reasoning.

What causes users to misread meaning in visual interface design cues?

Users misread meaning in visual interface design cues when signifier-to-signified mappings fail, causing icon polysemy, color connotation drift, or inconsistent affordances across multiple product screens and surfaces.

How do I check design coherence between UI icons and API naming conventions?

Check design coherence between UI icons and API naming by performing a cross-surface consistency review to evaluate whether the same concept is signed consistently across both visual and code-facing surfaces.

When should I use semiotic analysis for interface design audits?

Use semiotic analysis for interface design audits when diagnosing sign-system failures in icons, color status badges, visual metaphors, interactive states, and code or API naming conventions across multiple product screens.

Can I diagnose disabled state anti-affordance failures using sign analysis?

You can diagnose disabled state anti-affordance failures by applying semiotic sign analysis to detect missing anti-affordances and evaluate interactive versus disabled state coherence separately from color math and accessibility contracts.

What is the best way to prevent color denotation and connotation drift in interfaces?

The best way to prevent color denotation and connotation drift in interfaces is to separate sign analysis from microcopy and color math, evaluating color-as-sign mappings against intended meaning within their specific context.