jpoindexter
UserEdward Tufte's visual design principles as agent skills — 38 skills plus a router that picks them for you. Works in Claude Code, Codex, Copilot, Gemini, or any agent that can read a file. Every claim verified page-by-page against all five books.
Categories
Indexed Skills (86)
tufte-aesthetics-and-technique
Use when refining or judging the look of a finished data graphic — aspect ratio and proportion, line weights, type choices, legend versus direct labels, integrating a graphic with its surrounding text — or when a chart is technically correct but ugly, portrait-shaped by software default, legend-dependent, set in clotted all-caps type, or exiled from the prose it belongs to. Not for data-integrity or chartjunk audits.
tufte-analytical-design
Use when designing, reviewing, or defending an evidence presentation — a report, dashboard, scientific figure, policy brief, or technical display — and a standard is needed for whether it assists reasoning; when arguing that a design choice follows from the intellectual task rather than from a template or tool; or when working through Minard's 1869 map as a reference implementation.
tufte-annotation-as-thinking
Use when an image, chart, scan, screenshot, diagram, or dashboard is about to ship without explanation on it; when writing captions, callouts, keys, figure legends, or marginalia; when reviewers cannot tell what they are looking at; when a display must carry a dispute, rebuttal, or provenance beside the evidence; or when designing two-reader formats, commentary layers, or annotated reference editions.
tufte-causal-reasoning-in-graphics
Use when building or critiquing any display whose job is to support a causal claim or a go/no-go decision — epidemic maps, risk scatterplots, failure analyses, treatment comparisons, policy charts — or when reviewing whether a graphic shows why something happened rather than merely when it happened.
tufte-chartjunk
Use when a chart, dashboard, or data graphic looks busy, shimmery, or over-decorated — crosshatch or pattern fills, heavy or doubled grid lines, 3-D extrusion, fake perspective, pictorial fills, drop shadows, or unexamined software-default styling — or when auditing any graphic before publication for marks that carry no data.
tufte-cognitive-style
Use when building, reviewing, or replacing a slide deck, briefing, or analytical presentation; when deciding between slides and a written report or handout; when a deck's density, bullet structure, or headline framing is in question; or when diagnosing how a presentation format degraded the reasoning it was supposed to carry.
tufte-color-in-information-design
Use when choosing or auditing color in a data graphic and something is off — rainbow scales on ordered data, more hues than a viewer can remember, saturated fields drowning small marks, key distinctions riding on color alone, adjacent pastels over large areas, phantom bands appearing at color boundaries, or color that decorates without labeling, measuring, or representing anything.
tufte-data-density
Use when a graphic feels sparse, oversized, or padded for one chart's worth of data — when deciding how much data a display should carry, how small it can shrink, whether a dense chart is really cluttered or just rich, or when choosing between one big chart, small multiples, and a dense table for a large dataset.
tufte-data-forensics
Use when an analysis, dataset, spreadsheet, model, benchmark, or research claim must be audited before it is trusted or acted on — deciding what to demand from a data supplier, tracing a number back to its measurement, screening for randomization, image, binning, or batch-effect failures, scoring a study's credibility, separating a forensic audit from data cleaning, or naming who paid for the answer.
tufte-data-ink-ratio
Use when a chart, graph, or dashboard looks cluttered, over-decorated, or 'busy' — heavy grids, filled bars, box frames, duplicate axes — or before shipping any statistical graphic. Covers Tufte's data-ink ratio, the two-pass erasure procedure, and converting frame/tick ink into data.
tufte-data-maps
Use when designing or auditing a map that carries data and something is off — a plan view spending both axes on geography the question does not need, poster-thin density that collapses on close inspection, ornament filling empty regions, one rigid scale forcing a choice between detail and overview, aggregation to political areas distorting the signal, or map small multiples restyled per panel.
tufte-disinformation-design
Use when auditing a chart, demo, interface, or vendor presentation for concealment tactics — masking, dazzle, decorative diversion, buried disclosures, presenter-dependent displays — when designing pictorial instructions that must show both the audience view and the hidden mechanism (flaps, cutaways, operator viewpoints), when verifying inherited or copied diagrams, or when structuring an honest technical reveal.
tufte-escaping-flatland
Use when a chart, map, dashboard, table, or display must carry more than two variables and the flat surface is running out of room — symptoms include fake 3-D or ornament standing in for data, one separate mark per variable, density so thin it invites suspicion, or uncertainty about which of Tufte's five envisioning methods (micro/macro, layering, small multiples, color, space-time narratives) the problem calls for.
tufte-evidence-corruption
Use when auditing an evidence presentation, research report, press release, or repackaged summary for corruption — passive-voice effects without causes, cherry-picked or culled data, model-search shopping, punning and overreaching claims, chartjunk, or a rage to conclude — and when deciding how much to trust a secondary or tertiary account of primary evidence.
tufte-graphical-competence
Use when diagnosing why a team, publication, or product keeps shipping weak or dishonest data graphics; when chart production is owned by art, brand, or marketing alone; when a brief claims the audience won't understand, statistics are boring, or 'if you have to explain it, don't use it'; when auditing what share of a report's displays are relational; or when deciding who must review a data display before it ships.
tufte-graphical-excellence
Use when designing a new data graphic, grading or reviewing an existing chart, or deciding whether data deserves a graphic at all — especially when a chart looks polished but feels thin, shows a single variable, forces a slow read, or when summary statistics are being offered in place of a plot of the actual data.
tufte-graphical-integrity
Use when designing, reviewing, or auditing any chart for truthfulness — truncated baselines, scaled pictograms, dual axes, perspective or 3-D effects, nominal-dollar time series, or any display where the visual effect may exceed the effect in the data. Covers the Lie Factor and Tufte's six principles of graphical integrity.
tufte-instructions-at-point-of-need
Use when guidance is being written into a manual, help center, onboarding tour, or README instead of into the place where the action happens; when users keep getting a step wrong despite documentation; when designing signage, wayfinding, labels, or checklists; when a decision tree is growing branches; or when glare, reflections, or screen placement degrade a display in a real working environment.
tufte-integration-of-modes
Use when deciding how a document places its words, numbers, images, tables, and diagrams — figure placement, captions, appendices, plates or color sections, cross-reference numbering — or when a report, book, guide, or interface separates evidence by mode and readers have to chase links between parts to reconstruct a single argument.
tufte-layering-and-separation
Use when a display's layers fight each other — grids louder than the data, vibrating or shimmering edges, boxed words with white halos, moire beating between overlapping patterns, every element at one equal visual weight, or labels breeding bright stripes against the marks they name. Applies to any surface stacking data over scaffolding: maps, tables, timetables, dashboards, dense diagrams.
tufte-link-differentiation
Use when designing or critiquing any diagram that ties nouns together with lines — flow charts, networks, webs, trees, cladograms, org charts, project or parse trees, influence and causal diagrams — and the connectors need to carry relationship type, direction, strength, certainty, or mechanism; also when auditing what a diagram's missing links silently claim.
tufte-lists
Use when a backlog, nav menu, settings screen, tag system, or taxonomy is ordered alphabetically or by inherited default; when a hierarchy runs past 2 levels and users call it complicated; when checklist items were chosen without asking what was excluded; when a style sheet or linter fights a list's spacing; when pros/cons or comparisons need a 2-D array; or when a list of nouns is hiding agency that verbs would show.
tufte-mapped-pictures
Use when preparing or auditing an image meant to serve as evidence — a photograph, scientific micrograph, satellite or astronomical picture, diagram, drawing, or painting — and it needs measurement scales, a coordinate grid, or labels; also when judging whether a mapping or overlay laid on top of an image is a credible explanation or an unfalsifiable one.
tufte-meetings-and-documents
Use when a slide deck is scheduled for a decision meeting, design review, PRD review, or briefing; when planning a meeting's time budget, agenda, or pre-read; when pre-reads go out by email and nobody reads them; when a talk to a large audience needs a handout; when you are the low-power party who keeps getting interrupted; or when choosing between presenting a thing and circulating a document about it.
tufte-micro-macro-readings
Use when a dense display must read at two scales at once and is failing at either — the glance shows no pattern, close inspection yields no individual values, detail is being stripped to 'reduce clutter,' data is fanned thinly across many pages or slides, or an ordering choice (alphabetical vs. meaningful) is severing individual marks from the aggregate story.
tufte-multifunctioning-elements
Use when a chart's frames, grids, axes, ticks, or labels carry no data — round-number axes, arbitrary grid lines, blank rectangular frames — or when more variables must be encoded without adding ink; also when choosing or reviewing range-frames, dot-dash-plots, quartile plots, white grids, rug plots, or any element asked to do two display jobs at once.
tufte-narrative-and-sequence
Use when designing or reviewing visual explanations of process, motion, causality, or change — instructional diagrams, animation stills, step-by-step guides, motion multiples, field guides, or technical presentations — or when auditing an image-based display for missing scales, hidden data, or misleading sequence.
tufte-parallelism
Use when designing comparison views, before/after UI, diff displays, overlays, synchronized media panels, identification guides, field guides, or any layout that sets two or more things side by side — or when reviewing a comparison for mismatched scales, broken registration, stacked-in-time sequences, or labels relayed through codes.
tufte-presentation-of-artifacts
Use when deciding or reviewing how finished work is displayed — mounts, pedestals, frames, packaging, app-store screenshots, portfolio case-study staging, dashboard chrome, demo wrappers; when display apparatus added after completion competes with the work, covers a maker's mark or attribution, or leaves a visible seam between work and its ground; or when auditing what fraction of visual space presentation chrome consumes.
tufte-redundant-encoding
Use when deciding whether a variable should ride on more than one visual channel, or when a display shows symptoms of getting that wrong — hue-only encoding that dies in grayscale or for color-deficient viewers, channels colliding into moire or 1+1=3 noise, a second encoding that buys no robustness or separation, or cyclic data severed at an arbitrary boundary such as midnight.
tufte-small-multiples
Use when comparing the same measurement across many conditions, categories, times, or places — when an overlaid chart drowns in crossing lines, an animation or slideshow forces comparison from memory, panels auto-scale to different ranges, or a faceted/trellis/grid layout is being designed or reviewed for panel size, ordering, borders, and shared scales.
tufte-space-time-graphics
Use when data records movement or development through space and time — transit schedules, single-track planning, orbital or biological trajectories, race standings, motion or dance notation — especially when a numeric timetable is hiding conflicts, dwell, or congestion, slopes are corrupted by equally spaced stations, a dark grid is burying the lines, or a daily cycle is cut off at midnight.
tufte-sparklines
Use when a number, table, or dashboard metric needs its history shown in the space of a word; when embedding data graphics in prose, tables, or clinical, financial, sports, and scientific displays; when choosing sparkline aspect ratio, color, or anchoring method; or when arguing for higher information density against low-resolution charts and slides.
tufte-tables-and-text-tables
Use when choosing between a sentence, text-table, table, semi-graphic, or chart for a set of numbers; when ~20 or fewer values are about to become a graphic; when designing or auditing any data table — row order, clustering, rules, alignment; when dozens of little bar or pie charts could collapse into one dense reference table; or when a table needs graphical properties: slopes, value-glyphs, or data-proportional spacing.
tufte-typography-for-data
Use when setting type that carries data — chart labels, axis titles, table headers, legends, captions, schedules, maps, dashboards, or numeric columns; when a legend, key, or letter-coded caption is being added; when linebreaks, alignment, or column width are being decided by a grid or style sheet rather than by content; when choosing a typeface or weight for small or dense text; or when a display's aspect ratio is being set by a default.
tufte-visual-confections
Use when designing explanatory posters, mixed-media dashboards, infographic narratives, onboarding scenes, kiosk or content-first interface screens, or title/cover art that must argue rather than decorate — or when judging whether an assembled composition of heterogeneous images reasons, lists, and narrates or merely juxtaposes.
tufte-visual-index
Use when back matter, a reference list, an appendix, a component library, a design-system doc, an asset registry, a figure list, a research repository, a changelog, or a portfolio archive has become an alphabetical wall of strings nobody browses — or when deciding how to order and key a reference apparatus so readers can recognize entries by sight and by position instead of searching for an exact string.
tufte-visual-thinking
Use when a display, interface, model, or taxonomy is being accepted in its inherited form; when a default format, style sheet, grid, or chart type is chosen by convention rather than by content; when 3D reality is being flattened into a 2D model; when a claim needs tracing to primary measurement; when links or arrows are unlabeled; or when a reviewer asks how a claim is really known.
tufte
Use when invoked by name (/tufte in Claude Code, $tufte in Codex, or 'tufte' in any agent), or when creating, reviewing, or auditing any data display — chart, graph, table, dashboard, map, timeline, sparkline, diagram, annotated image, slide deck, meeting doc, or evidence presentation — and it's unclear which tufte-* skill applies. Router for the 38-skill Edward Tufte pack.
body-text-and-reading
Use when setting or fixing running text meant to be read continuously — article bodies, documentation, long-form pages, onboarding copy, email. Also use when readers report eye strain, losing their place, re-reading lines, or text that "feels dense", and when choosing body size, line-height, or measure.
color-and-icon-fonts
Use when type needs to be more than one flat colour, or when glyphs carry non-letter meaning — layer fonts, colour fonts (COLRv1, OT-SVG, bitmap), CSS font-palette, icon fonts, emoji. Also use when deciding between an icon font and SVG, when a colour font renders as flat black, or when emoji or icons break in a screen reader.
design-token-generation
Use when turning typographic decisions into tokens, variables, or theme config — naming a type scale, structuring font/size/weight/line-height tokens, exporting to CSS/Tailwind/Style Dictionary/iOS/Android, or fixing a token set that has drifted into arbitrary values. Also use when design and code disagree about what the type scale actually is.
editorial-web-typography
Use when designing article, long-form, marketing, or art-directed pages — pull quotes, drop caps, captions, bylines, subheads, figures, footnotes, hero compositions. Also use when an article template feels flat and undifferentiated, or when a page needs expressive typographic voice without sacrificing readability.
font-loading-and-performance
Use when shipping webfonts — choosing formats, subsetting, preloading, setting font-display, eliminating FOUT/FOIT, or fixing layout shift (CLS) caused by font swap. Also use when fonts are slow, text is invisible on load, the page jumps when fonts arrive, or Core Web Vitals flag font-related shift.
hierarchy-and-scale
Use when building or fixing a type scale, choosing heading sizes, or when a screen's importance ordering is unclear — everything looks the same weight, users miss the primary action, or headings compete. Also use when a design has drifted into a dozen ad-hoc font sizes.
international-typography
Use whenever type will render in a non-Latin script or a language other than English — Arabic, Hebrew, CJK, Indic, Cyrillic, Greek, Thai. Also use for bidirectional text, vertical writing, localisation-driven layout breakage, font stacks for multiple scripts, and any assumption that Latin typographic rules generalise.
microtypography
Use when text is technically correct but reads poorly — uneven word spacing, rivers, bad rags, orphans and widows, awkward hyphenation, loose or tight tracking, wrong quote marks and dashes, cramped all-caps. Also use when a design "feels cheap", "looks AI-generated", or "something is off" and the cause is spacing detail rather than font choice.
motion-typography
Use when type moves or changes over time — animated headlines, kinetic type, text transitions, animated or responsive logotypes, scroll-driven text effects, typing/counting animations, variable-font axis animation, or loading and streaming text. Also use when motion is making text hard to read, causing discomfort, or failing reduced-motion and accessibility requirements.
responsive-typography
Use when type must adapt across viewports, containers, or devices — fluid sizing with clamp(), breakpoint jumps, text that overflows or shrinks illegibly on mobile, headings that wrap badly, or a scale that works on desktop and collapses on phone. Also use when building a type system intended to be resolution-independent.
type-foundations
Use when typographic vocabulary or first principles are needed — what an em actually is, font vs typeface, leading vs line-height, points vs pixels, how CSS units relate, what the em square means. Also use when someone is confidently using a term incorrectly, or when an explanation needs grounding before a decision is made.
type
Use when the user invokes /type, or when any task involves setting, choosing, scaling, spacing, loading, tokenizing, auditing, or critiquing type — a font choice, a type scale, body copy, headings, a data table, a UI label, responsive text, webfont performance, or non-Latin script. Also use when a screen "looks off" and the cause may be typographic. Dispatcher that routes to the focused typography-* skills.
typeface-anatomy
Use when reading a specimen, naming letterform parts, or explaining why two typefaces differ — apertures, counters, terminals, stroke contrast, axis, x-height, proportions. Also use when a font choice needs to be justified from visible evidence rather than vibes, or when comparing candidates that "look basically the same".
typeface-pairing
Use when combining two or more typefaces — heading plus body, display plus UI, adding a face to an existing system, or diagnosing a pairing that "clashes" or "looks the same". Also use when deciding whether a second typeface is needed at all.
typeface-selection
Use when choosing or replacing a typeface — "which font should we use", evaluating candidates, building a type palette, or replacing a face that isn't working. Also use when a font must carry a brand tone, survive small sizes, support extra scripts, or fit a licensing and performance budget.
typography-accessibility
Use whenever type carries information — always co-load this with body text, UI, and editorial typography work. Specifically for contrast, 200% zoom, user text-spacing overrides, Dynamic Type, dyslexia and low-vision needs, screen-reader compatibility, images of text, and any claim that typography is "accessible".
typography-audit
Use when systematically reviewing existing typography against criteria — "check this page", "audit our type", pre-launch review, design-system compliance, or inherited work of unknown quality. Produces a pass/fail finding list with evidence. Use typography-critique instead when the question is about taste rather than compliance.
typography-critique
Use when the question is quality or taste rather than compliance — "is this any good", "does this feel right", "why does this look generic or AI-generated", art-direction review, or judging whether a typographic risk pays off. Use typography-audit instead when checking against defined criteria.
typography-layout-systems
Use when composing type in space rather than sizing it — deciding how a poster, hero, editorial spread, dashboard, or landing page is structurally organized. Also use when a layout feels arbitrary, elements float without relationship, a grid is being applied by reflex, or a composition needs deliberate tension or movement.
ui-component-typography
Use when setting type inside interface components — buttons, labels, inputs, form errors, navigation, badges, tooltips, tables, dense dashboards. Also use when numbers jitter in a table, labels wrap unpredictably, UI text is illegible at small sizes, or a component's text breaks in another language.
variable-fonts
Use when working with variable fonts — choosing between variable and static files, using weight/width/optical-size/slant axes, setting font-variation-settings vs standard properties, animating axes, or deciding whether a variable font actually saves bytes. Also use when a variable font renders wrong or ignores its axes.
ai-agent-case-study
Structure and write design case studies for AI agents, copilots, autonomous workflows, multi-agent systems, and other probabilistic products. Use when a case study must explain autonomy levels, permissions, approval thresholds, steering, observability, user-visible rationale, uncertainty, trust calibration, streaming, latency, orchestration, failures, retries, rollback, state recovery, evals, or human-in-the-loop design.
case-study
Route and produce evidence-backed product or design case studies from raw notes, research, screenshots, specifications, decision logs, architecture, metrics, and project artifacts. Use when the user invokes /case-study, asks to write, critique, structure, or polish a portfolio case study, needs to explain a complex design project, or needs an AI-agent case study covering autonomy, human oversight, telemetry, trust, latency, failures, and recovery.
portfolio
Plan, build, critique, update, or ship a professional design portfolio as one evidence-backed system. Use when the user invokes /portfolio; needs portfolio positioning, project inventory and selection, personal brand, case studies, homepage/about/contact copy, information architecture, visual direction, website implementation, accessibility, review, or publishing; or wants to turn scattered work into a coherent portfolio for a specific role, client, or audience.
narrative-arc-builder
Map raw project timelines, notes, research, and metrics into a five-stage evidence-backed narrative arc for a design case study. Use when a draft reads like a chronological task list, lacks tension or a turning point, makes the designer or product the hero, buries the pivotal decision, or needs a clear context-friction-complexity-breakthrough-impact structure.
technical-microcopy-editor
Run an accuracy, clarity, and brevity edit on technical design case-study copy. Use when prose contains vague UX jargon, imprecise system claims, passive voice, inconsistent terms, inflated ownership, unsupported metrics, long captions, or when the draft should become materially shorter without losing quantitative evidence or technical meaning.
usedesign
Use when the user invokes /usedesign, or hands over any design/UI task (screen, component, layout, color, type, motion, flow, chart, wireframe, audit, polish, copy, case study) and it's unclear which design skills to load — a router over ALL installed design skills that reads the task and picks the best 2-5 to apply.
case-study-design-decisions
Explain and defend pivotal design decisions in a case study using stakeholder context, user and business evidence, alternatives, constraints, trade-offs, consequences, limitations, and follow-up. Use when a portfolio draft shows screens without rationale, lists activities instead of decisions, needs executive credibility, must explain rejected options, or must communicate complex enterprise, platform, system, or AI-agent design choices.
case-study-story-map
Map project evidence into a user-centered outcome arc for a product or design case study. Use when raw notes are chronological, the story lacks tension or a clear result, the product or designer has become the hero instead of the user, a journey needs a beginning-middle-end structure, or research and analytics must be connected to goals, conflicts, pivotal decisions, and measurable outcomes.
case-study-storytelling
Build a coherent narrative system for complex design case studies using characters, context, plot, subplots, turning points, branching journeys, theme, scenes, and a trust or emotional arc. Use for multichannel products, nonlinear flows, service ecosystems, AI-agent experiences, portfolio presentations, or drafts that contain good evidence but read like disconnected screens and activities.
case-study-writing
Draft, edit, and finish concise design case-study copy from an evidence ledger or structured outline. Use when a portfolio case study is verbose, vague, generic, overly chronological, full of UX process theater, missing scannable headings and captions, inconsistent in voice, or needs publication-ready structure without inventing research, metrics, outcomes, or quotes.
enforce-scannable-density
Edit a portfolio case study for high signal, compact hierarchy, and fast scanning without losing evidence. Use when a draft is fluffy, repetitive, slow to navigate, paragraph-heavy, full of generic process language, or needs concise headings, key-value blocks, comparison matrices, captions, and technical spec blocks.
extract-design-rationale
Extract defensible design rationale from project notes, logs, specifications, research, and artifacts. Use when a case study shows what was built but not why, needs a constraint-alternatives-decision matrix, must explain rejected options and trade-offs, or needs to connect a UI, product, system, or AI-agent decision to evidence and measurable consequences.
system-architecture-translator
Translate data flows, services, queues, workflows, storage, consistency, latency, failures, retries, and distributed-system constraints into visible product and UX decisions for a case study. Use for AI agents, desktop tools, data products, scraping engines, background jobs, cloud systems, or any portfolio story where architecture determines telemetry, state management, loading, recovery, permissions, or user control.
brand-case-studies
Use when you need a real-world brand-identity precedent to justify a recommendation, cite a comparable project, or diagnose what made an identity succeed — e.g. a rebrand honoring heritage/equity, localizing or naming for a new market, differentiating from a parent company, launching a new company or category, unifying a fractured multi-touchpoint ecosystem, or building a dynamic/flexible system.
brand-dynamics
Use when accounting for contemporary forces on a brand — social justice stances, sustainability/triple bottom line, going global or localizing, AI in the workflow, big-data analytics, social media strategy, digital/AR/VR interfaces, mobile app icons, evidence-based marketing, private-label architecture, brand licensing, certification symbols, crisis communications, or personal branding.
brand-elements
Use when choosing or evaluating the concrete building blocks of a visual identity — deciding which type of logo or mark fits a brand (wordmark, letterform, pictorial, abstract, emblem, dynamic), naming a company or product, judging whether a name or tagline is strong, or picking whether a brand needs a character. Reach for it whenever the question is 'what type of mark/name/tagline should this be' rather than how to run the identity process.
brand-fundamentals
Use when someone conflates brand, branding, brand identity, and brand strategy or asks what those words mean; when justifying investment in identity; when mapping stakeholders, aligning culture with brand, defining brand experience, or choosing a brand-architecture type (branded house vs house of brands vs endorsed/hybrid); or when scoping visual identity, messaging/voice, or governance.
brand-ideals
Use when judging, critiquing, or defending brand identity work and functional checkboxes (recognizable, protectable, consistent) aren't enough to explain why one identity is better; evaluating a proposed logo/system, setting acceptance criteria for an identity project, repositioning a brand, or grading a merger/retail/venture identity against a rubric.
brand-redesign
Use when deciding whether to refresh an existing brand, evolve vs overhaul a brandmark, redesign packaging, or rename a company or product — and when judging how much brand equity to preserve, whether a redesign is warranted, or how to justify the business case for change.
brand
Use when the user invokes /brand, or asks to build, name, position, design, roll out, evaluate, or refresh a brand identity — a logo/brandmark, brand strategy, positioning, brand brief, visual system, brand guidelines, touchpoints, or a rebrand — and it is unclear which brand-identity reference skills apply. Dispatcher that routes to the right companion skills distilled from Wheeler & Meyerson's Designing Brand Identity (6e).
clarifying-strategy
Use when defining what a brand stands for and what to call it — distilling research into a unifying idea, narrowing focus, writing a positioning strategy, developing a brand brief, running a naming project, or screening names for trademark/legal availability. Also when a merger, joint venture, blank-page startup, or repositioning needs a strategy or name.
conducting-research
Use when starting a brand identity project and you need to understand the organization before designing — gathering baseline documents, interviewing stakeholders, defining the problem, running market research or usability tests, auditing marketing/competitors/language, or presenting a findings report to decision makers.
creating-touchpoints
Use when the identity concept is approved and it's time to roll it out across every touchpoint — designing or reviewing the website, collateral, stationery, product, packaging, advertising, branded environments, signage/wayfinding, vehicles, uniforms, or ephemera — or when applications feel inconsistent, off-brand, or produced ad hoc without a unified system.
designing-identity
Use when starting Phase 3 creative design after the brand brief is agreed — designing the actual visual/sensory system: choosing wordmark vs symbol, building color palettes, selecting or commissioning typefaces, designing iconography, defining look and feel, adding sound/scent/touch/taste, testing marks in trial applications, or planning the first design presentation.
managing-brand-assets
Use when launching a new or changed brand identity, rebranding or merging entities, planning an internal vs external rollout, building employee brand champions, standing up an online brand center or DAM, writing brand guidelines or a brand book, or deciding what content the standards must cover to keep the brand consistent over time.
managing-the-process
Use when planning or running a brand-identity initiative end to end — scoping a rebrand or new brand, estimating how long it will take, setting up project-management or decision-making protocols, choosing who leads, judging whether the organization is ready to start, defining how success is measured, handling collaboration across silos, or sorting out trademark/IP basics.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.