Vtex Io Admin React
Apply when building VTEX IO admin-facing React interfaces under the admin builder. Covers VTEX Styleguide and Shoreline usage, admin page composition, data-heavy admin interactions, and keeping administrative interfaces consistent with the VTEX Admin environment. Use for settings pages, moderation tools, dashboards, or operational UIs inside VTEX Admin.
Install
/plugin marketplace add vtex/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vtex/skills --skill vtex-io-admin-reactgit clone --depth 1 https://github.com/vtex/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/exports/opencode/vtex-io-admin-react ~/.claude/skills/vtex-io-admin-reactPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Admin React Interfaces ## When this skill applies Use this skill when building administrative React interfaces for VTEX Admin experiences. - Settings pages - Moderation tools - Internal dashboards - Operational forms and tables Do not use this skill for: - storefront components - render-runtime blocks - route authorization design - backend service structure ## Decision rules - Use VTEX official design systems for admin interfaces. - Prefer `vtex.styleguide` as the default choice for VTEX IO admin apps published to customers. - Accept `@vtex/shoreline` as an official VTEX design system, especially in internal back-office contexts. - Prefer core Styleguide layout patterns such as `Layout`, `PageHeader`, and `PageBlock` for page composition. - Prefer Styleguide building blocks for common admin needs: `Table`, `Input`, `Dropdown`, `Toggle`, `Tabs`, `Modal`, `Spinner`, and `Alert`. - Keep admin screens focused on operational clarity rather than storefront styling concerns. - Prefer explicit loading, empty, and error states for data-heavy admin pages. - Use button loading states and toast-based feedback for async actions so users can tell when a mutation starts, succeeds, or fails. - Prefer internationalized messages over hardcoded admin copy so labels and feedback can stay consistent across stores and locales. - Use tables, forms, filters, and feedback patterns that align with VTEX Admin conventions.
Details
- Skill name
vtex-io-admin-react- Repository
- vtex/skills
- Path
exports/opencode/vtex-io-admin-react/SKILL.md- Repo updated
- 14 October 2026
FAQ
What does the Vtex Io Admin React skill do?
Apply when building VTEX IO admin-facing React interfaces under the admin builder. Covers VTEX Styleguide and Shoreline usage, admin page composition, data-heavy admin interactions, and keeping administrative interfaces consistent with the VTEX Admin environment. Use for settings pages, moderation tools, dashboards, or operational UIs inside VTEX Admin.
How do I install the Vtex Io Admin React skill?
Claude Code plugin: /plugin marketplace add vtex/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Vtex Io Admin React popular?
It lives in vtex/skills, which has 47 GitHub stars and 9 forks.
Related skills
Architecture Well Architected Commerce
47vtex/skills
Apply when scoping, reviewing, or documenting cross-cutting VTEX commerce architecture across storefront, IO, headless, marketplace, payments, or any other VTEX module. Grounds work in the Well-Architected Commerce framework—Technical Foundation (reliability, trust, integrity; security, infrastructure, compliance), Future-proof (innovation, simplicity, efficiency; scalable and adaptable solutions), and Operational Excellence (accuracy, accountability, data-driven improvement; process and customer experience). Routes implementation detail to product tracks (IO caching and paths, Master Data str
Faststore Storefront
47vtex/skills
Core coding rules and workflow for developing VTEX FastStore storefronts. Use when starting any FastStore development task, writing TypeScript/React components, creating section overrides, extending the BFF, or styling. Covers all primary conventions, safety rules, and the development workflow used across every FastStore project.
Headless Bff Architecture
47vtex/skills
Apply when designing or modifying a BFF (Backend-for-Frontend) layer, middleware, or API proxy for a headless VTEX storefront. Covers BFF middleware architecture, public vs private API classification, VtexIdclientAutCookie management, API key protection, and secure request proxying. Use for any headless commerce project that must never expose VTEX_APP_KEY or call private VTEX APIs from the browser.
Vtex Io React Apps
47vtex/skills
Apply when building React components under react/ or configuring store blocks in store/ for VTEX IO apps. Covers interfaces.json, contentSchemas.json for Site Editor, VTEX Styleguide for admin apps, and css-handles for storefront styling. Use for creating custom storefront components, admin panels, pixel apps, or any frontend development within the VTEX IO react builder ecosystem.
Headless Intelligent Search
47vtex/skills
Apply when implementing search functionality, faceted navigation, or autocomplete in a headless VTEX storefront. Covers product_search, autocomplete_suggestions, facets, banners, correction_search, and top_searches endpoints, plus analytics event collection. Use for any custom frontend that integrates VTEX Intelligent Search API for product discovery and search result rendering.
Vtex Io Render Runtime and Blocks
47vtex/skills
Apply when connecting React components to Store Framework blocks and render-runtime behavior in VTEX IO. Covers interfaces.json, block registration, block composition, and how storefront components become configurable theme blocks. Use for block mapping, theme integration, or reviewing whether a React component is correctly exposed to Store Framework.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.