Results for “edge”

Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections for visual canvases, mind maps, and flowcharts.

Use this skill for property tests for parsers, validators, transforms, state machines, edge cases. Trigger when the task involves programming work related to Property Based Testing, implementation, audits, debugging, strategy, or validation.

Transforms earnest content into playful, satirical material using the voice and techniques of Eric Idle, including musical comedy, wordplay, and cheerful subversion.

Defines a structured eval-driven development workflow with define, implement, and verify phases, including capability, behavior, and non-functional checks, plus optional swarm mode for parallel evaluation.

Embody the voice and methodology of Andy Grove for strategic management advice, including frameworks for strategic inflection points, 10X forces, and high-output management.

Design user journeys and task flows for a product concept or MVP. Use when the team needs primary flows, branch conditions, edge cases, onboarding paths, and end-to-end user movement before screen planning or UI implementation.

Expert texture artist specializing in PBR workflows, Substance suite, Quixel Mixer, and hand-painted techniques for games and film productionUse when "texture artist, PBR textures, Substance Painter, Substance Designer, Quixel Mixer, normal map, roughness map, metallic map, albedo texture, base color map, texture baking, bake normal, texel density, trim sheet, texture atlas, channel packing, material layering, wear and tear, edge wear, hand painted texture, stylized texture, UDIM workflow, height map vs normal, color ID map, material ID, texture seams, tiling texture, seamless texture, texture, pbr, substance-painter, substance-designer, quixel, megascans, normal-map, roughness, metallic, albedo, uv-mapping, baking, trim-sheet, material, hand-painted, stylized, photorealistic, game-art, 3d-art" mentioned.

Local CLI issue tracker for todos, follow-ups, structured records, and the canonical pattern for decomposing multi-step work into a parent + subissues with acceptance criteria, dependency edges, and priority. Use when the user mentions a task to remember, a bug to track, an open question, anything that needs to outlive the current turn, or when planning multi-heartbeat work that needs `chainlink issue ready`-driven pickup across sessions. Includes guidance on writing descriptions future-you can act on (handles, success path, failure path) and idempotency tactics for actions that might fire twice (boundary firing, overlapping heartbeats, retried subagent completion). Pairs with five-whys (chainlink is the storage backend for RCA trees). Storage is local — issues live under a `.chainlink/` directory in the operator's repo.