create-glyph
Über
Die `create-glyph`-Fähigkeit erzeugt R-basierte Piktogramm-Icons für Visualisierungsebenen unter Verwendung von ggplot2 und einer Primitiven-Bibliothek. Sie verwaltet den gesamten Workflow von Konzept und Farbstrategie über Registrierung, Pipeline-Rendering bis zur Verifizierung der Neon-Leucht-Ausgabe. Nutzen Sie sie, wenn neue Entitäten hinzugefügt, bestehende Glyphen ersetzt oder stapelweise Icons für eine neue Domäne in der Force-Graph-Visualisierung erstellt werden sollen.
Schnellinstallation
Claude Code
Empfohlennpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/create-glyphKopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um diese Fähigkeit zu installieren
Dokumentation
Create Glyph
Make R-based pictogram glyphs for skill, agent, or team icons in viz/ visualization layer. Each glyph is pure-ggplot2 function. Draws recognizable shape on 100x100 canvas. Rendered with neon glow to transparent-background WebP.
When Use
- New skill, agent, or team added. Needs visual icon
- Existing glyph needs replacement or redesign
- Batch-creating glyphs for new skills domain
- Prototyping visual metaphors for entity concepts
Inputs
- Required: Entity type —
skill,agent, orteam - Required: Entity ID (e.g.,
create-glyph,mystic,r-package-review) and domain (for skills) - Required: Visual concept — what glyph should depict
- Optional: Reference glyph to study for complexity level
- Optional: Custom
--glow-sigmavalue (default: 4)
Steps
Step 1: Concept — Design the Visual Metaphor
Identify entity being iconified. Pick visual metaphor.
- Read entity's source file. Understand core concept:
- Skills:
skills/<id>/SKILL.md - Agents:
agents/<id>.md - Teams:
teams/<id>.md
- Skills:
- Pick metaphor type:
- Literal object: flask for experiments, shield for security
- Abstract symbol: arrows for merging, spirals for iteration
- Composite: combine 2-3 simple shapes (e.g., document + pen)
- Reference existing glyphs for complexity calibration:
Complexity Tiers:
+----------+--------+-------------------------------------------+
| Tier | Layers | Examples |
+----------+--------+-------------------------------------------+
| Simple | 2 | glyph_flame, glyph_heartbeat |
| Moderate | 3-5 | glyph_document, glyph_experiment_flask |
| Complex | 6+ | glyph_ship_wheel, glyph_bridge_cpp |
+----------+--------+-------------------------------------------+
- Pick function name:
glyph_<descriptive_name>(snake_case, unique)
Got: Clear mental sketch of shape with 2-6 planned layers.
If fail: Concept too abstract? Fall back to related concrete object. Review existing glyphs in same domain for inspiration.
Step 2: Compose — Write the Glyph Function
Write R function producing ggplot2 layers.
-
Function signature (immutable contract):
glyph_<name> <- function(cx, cy, s, col, bright) { # cx, cy = center coordinates (50, 50 on 100x100 canvas) # s = scale factor (1.0 = fill ~70% of canvas) # col = domain color hex (e.g., "#ff88dd" for design) # bright = brightened variant of col (auto-computed by renderer) # Returns: list() of ggplot2 layers } -
Apply scale factor
* sto ALL dimensions for consistent scaling:r <- 20 * s # radius hw <- 15 * s # half-width lw <- .lw(s) # line width (default base 2.5) lw_thin <- .lw(s, 1.2) # thinner line width -
Build geometry using available primitives:
Geometry Usage ggplot2::geom_polygon(data, .aes(x, y), ...)Filled shapes ggplot2::geom_path(data, .aes(x, y), ...)Open lines/curves ggplot2::geom_segment(data, .aes(x, xend, y, yend), ...)Line segments, arrows ggplot2::geom_rect(data, .aes(xmin, xmax, ymin, ymax), ...)Rectangles ggforce::geom_circle(data, .aes(x0, y0, r), ...)Circles -
Apply color strategy:
Alpha Guide: +----------------------+------------+--------------------------+ | Purpose | Alpha | Example | +----------------------+------------+--------------------------+ | Large fill (body) | 0.08-0.15 | hex_with_alpha(col, 0.1) | | Medium fill (accent) | 0.15-0.25 | hex_with_alpha(col, 0.2) | | Small fill (detail) | 0.25-0.35 | hex_with_alpha(bright, 0.3) | | Outline stroke | 1.0 | color = bright | | Secondary stroke | 1.0 | color = col | | No fill | --- | fill = NA | +----------------------+------------+--------------------------+ -
Return flat
list()of layers. Renderer iterates and wraps each with glow. -
Place function in right primitives file by entity type:
- Skills: domain-grouped across 19 primitives files:
primitives.R— bushcraft, compliance, containerization, data-serialization, defensiveprimitives_2.R— devops, general, git, mcp-integrationprimitives_3.R— mlops, observability, PM, r-packages, reporting, review, web-dev, esoteric, design- More
primitives_4.Rthroughprimitives_19.Rfor newer domains
- Agents:
viz/R/agent_primitives.R - Teams:
viz/R/team_primitives.R
- Skills: domain-grouped across 19 primitives files:
Got: Working R function returning list of 2-6 ggplot2 layers.
If fail: ggforce::geom_circle errors? Confirm ggforce installed. Coords off? Canvas is 100x100 with (0,0) at bottom-left. Test function interactively:
source("viz/R/utils.R"); source("viz/R/primitives.R") # etc.
layers <- glyph_<name>(50, 50, 1.0, "#ff88dd", "#ffa8f0")
p <- ggplot2::ggplot() + ggplot2::coord_fixed(xlim=c(0,100), ylim=c(0,100)) +
ggplot2::theme_void()
for (l in layers) p <- p + l
print(p)
Step 3: Register — Map Entity to Glyph
Add entity-to-glyph mapping in right glyph mapping file.
For skills:
- Open
viz/R/glyphs.R - Find comment section for target domain (e.g.,
# -- design (3)) - Add entry in alphabetical order within domain block:
"skill-id" = "glyph_function_name", - Update domain count in comment if applicable
For agents:
- Open
viz/R/agent_glyphs.R - Find alphabetical position in
AGENT_GLYPHS - Add entry:
"agent-id" = "glyph_function_name",
For teams:
-
Open
viz/R/team_glyphs.R -
Find alphabetical position in
TEAM_GLYPHS -
Add entry:
"team-id" = "glyph_function_name", -
Verify no duplicate ID exists in target list
Got: Right *_GLYPHS list has new mapping.
If fail: Build later reports "No glyph mapped"? Double-check entity ID exactly matches one in manifest and registry.
Step 4: Manifest — Add Icon Entry
Register icon in right manifest file.
For skills: viz/data/icon-manifest.json
{
"skillId": "skill-id",
"domain": "domain-name",
"prompt": "<domain basePrompt>, <descriptors>, dark background, vector art",
"seed": <next_seed>,
"path": "public/icons/cyberpunk/<domain>/<skill-id>.webp",
"status": "pending"
}
For agents: viz/data/agent-icon-manifest.json
{
"agentId": "agent-id",
"prompt": "<agent-specific descriptors>, dark background, vector art",
"seed": <next_seed>,
"path": "public/icons/cyberpunk/agents/<agent-id>.webp",
"status": "pending"
}
For teams: viz/data/team-icon-manifest.json
{
"teamId": "team-id",
"prompt": "<team-specific descriptors>, dark background, vector art",
"seed": <next_seed>,
"path": "public/icons/cyberpunk/teams/<team-id>.webp",
"status": "pending"
}
Got: Valid JSON with new entry placed among type siblings.
If fail: Validate JSON syntax. Common mistakes: trailing comma after last array element, missing quotes.
Step 5: Render — Generate the Icon
Run icon pipeline to render new glyph. Always use build.sh as entry point — it handles platform detection and R binary selection. See render-icon-pipeline for full flag reference and pipeline architecture.
# From project root — renders all palettes, standard + HD, skips existing icons
bash viz/build.sh --only <domain> --skip-existing # skills
bash viz/build.sh --type agent --only <id> --skip-existing # agents
bash viz/build.sh --type team --only <id> --skip-existing # teams
# Dry run first:
bash viz/build.sh --only <domain> --dry-run
build.sh runs full pipeline (palette → data → manifest → render → terminal glyphs). Non-render steps add ~10 seconds but keep all data current.
Output locations:
- Skills:
viz/public/icons/<palette>/<domain>/<skill-id>.webp - Agents:
viz/public/icons/<palette>/agents/<agent-id>.webp - Teams:
viz/public/icons/<palette>/teams/<team-id>.webp
Got: Log shows OK: <entity> (seed=XXXXX, XX.XKB). WebP file exists.
If fail:
"No glyph mapped"— Step 3 mapping missing or typo"Unknown domain"— Domain not inget_palette_colors()inpalettes.R- R package errors — Run
install.packages(c("ggplot2", "ggforce", "ggfx", "ragg", "magick"))first - Rendering crashes? Test glyph function interactively (see Step 2 fallback)
Step 6: Verify — Visual Inspection
Check rendered output meets quality standards.
-
Verify file exists and has reasonable size:
ls -la viz/public/icons/cyberpunk/<type-path>/<entity-id>.webp # Expected: 15-80 KB typical range -
Open WebP in image viewer. Check:
- Shape reads clearly at full size (1024x1024)
- Neon glow present but not overpowering
- Background transparent (no black/white rectangle)
- No clipping at canvas edges
-
Check at small sizes (icon renders at ~40-160px in force graph):
- Shape stays recognizable
- Detail does not turn to noise
- Glow does not overwhelm shape
Got: Clear, recognizable pictogram with even neon glow on transparent background.
If fail:
- Glow too strong: re-render with
--glow-sigma 2(default is 4) - Glow too weak: re-render with
--glow-sigma 8 - Shape unreadable small? Simplify glyph (fewer layers, bolder strokes, bump
.lw(s, base)base value) - Clipping at edges? Shrink shape dimensions or shift center
Step 7: Iterate — Refine if Needed
Adjust and re-render.
-
Common adjustments:
- Bolder strokes: bump
.lw(s, base)— trybase = 3.0or3.5 - More visible fill: bump alpha from 0.10 to 0.15-0.20
- Shape proportions: tune multipliers on
s(e.g.,20 * s->24 * s) - Add/remove detail layers: keep total layers 2-6 for best results
- Bolder strokes: bump
-
Re-render after changes:
# Delete the existing icon first, then re-render rm viz/public/icons/cyberpunk/<type-path>/<entity-id>.webp # Use the appropriate build command from Step 5 -
Satisfied? Verify manifest status shows
"done". Build script updates it on success.
Got: Final icon passes all verification checks from Step 6.
If fail: After 3+ iterations glyph still reads poorly? Consider completely different visual metaphor (back to Step 1).
Reference
Domain and Entity Color Palettes
All 58 domain colors (for skills) in viz/R/palettes.R (single source of truth). Agent and team colors also in palettes.R. Cyberpunk palette (hand-tuned neon colors) in get_cyberpunk_colors(). Viridis-family palettes auto-generated via viridisLite.
Look up color:
source("viz/R/palettes.R")
get_palette_colors("cyberpunk")$domains[["design"]] # skill domain
get_palette_colors("cyberpunk")$agents[["mystic"]] # agent
get_palette_colors("cyberpunk")$teams[["tending"]] # team
Adding new domain? Add to three places in palettes.R:
PALETTE_DOMAIN_ORDER(alphabetical)get_cyberpunk_colors()domains list- Run
bash viz/build.shto regenerate palettes, data, manifests
Glyph Function Catalog
See full catalog of available glyph functions in primitives source files:
- Skills:
viz/R/primitives.Rthroughviz/R/primitives_19.R(domain-grouped) - Agents:
viz/R/agent_primitives.R - Teams:
viz/R/team_primitives.R
Helper Functions
| Function | Signature | Purpose |
|---|---|---|
.lw(s, base) | (scale, base=2.5) | Scale-aware line width |
.aes(...) | alias for ggplot2::aes | Shorthand aesthetic mapping |
hex_with_alpha(hex, alpha) | (string, 0-1) | Add alpha to hex color |
brighten_hex(hex, factor) | (string, factor=1.3) | Brighten a hex color |
dim_hex(hex, factor) | (string, factor=0.4) | Dim a hex color |
Checks
- Glyph function follows
glyph_<name>(cx, cy, s, col, bright) -> list()signature - All dimensions use
* sscaling factor - Color strategy uses
colfor fills,brightfor outlines,hex_with_alpha()for transparency - Function placed in right primitives file for entity type and domain
- Glyph mapping entry added in right
*_glyphs.Rfile - Manifest entry added with right entity ID, path,
"status": "pending" - Build command runs without error (dry-run first)
- Rendered WebP exists at expected path
- File size in expected range (15-80 KB)
- Icon reads clearly at both 1024px and ~40px display sizes
- Transparent background (no solid rectangle behind glyph)
- Manifest status updated to
"done"after successful render
Pitfalls
- Forgetting
* s: Hard-coded pixel values break when scale changes. Always multiply bys. - Canvas origin confusion: (0,0) is bottom-left, not top-left. Higher
yvalues move UP. - Double glow: Renderer already applies
ggfx::with_outer_glow()to every layer. Do NOT add glow inside glyph function. - Too many layers: Each layer gets individual glow wrapping. More than 8 layers → slow rendering, noisy visuals.
- Mismatched IDs: Entity ID in glyph mapping, manifest, registry must all match exactly.
- JSON trailing commas: Manifest is strict JSON. No trailing comma after last array element.
- Missing domain color: Domain not in
get_cyberpunk_colors()inpalettes.R? Rendering errors. Add color first, then regenerate. - Wrong primitives file: Skills in domain-grouped
primitives*.R, agents inagent_primitives.R, teams inteam_primitives.R.
See Also
enhance-glyph— improve existing glyph's visual quality, fix rendering issues, add detail layersaudit-icon-pipeline— detect missing glyphs and icons, know what needs creatingrender-icon-pipeline— run full rendering pipeline end-to-endornament-style-mono— complementary AI-based image generation (Z-Image vs R-coded glyphs)ornament-style-color— color theory for glyph accent fill decisionscreate-skill— parent workflow triggering glyph creation when adding new skills
GitHub Repository
Verwandte Skills
content-collections
MetaDiese Skill bietet eine produktionsgetestete Einrichtung für Content Collections – ein TypeScript-first-Tool, das Markdown/MDX-Dateien in typsichere Datensammlungen mit Zod-Validierung umwandelt. Verwenden Sie ihn beim Erstellen von Blogs, Dokumentationsseiten oder inhaltsstarken Vite + React-Anwendungen, um Typsicherheit und automatische Inhaltsvalidierung zu gewährleisten. Er behandelt alles von der Vite-Plugin-Konfiguration und MDX-Kompilierung bis hin zur Deployment-Optimierung und Schema-Validierung.
polymarket
MetaDiese Fähigkeit ermöglicht es Entwicklern, Anwendungen mit der Polymarket-Prognosemärkte-Plattform zu erstellen, einschließlich API-Integration für Handel und Marktdaten. Sie bietet außerdem Echtzeit-Datenstreaming über WebSocket, um Live-Trades und Marktaktivitäten zu überwachen. Nutzen Sie sie zur Implementierung von Handelsstrategien oder zur Erstellung von Tools, die Live-Marktaktualisierungen verarbeiten.
creating-opencode-plugins
MetaDiese Fähigkeit unterstützt Entwickler dabei, OpenCode-Plugins zu erstellen, die in über 25 Ereignistypen wie Befehle, Dateien und LSP-Operationen eingreifen. Sie bietet die Plugin-Struktur, Event-API-Spezifikationen und Implementierungsmuster für JavaScript/TypeScript-Module. Nutzen Sie sie, wenn Sie den Lebenszyklus des OpenCode KI-Assistenten mit benutzerdefinierter ereignisgesteuerter Logik abfangen, überwachen oder erweitern müssen.
sglang
MetaSGLang ist ein hochperformantes LLM-Serving-Framework, das sich auf schnelle, strukturierte Generierung für JSON, Regex und agentenbasierte Workflows unter Verwendung seines RadixAttention-Prefix-Cachings spezialisiert. Es bietet deutlich schnellere Inferenz, insbesondere für Aufgaben mit wiederholten Präfixen, was es ideal für komplexe, strukturierte Ausgaben und Mehrfachdialoge macht. Wählen Sie SGLang gegenüber Alternativen wie vLLM, wenn Sie constrained decoding benötigen oder Anwendungen mit umfangreicher Präfix-Weitergabe entwickeln.
