Agent skill

Components Architecture

by operately in operately/operately

Defines where UI components belong in Operately (TurboUI-first).

Custom licenceAuto-check passedFrontend & Design

Install Components Architecture

skills CLI
$ npx skills add operately/operately --skill components-architecture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install operately/operately components-architecture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/operately/operately.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/components-architecture .claude/skills/components-architecture && rm -rf skills-src

Use ~/.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/

Facts

Skill name
components-architecture
GitHub stars
577
Token cost
~2.5k tokens
SKILL.md length
1,133 words
Files
2
Skills in repo
9
Repo updated
First seen
Licence
Custom licence

At a glance

Defines where UI components belong in Operately (TurboUI-first).

  • Works in 4 steps: List every required control and… → Search turboui/src/index.tsx, relevant… → Compose the UI from those components.… → …
  • Migrating UI components
  • SKILL.md covers Architecture, Pure Components, App Bridge and Scenario 1: New UI Components, plus 2 more sections
  • Calls make

What it does

Components Architecture is an agent skill from operately/operately. Defines where UI components belong in Operately (TurboUI-first). Use when creating, changing, reviewing, or migrating UI components, adding features that need UI, or deciding whether to refactor legacy app UI in app/assets/js/components or app/assets/js/features. Covers pure TurboUI components, component reuse, the app bridge pattern, and legacy migration scenarios.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).

It sits in Frontend & Design. It works with Elixir. The repository describes itself as: The open source company operating system.

When your agent uses it

  • Migrating UI components
  • Adding features that need UI
  • Deciding whether to refactor legacy app UI in app/assets/js/components
  • App/assets/js/features

Example prompts

  • “Use the components-architecture skill to define where UI components belong in Operately (TurboUI-first)”
  • “/components-architecture”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. List every required control and interaction pattern: forms, fields, buttons, links, selectors, modals, empty states, validation, and…
  2. Search turboui/src/index.tsx, relevant component directories, and existing usages for matching components.
  3. Compose the UI from those components. Use raw interactive elements only when implementing a TurboUI primitive or when the inventory…
  4. If a raw , , , , dialog, link-like action, or validation message remains, document the reason in the implementation summary.

What it can do on your machine

Read from SKILL.md and the folder at commit c81d2bd. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Components Architecture loads about 2.5k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 1,133 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

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.

Safety

Auto-check passed

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.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,133 words (~2,500 tokens).

“All UI components belong in TurboUI as pure components. The app bridges the backend and TurboUI: it loads data, calls APIs, reads app contexts, and passes data and callbacks as props.”

— opening of SKILL.md by operately, Custom licence
name
components-architecture

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in .agents/skills/components-architecture of operately/operately.

  • SKILL.md
  • reference.md

Open the folder on GitHubat commit c81d2bd

Compare with similar skills

Components Architecture 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.

Components Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Components Architecture this skilloperately/operately577—~2.5kAutomated safety check: PassCustom licence
Phoenix LiveView Patternsgeorgeguimaraes/elixir-agent-tools184—~1.3kAutomated safety check: PassApache-2.0
Elixirsickn33/agentic-awesome-skills47k1 repos~2.1kAutomated safety check: PassMIT
Web Artifacts Builderanthropics/skills180k41 repos~769Automated safety check: PassApache-2.0
React Doctormakeplane/plane61k12 repos~657Automated safety check: PassAGPL-3.0
Impeccablebestofjs/bestofjs3.1k27 repos~2.6kAutomated safety check: PassMIT

Similar skills

  • Phoenix LiveView Patterns

    georgeguimaraes/elixir-agent-tools

    Guidance for building and debugging Phoenix web interfaces: where LiveView loads data, scopes, PubSub topics, external polling and component state.

    184 GitHub stars~1.3k tokensUpdated 18 days ago
    Backend & APIsAuto-check passed
  • Elixir

    sickn33/agentic-awesome-skills

    Language-specific super-code guidelines for elixir. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 1 repo~2.1k tokens
    MobileAuto-check passed
  • Web Artifacts Builder

    anthropics/skills

    Official

    Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.

    180k GitHub starsUsed in 41 repos~769 tokens
    Frontend & DesignAuto-check passed
  • React Doctor

    makeplane/plane

    Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.

    61k GitHub starsUsed in 12 repos~657 tokens
    Frontend & DesignAuto-check passed
  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 27 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Frontend & DesignAuto-check passed

More from operately/operately

All 9 skills in this repo
  • Ecto Migrations

    operately/operately

    Rules for Operately schema migrations (app/priv/repo/migrations/) and data migrations (app/lib/operately/data/change.ex).

    577 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • MCP Tools

    operately/operately

    Defines how to add Operately MCP tools (API-first wrappers).

    577 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Tanstack Query

    operately/operately

    Operately frontend data fetching with TanStack Query. An agent skill from operately/operately.

    577 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Writing Tests

    operately/operately

    Operately test layout, naming (.projections.json), factories, feature/e2e steps, external query/mutation auth specs, and how to run Elixir/API/JS/EE tests.

    577 GitHub stars~2.7k tokensUpdated today
    Auto-check: notes
  • Clean Code

    operately/operately

    Clean-code engineering standards for writing, refactoring, and reviewing code in any programming language.

    577 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Help Docs

    operately/operately

    Discover help documentation work from operately git history.

    577 GitHub stars~866 tokensUpdated today
    Auto-check passed

Works with

Questions about Components Architecture

What does Components Architecture do?

Defines where UI components belong in Operately (TurboUI-first). Components Architecture is an agent skill from operately/operately. Defines where UI components belong in Operately (TurboUI-first).

When should I use Components Architecture?

Components Architecture fits situations like: migrating UI components; adding features that need UI; deciding whether to refactor legacy app UI in app/assets/js/components; app/assets/js/features.

How do I install Components Architecture in Claude Code?

Run `npx skills add operately/operately --skill components-architecture -a claude-code`. Or copy the skill folder (.agents/skills/components-architecture in operately/operately) into .claude/skills/components-architecture in your project. Claude Code loads it when a task matches its description.

How do I install Components Architecture in Codex?

Run `npx skills add operately/operately --skill components-architecture -a codex`. Or copy the skill folder (.agents/skills/components-architecture in operately/operately) into .agents/skills/components-architecture in your project. Codex loads it when a task matches its description.

Can I use Components Architecture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add operately/operately --skill components-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/components-architecture, .gemini/skills/components-architecture, .github/skills/components-architecture and .opencode/skills/components-architecture in your project.

What does Components Architecture need to run?

Going by SKILL.md and its folder, Components Architecture needs the command-line tools its instructions call (make).

Does Components Architecture access the network?

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.

Is Components Architecture safe to install?

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.

What licence does Components Architecture use?

Components Architecture has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Components Architecture use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Components Architecture?

Skills that share tags, products or a category with Components Architecture: Phoenix LiveView Patterns (georgeguimaraes/elixir-agent-tools, 184 stars), Elixir (sickn33/agentic-awesome-skills, 47k stars), Web Artifacts Builder (anthropics/skills, 180k stars) and React Doctor (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Components Architecture?

operately (a GitHub organization) maintains it in operately/operately, which has 577 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.

Source: operately/operately on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.