Loading...
Loading...
Found 1,738 Skills
Concise communication mode. Cuts ~60-70% of output tokens while keeping natural, readable English. Drops filler, hedging, and pleasantries but maintains grammar and sentence flow. Elaborate on request -- ask for detail and get it, then auto-return to concise. Use when user says "concise mode", "be concise", "less verbose", or invokes /concise. Also triggers when user requests token efficiency with readability.
Run a structured UI/UX consultation to either (a) co-design a project-specific design system and emit `design-spec.md`, (b) review an existing UI with prioritized fixes, or (c) emit compact do/don't rules for a surface. Triggers when the user wants to define / build / refine a design system or design tokens, asks for a design spec, asks for a full UI review of a screen / mockup / PR, or wants design rules for a surface type. Do NOT trigger for narrow one-off questions ("is this color OK?", "should this button be larger?") — answer those directly without invoking the consultation flow.
Refine text, screenshots, hand-drawn sketches, "Little Black" illustrations, or existing HTML relationship diagrams into minimal wireframes with teaching semantics; for relationship-dense diagrams, first write executable relationship structure specifications using Mermaid, then implement them as accessible, responsive inline SVGs, and simultaneously output reusable wireframe generation prompts. Used for comparison diagrams, architecture diagrams, flowcharts, interface or API diagrams, Agent collaboration diagrams, and state relationship diagrams in HTML Presentations, course pages, and web cards; activated when users request "semantic wireframes", "wireframe illustrations", "convert illustrations to SVG", "generate wireframe prompts", "draw GUI/LUI, Agent, task, or system relationships in cards", or require following the STYLE_DNA of course-design for teaching illustrations. Not applicable to photos, decorative posters, complex data charts, emotional hand-drawn illustrations, or direct editing of binary PPTX files.
Design structural visuals on Moda — diagrams, charts, and screen layouts: (1) diagrams and flowcharts (process, org chart, architecture, decision tree, swimlane, workflow), (2) 2x2 matrices, quadrant charts, market maps, and standalone data charts (bar/line/pie graphics), and (3) static UI wireframes and app/site screen mockups. Boxes-and-arrows intents only: a simple graphic that merely uses shapes — a quote card, a decorative visual, a circle with a caption — is moda-social. Produces anchored-connector diagrams, charts, and screen layouts on a live Moda canvas and exports png or pdf. A mockup is a picture of an interface — for a live hosted page use moda-website; a diagram or chart destined for an existing deck/document canvas stays with moda-deck, moda-one-pager, or moda-edit.
Ask which skill or flow fits your situation. A router over the docs/Agent-Note maintenance flow, the documentation governance run, the prose-and-docs tool layer, and the standalone git and game skills in this pack.
Record browser or Web UI interaction demos as optimized GIFs using the available browser tooling, state-based frame capture, and deterministic encoding, then publish to a dedicated assets branch when the task includes attaching the GIF to a pull request. Use when asked to make, record, or generate a GIF that demonstrates a browser workflow, and for every pull request that changes product-user-visible GUI behavior, which MUST include a GIF recorded from the pull request's real server and data flow.
Generate animated HTML pages for educational/popular science flowcharts, concept maps, and principle demonstrations. Use CSS/SVG to draw nodes and connections, supporting animation effects like flowing arrows, gradual appearance, and hover highlighting. Suitable for technical explanation, video popular science, and PPT illustration scenarios.
Use when designing, critiquing, or implementing forms, inputs, validation, checkout, registration, payment, or any data-entry flow.
Use eBPF for deep kernel-level observability — trace syscalls, network flows, and application behavior without code changes using Cilium, Tetragon, and bpftrace.
Decide when Git submodules are the right external-repo boundary, then choose one safe operator flow: add and pin, bootstrap recursively, sync to the recorded commit, advance a tracked branch, edit inside the submodule without detached-HEAD surprises, remove cleanly, or configure CI/hosted-platform checkout constraints. Use when the user asks about `.gitmodules`, `git submodule`, recursive clone/setup, pointer updates, detached HEAD, private submodules in CI, GitHub Pages submodule limits, or submodule vs subtree/vendoring/package delivery. Not for generic Git history cleanup or package-manager dependency delivery.
Prove a frontend feature actually works by driving it in a real browser and capturing screenshots + a short GIF as PR-ready proof, published so a pull request can embed it inline. Use when a frontend change is built and you want visual evidence it works before opening the PR: "verify this feature", "capture proof it works", "record the flow working", "prove the UI change", "/verifykit", or when a PR needs proof artifacts to attach.
When the user wants to create or improve an automated email sequence, drip campaign, welcome series, nurture flow, or lifecycle email program. Also use when the user says 'set up a welcome email,' 'build a drip campaign,' 'onboarding emails,' 'lifecycle emails,' 'nurture sequence,' or 'what emails should I send new users.' For cold outreach to prospects, see cold-email.