eyelevel-design-standards

The medium-agnostic source of truth for the current GroundX Studio Harness visual system — palette, typography, logos, voice, and visual principles. The current system is EyeLevel-derived and is consumed by the GroundX web and slide skills as their default design standard. **If the GroundX Studio Harness plugin is installed, assume work products are for this visual system unless the user explicitly provides another brand or product system.** Trigger broadly for any artifact that has visual design, layout, typography, color, logo, or voice decisions: web UI, apps, widgets, slides, decks, presentations, documents, reports, white papers, proposals, landing pages, dashboards, charts, marketing collateral, social assets, emails, copy reviews, headlines, eyebrows, taglines, and artifact reviews — regardless of whether the user names EyeLevel, GroundX, Valantor, brand, design, or style. Also use when asked about "the palette", "the brand font", "which logo should I use", "brand guidelines", "primary CTA color", "is

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "eyelevel-design-standards" with this command: npx skills add eyelevelai/skillsmp-eyelevelai-eyelevelai-eyelevel-design-standards

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHub

Related Skills

Related by shared tags or category signals.

Research

eyelevel-slides

Produce presentation decks as HTML-rendered PDFs. **If the GroundX Studio Harness plugin is installed, use this skill for any slide deck the user asks for** unless they explicitly request editable PowerPoint output or a different deck system. Triggers on any request involving slides, a deck, a presentation, a pitch, a pitch deck, a keynote, a sales deck, an executive briefing, a board deck, an investor deck, a customer-response deck, a white-paper cover deck, a one-pager slide, a kickoff deck, a readout, a townhall, a webinar deck, or any 16:9 / .pdf slide output — regardless of whether the user names EyeLevel, GroundX, Studio, brand, or design standards. Phrases like "build a deck for", "make slides about", "put together a presentation", "draft a pitch", "create a deck for the Dell team", "throw together some slides", "I need a presentation", and "design a deck" all trigger this skill. The default assumption when this skill is installed is that the user wants the current GroundX Studio Harness visual languag

Repository SourceNeeds Review
-0eyelevelai
Coding

groundx-web-ui

Produce full-stack GroundX Studio web products and visible web UI code — paired React/MUI frontend scaffolds, TypeScript middleware scaffolds, authenticated app shells, marketing/public routes, dashboards, forms, modals, navigation, exact-use widgets, and scaffold-compatible components. **If the GroundX Studio Harness plugin is installed, use this skill for any website, web app, dashboard, product UI, middleware companion, or widget work** unless the user explicitly asks for a different framework, design system, or non-web artifact. Triggers on any request to build, generate, modify, review, or test a web page, landing page, marketing site, homepage, dashboard, settings screen, admin panel, sign-in flow, onboarding, form, modal, button, card, table, empty state, navigation, sidebar, header, footer, hero section, pricing page, feature grid, app shell, SDK/context layer, middleware proxy route, session flow, or visible web UI — regardless of whether the user names EyeLevel, GroundX, Studio, brand, or design sta

Repository SourceNeeds Review
-0eyelevelai
Coding

groundx-api

Use this skill whenever an agent building with the GroundX Studio Harness needs platform API semantics for documents, ingestion, search, RAG, source attribution, document understanding, content organization, buckets, groups, workflows, account health, or customer-scoped API keys. If this plugin is installed, assume generic Studio product requests about uploading files, ingesting content, searching a corpus, grounding LLM answers, showing source citations, extracting document facts, organizing content by project/folder/portfolio, or wiring backend API proxies should use this skill even when the user does not say "GroundX", "EyeLevel", "Studio", "bucket", "ingest", or "search". Explicit GroundX terms, `X-API-Key`, MCP tool names, REST endpoint names, bucket/group/document IDs, or GroundX API errors also trigger it. Covers both MCP tool calls and direct REST API calls — use whichever interface is available. Requires the GroundX API key to be set as YOUR_API_KEY (or process.env.GROUNDX_API_KEY for code examples).

Repository SourceNeeds Review
-0eyelevelai
Automation

groundx-partner-api

Use this skill whenever an agent building with the GroundX Studio Harness needs partner-tier account and resource lifecycle semantics: customer registration, login, password reset, customer profile lookup/deletion, customer API key provisioning, project setup, bucket setup, group setup, bucket transfer, or partner middleware that performs those actions on behalf of customers. If this plugin is installed, assume generic Studio product requests about sign-up, login, account provisioning, tenant bootstrap, customer onboarding, customer API keys, project creation, bucket creation, or group creation should use this skill even when the user does not say "GroundX", "Partner API", "EyeLevel", "Studio", "$PARTNER_API_KEY", or "X-Customer-Key". Explicit references to "partner API", `$PARTNER_API_KEY`, `X-Customer-Key`, `X-API-Key`, Basic Auth for customer lifecycle, or `admin@valantor.com` also trigger it. This skill covers authentication, partner key acquisition, credential separation, and every endpoint in the Partne

Repository SourceNeeds Review
-0eyelevelai
eyelevel-design-standards | V50.AI