Docs Seeker
avibebuilder/claude-prime
Fetch up-to-date documentation for any library, framework, API, or service into context.
Build consistent, accessible UIs in Rails using maquinacomponents.
$ npx skills add maquina-app/maquina_components --skill maquina-ui-standards -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install maquina-app/maquina_components maquina-ui-standards --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/maquina-app/maquina_components.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill .claude/skills/maquina-ui-standards && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "maquina-ui-standards" agent skill from https://github.com/maquina-app/maquina_components/tree/main/skill into .claude/skills/maquina-ui-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maquina-ui-standards", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/maquina-app/maquina_components/tree/main/skillType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add maquina-app/maquina_components --skill maquina-ui-standards -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install maquina-app/maquina_components maquina-ui-standards --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maquina-app/maquina_components.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skill .agents/skills/maquina-ui-standards && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maquina-ui-standards" agent skill from https://github.com/maquina-app/maquina_components/tree/main/skill into .agents/skills/maquina-ui-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maquina-ui-standards", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maquina-app/maquina_components --skill maquina-ui-standards -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install maquina-app/maquina_components maquina-ui-standards --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maquina-app/maquina_components.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skill .cursor/skills/maquina-ui-standards && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "maquina-ui-standards" agent skill from https://github.com/maquina-app/maquina_components/tree/main/skill into .cursor/skills/maquina-ui-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maquina-ui-standards", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/maquina-app/maquina_components.git --path skill--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add maquina-app/maquina_components --skill maquina-ui-standards -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install maquina-app/maquina_components maquina-ui-standards --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maquina-app/maquina_components.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skill .gemini/skills/maquina-ui-standards && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "maquina-ui-standards" agent skill from https://github.com/maquina-app/maquina_components/tree/main/skill into .gemini/skills/maquina-ui-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maquina-ui-standards", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install maquina-app/maquina_components maquina-ui-standardsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add maquina-app/maquina_components --skill maquina-ui-standards -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/maquina-app/maquina_components.git skills-src && mkdir -p .github/skills && cp -r skills-src/skill .github/skills/maquina-ui-standards && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "maquina-ui-standards" agent skill from https://github.com/maquina-app/maquina_components/tree/main/skill into .github/skills/maquina-ui-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maquina-ui-standards", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maquina-app/maquina_components --skill maquina-ui-standards -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install maquina-app/maquina_components maquina-ui-standards --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maquina-app/maquina_components.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skill .opencode/skills/maquina-ui-standards && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "maquina-ui-standards" agent skill from https://github.com/maquina-app/maquina_components/tree/main/skill into .opencode/skills/maquina-ui-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maquina-ui-standards", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
maquina-ui-standardsBuild consistent, accessible UIs in Rails using maquinacomponents.
Maquina UI Standards is an agent skill from maquina-app/maquina_components. Build consistent, accessible UIs in Rails using maquinacomponents. Use this skill when implementing UI for features, creating views, building forms, or reviewing UI specs. Triggers on view creation, UI implementation, form building, layout design, or mentions of maquinacomponents usage.
Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `QUICKSTART.md`, `README.md` and `references/component-catalog.md`).
It sits in Backend & APIs, covering Backend development. It works with shadcn/ui. The repository describes itself as: Modern UI components for Ruby on Rails, powered by TailwindCSS and Stimulus. The licence is MIT.
11 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 8a88019. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are erb and css).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Maquina UI Standards loads about 3.5k tokens when it runs, and up to ~31k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 633 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from maquina-app/maquina_components at commit 8a88019, republished under its MIT licence (© maquina-app). 633 words, ~3,536 tokens.
.claude/skills/maquina-ui-standards/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.Build production-quality Rails UIs with maquina_components — ERB partials styled with Tailwind CSS 4 and data attributes, inspired by shadcn/ui.
<%# Partial components %>
<%= render "components/card" do %>
<%= render "components/card/header" do %>
<%= render "components/card/title", text: "Title" %>
<% end %>
<% end %>
<%# Data-attribute components (forms) %>
<%= f.text_field :email, data: { component: "input" } %>
<%= f.submit "Save", data: { component: "button", variant: "primary" } %>| Need | Component | Why |
|---|---|---|
| Container with header/content/footer | Card | Structured content grouping |
| Important message to user | Alert | Draws attention, semantic variants |
| Status indicator | Badge | Compact, inline status |
| Data display | Table | Structured rows/columns |
| No data state | Empty | Consistent empty patterns |
| User actions menu | Dropdown Menu | Accessible, keyboard-navigable |
| Selection from options | Toggle Group | Visual, single/multi select |
| Selection from many options | Combobox | Searchable, filterable |
| Date selection (inline) | Calendar | Always-visible date picker |
| Date selection (popover) | Date Picker | Compact form date input |
| Page location | Breadcrumbs | Navigation context |
| Large result sets | Pagination | Pagy integration |
| App navigation | Sidebar | Collapsible, persistent state |
| Temporary notifications | Toast | Non-intrusive feedback |
| Form inputs | Form components | Consistent styling via data attrs |
| File | Content |
|---|---|
| component-catalog.md | All components with props, variants, examples |
| layout-patterns.md | Page structure, grids, responsive design |
| form-patterns.md | Forms, validation, field groups |
| turbo-integration.md | Frames, Streams, Morph with components |
| spec-checklist.md | UI implementation checklist for specs |
Components are small, composable building blocks. You have full flexibility in how you use them:
Option A: Use partials as-is — Render maquina_components partials directly for standard patterns.
Option B: Compress complexity — Wrap multiple partials into your own application-specific components that encode your conventions.
Option C: Copy and adapt — Copy component partials into your app and customize for specific needs.
<%# Option A: Direct partial usage %>
<%= render "components/card" do %>
<%= render "components/card/header" do %>
<%= render "components/card/title", text: @resource.name %>
<% end %>
<% end %>
<%# Option B: Application-specific wrapper %>
<%# app/views/components/_resource_card.html.erb %>
<%= render "components/card" do %>
<%= render "components/card/header", layout: :row do %>
<div>
<%= render "components/card/title", text: resource.name %>
<%= render "components/card/description", text: resource.summary %>
</div>
<%= render "components/card/action" do %>
<%= yield :actions if content_for?(:actions) %>
<% end %>
<% end %>
<%= render "components/card/content" do %>
<%= yield %>
<% end %>
<% end %>
<%# Usage: <%= render "components/resource_card", resource: @user do %>...content...<% end %>
<%# Option C: Copied and customized for booking-specific needs %>
<%# app/views/bookings/_booking_card.html.erb - your own component %>Choose the approach that best fits your use case. The goal is consistency within your application, not rigid adherence to a single pattern.
<%# ✅ GOOD: Compose from parts %>
<%= render "components/card" do %>
<%= render "components/card/header", layout: :row do %>
<div>
<%= render "components/card/title", text: @resource.name %>
<%= render "components/card/description", text: @resource.summary %>
</div>
<%= render "components/card/action" do %>
<%= link_to "Edit", edit_path, data: { component: "button", variant: "outline", size: "sm" } %>
<% end %>
<% end %>
<%= render "components/card/content" do %>
<!-- Content -->
<% end %>
<% end %>
<%# ❌ BAD: Trying to configure everything via props %>
<%= render "components/card",
title: @resource.name,
description: @resource.summary,
action_text: "Edit",
action_path: edit_path %>Always prefer inline field errors with a flash message over an alert containing a list of all validation errors.
<%# ✅ RECOMMENDED: Inline errors + flash %>
<%= form_with model: @user, data: { component: "form" } do |f| %>
<div data-form-part="group">
<%= f.label :email, data: { component: "label" } %>
<%= f.email_field :email, data: { component: "input" },
aria: { invalid: @user.errors[:email].any? } %>
<% if @user.errors[:email].any? %>
<p data-form-part="error"><%= @user.errors[:email].first %></p>
<% end %>
</div>
<%# Flash shows brief summary: "Please fix the errors below" %>
<% end %>
<%# ❌ AVOID: Alert with error list %>
<% if @user.errors.any? %>
<%= render "components/alert", variant: :destructive do %>
<ul>
<% @user.errors.full_messages.each do |msg| %>
<li><%= msg %></li>
<% end %>
</ul>
<% end %>
<% end %>Inline errors are more accessible — users see the problem next to the field that needs fixing. The flash provides a brief notification that something needs attention.
Every input should have appropriate HTML5 attributes for validation, accessibility, and mobile optimization:
| Attribute | Purpose | Example |
|---|---|---|
type | Correct keyboard, validation | email, tel, url, number |
required | Mark mandatory fields | required: true |
maxlength | Prevent overflow, guide user | maxlength: 100 |
minlength | Minimum input | minlength: 2 |
pattern | Custom validation | pattern: "[0-9]{10}" |
inputmode | Mobile keyboard hint | inputmode: "numeric" |
autocomplete | Autofill hints | autocomplete: "email" |
<%# ✅ GOOD: Complete input attributes %>
<%= f.email_field :email,
data: { component: "input" },
required: true,
maxlength: 254,
autocomplete: "email",
placeholder: "you@example.com" %>
<%= f.phone_field :phone,
data: { component: "input" },
required: true,
maxlength: 20,
pattern: "[+]?[0-9\\s\\-()]+",
inputmode: "tel",
autocomplete: "tel" %>
<%= f.text_field :name,
data: { component: "input" },
required: true,
minlength: 2,
maxlength: 100,
autocomplete: "name" %>
<%# ❌ BAD: Missing attributes %>
<%= f.text_field :name, data: { component: "input" } %>Components use data-component and data-*-part attributes. CSS targets these, not classes:
<%# Component identifies itself %>
<div data-component="card">
<div data-card-part="header">...</div>
<div data-card-part="content">...</div>
</div>
<%# Variants via data attributes %>
<%= render "components/badge", variant: :success do %>Active<% end %>
<%# Renders: <span data-component="badge" data-variant="success">Active</span> %>Form elements don't need partials — use data attributes directly:
<%= form_with model: @user, data: { component: "form" } do |f| %>
<div data-form-part="group">
<%= f.label :email, data: { component: "label" } %>
<%= f.email_field :email, data: { component: "input" } %>
</div>
<div data-form-part="actions">
<%= f.submit "Save", data: { component: "button", variant: "primary" } %>
</div>
<% end %>Use icon_for helper, which delegates to your app's icon system:
<%= icon_for :check, class: "size-4" %>
<%= icon_for :chevron_right, class: "size-4 text-muted-foreground" %>Colors come from CSS variables (shadcn/ui convention):
| Variable | Usage |
|---|---|
--primary / --primary-foreground | Primary actions, CTAs |
--secondary / --secondary-foreground | Secondary elements |
--muted / --muted-foreground | Subdued content |
--accent / --accent-foreground | Highlights |
--destructive / --destructive-foreground | Dangerous actions |
--card / --card-foreground | Card backgrounds |
--border | Borders |
--ring | Focus rings |
Read the feature spec. Map UI requirements to components:
Feature: User Dashboard
- Summary cards → Card (stats variant)
- User list → Table with Badge for status
- Empty state when no users → Empty
- Actions per row → Dropdown Menu
- Page navigation → PaginationDecide grid/layout before coding:
<%# Dashboard layout %>
<div class="space-y-6">
<%# Stats row %>
<div class="grid gap-4 md:grid-cols-2 lg:grid-cols-4">
<%= render "dashboard/stat_card", ... %>
</div>
<%# Main content %>
<%= render "components/card" do %>
...
<% end %>
</div>Use component catalog, follow composition patterns.
Run through spec-checklist.md before marking complete.
| ❌ Don't | ✅ Do Instead |
|---|---|
| Inline Tailwind for component styling | Use data attributes, let CSS handle it |
| Create custom card/alert/badge divs | Use maquina_components |
| Skip empty states | Always handle zero-data case |
| Hardcode button styles | Use data-component="button" |
| Forget loading/disabled states | Include all interaction states |
| Mix icon libraries | Use icon_for consistently |
| Nest components incorrectly | Follow documented composition |
| Skip accessibility attributes | Include ARIA labels, roles |
For the Haab project, these additional conventions apply:
Override theme variables in application.css:
:root {
--primary: oklch(0.467 0.175 3.95); /* Dusty Rose #BE185D */
--primary-foreground: oklch(0.985 0 0);
}<% variant = case booking.status
when "confirmed" then :success
when "pending" then :warning
when "cancelled", "no_show" then :destructive
else :secondary
end %>
<%= render "components/badge", variant: variant do %>
<%= t("enums.booking.status.#{booking.status}") %>
<% end %><%= render "components/badge", variant: :outline do %>
<%= format_money(service.price_cents) %>
<% end %><%# Use monospace for times %>
<span class="font-mono text-sm">
<%= l(booking.starts_at, format: :time) %>
</span><%= render "components/card" do %>
<%= render "components/card/header", layout: :row do %>
<div>
<%= render "components/card/title", text: t(".title") %>
<%= render "components/card/description", text: t(".description") %>
</div>
<%= render "components/card/action" do %>
<%= link_to new_resource_path, data: { component: "button", variant: "primary", size: "sm" } do %>
<%= icon_for :plus, class: "size-4 mr-1" %><%= t(".add") %>
<% end %>
<% end %>
<% end %>
<%= render "components/card/content" do %>
<!-- Content here -->
<% end %>
<% end %><%= render "components/table" do %>
<%= render "components/table/header" do %>
<%= render "components/table/row" do %>
<%= render "components/table/head" do %><%= t(".name") %><% end %>
<%= render "components/table/head" do %><%= t(".status") %><% end %>
<%= render "components/table/head", css_classes: "w-10" do %>
<span class="sr-only"><%= t(".actions") %></span>
<% end %>
<% end %>
<% end %>
<%= render "components/table/body" do %>
<% @items.each do |item| %>
<%= render "components/table/row" do %>
<%= render "components/table/cell" do %><%= item.name %><% end %>
<%= render "components/table/cell" do %>
<%= render "components/badge", variant: status_variant(item) do %>
<%= item.status.titleize %>
<% end %>
<% end %>
<%= render "components/table/cell" do %>
<%= render "shared/row_actions", item: item %>
<% end %>
<% end %>
<% end %>
<% end %>
<% end %><% if @items.empty? %>
<%= render "components/empty" do %>
<%= render "components/empty/header" do %>
<%= render "components/empty/media" do %>
<div class="flex h-16 w-16 items-center justify-center rounded-full bg-muted">
<%= icon_for :inbox, class: "size-8 text-muted-foreground" %>
</div>
<% end %>
<%= render "components/empty/title", text: t(".empty.title") %>
<%= render "components/empty/description", text: t(".empty.description") %>
<% end %>
<%= render "components/empty/content" do %>
<%= link_to t(".empty.action"), new_path, data: { component: "button", variant: "primary" } %>
<% end %>
<% end %>
<% end %>See individual reference files for complete documentation.
© maquina-app, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 7 other files (references) in skill of maquina-app/maquina_components.
Open the folder on GitHubat commit 8a88019
Maquina UI Standards next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Maquina UI Standards this skillmaquina-app/maquina_components | 141 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Docs Seekeravibebuilder/claude-prime | 120 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Billing SDKhashgraph-online/awesome-codex-plugins | 1.3k | — | ~3.5k | Automated safety check: Notes | Apache-2.0 | |
| Avoid AI Designsunkaifei/FlyCms | 656 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Flycms Devsunkaifei/FlyCms | 656 | — | ~827 | Automated safety check: Pass | MIT | |
| FbaZhongye1/KnowAgenticRAG | 135 | — | ~758 | Automated safety check: Pass | None |
avibebuilder/claude-prime
Fetch up-to-date documentation for any library, framework, API, or service into context.
hashgraph-online/awesome-codex-plugins
BillingSDK, the open-source React and shadcn component library for Dodo Payments billing UI.
sunkaifei/FlyCms
Audit and rewrite frontend UI to remove generic AI design patterns ("AI slop"), both the first-order defaults (purple gradients, Inter, a centered hero over three cards, untouched shadcn) and the…
sunkaifei/FlyCms
FlyCms 项目(backend/ Spring Boot 4.1.1 + frontend/ vue-vben-admin v5)的架构地图与开发规范总纲。凡在本仓库做任何开发——写后端接口、新增/修改模块、管理页面、数据库变更、修 bug、重构——都要先加载本 skill 再动手,即使用户只说"改一下""加个功能";前端登录/菜单/权限专项另见…
Zhongye1/KnowAgenticRAG
FastAPI Best Architecture (fba) project development guide. An agent skill from Zhongye1/KnowAgenticRAG.
agentfront/frontmcp
A skill your agent uses when customizing, branding, or replacing the built-in FrontMCP OAuth pages (the login, consent, federated-select, incremental-authorization, and error pages) with your own…
Works with
Categories
Build consistent, accessible UIs in Rails using maquinacomponents. Maquina UI Standards is an agent skill from maquina-app/maquina_components. Build consistent, accessible UIs in Rails using maquinacomponents.
Maquina UI Standards fits situations like: implementing UI for features; reviewing UI specs; UI implementation; mentions of maquinacomponents usage.
Run `npx skills add maquina-app/maquina_components --skill maquina-ui-standards -a claude-code`. Or copy the skill folder (skill in maquina-app/maquina_components) into .claude/skills/maquina-ui-standards in your project. Claude Code loads it when a task matches its description.
Run `npx skills add maquina-app/maquina_components --skill maquina-ui-standards -a codex`. Or copy the skill folder (skill in maquina-app/maquina_components) into .agents/skills/maquina-ui-standards in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add maquina-app/maquina_components --skill maquina-ui-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maquina-ui-standards, .gemini/skills/maquina-ui-standards, .github/skills/maquina-ui-standards and .opencode/skills/maquina-ui-standards in your project.
SKILL.md names no scripts, command-line tools or credentials: Maquina UI Standards is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Maquina UI Standards is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 27k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Maquina UI Standards: Docs Seeker (avibebuilder/claude-prime, 120 stars), Billing SDK (hashgraph-online/awesome-codex-plugins, 1.3k stars), Avoid AI Design (sunkaifei/FlyCms, 656 stars) and Flycms Dev (sunkaifei/FlyCms, 656 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
maquina-app (a GitHub organization) maintains it in maquina-app/maquina_components, which has 141 GitHub stars. The repository was last updated on September 27, 2026.
Source: maquina-app/maquina_components on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.