SkillAgentSearch skills...

RULE

Use the local UI component library (`@/ui/*`) consistently (Angular standalone + Tailwind/DaisyUI).

Install / Use

npx skills add WilliamChelman/sheath

Installs into whichever agent you are using.

About this skill
📐

Cursor Rules

Cursor IDE rules (v2)

Quality Score

61/100

Supported Platforms

Cursor

Our assessment of RULE

RULE scores 61/100 on our quality scale, 4085th of 4,617 Development & Engineering skills we index.

Its Cursor Rules is 3.2 KB long, split into 7 sections with 7 code examples: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
18/20
Description
12/15
Adoption
0/20
Freshness
5/15

Maintenance, license and trust

  • We could not determine when the repository was last updated.
  • Our last check on 2026-10-20 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

RULE compared with similar skills

All 4 of these similar skills score higher than RULE; compare them before choosing.

SkillScoreStarsUpdatedFormat
RULE (this skill)by WilliamChelman610—Cursor Rules
taste-skillby Leonxlnx100110.6ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10069.8ktodayCLAUDE.md
claude-howtoby luongnv8910046.6k2d agoCLAUDE.md
algorithmic-artby anthropics100177.9k44d agoSKILL.md

Frequently asked questions

How do I install RULE?
Run npx skills add WilliamChelman/sheath. The install tabs above show the steps for each supported agent.
Which AI agents does RULE work with?
It is written for Cursor, as a Cursor Rules file. Other agents that read the same format can often use it too.
Is RULE safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is RULE still maintained?
We could not determine when the repository was last updated.

description: Use the local UI component library (@/ui/*) consistently (Angular standalone + Tailwind/DaisyUI). globs:

  • apps/web-app/src/**/*.ts
  • apps/web-app/src/**/*.html alwaysApply: false

UI components: import + usage rules

Import rules (mandatory)

  • Always import UI building blocks from the barrel exports:
    • @/ui/badge
    • @/ui/card
    • @/ui/forms
    • @/ui/menu
  • Do not deep-import from apps/web-app/src/app/ui/** (keeps refactors easy and prevents circular deps).

Example:

import { BadgeComponent } from '@/ui/badge';
import { CardComponent } from '@/ui/card';
import { TextInputComponent, SelectComponent, type SelectOption } from '@/ui/forms';
import {
  DropdownContainerDirective,
  MenuTriggerDirective,
  MenuPanelComponent,
  MenuItemDirective,
} from '@/ui/menu';

Component conventions (follow existing repo patterns)

  • Standalone components only: add used UI components/directives to imports: [].
  • Signals-first: use input(), model(), computed() and built-in control flow (@if, @for).
  • Styling: use Tailwind utilities + DaisyUI classes in templates; avoid component CSS files.

app-badge

  • Use for status tags, counts, and category labels.
  • Prefer the typed inputs (color, variant, size) over hand-rolled class strings.
<app-badge color="success" variant="outline" size="sm" label="Available" />
<app-badge color="warning" variant="solid">Coming Soon</app-badge>

app-card

  • Prefer app-card for consistent card padding/typography.
  • Use inputs instead of duplicating markup (title, subtitle, variant, fullHeight).
<app-card title="Token Generator" subtitle="Create printable monster tokens" variant="soft">
  <div class="flex gap-2">
    <app-badge color="primary" variant="outline">PNG</app-badge>
    <app-badge color="secondary" variant="outline">PDF</app-badge>
  </div>
</app-card>

Forms (@/ui/forms)

General:

  • Use the provided form controls instead of raw <input class="input ..."> when possible.
  • Bind using signals (model()), not mutable component fields.

app-text-input:

<app-text-input
  label="Name"
  placeholder="e.g. Goblin Boss"
  [maxLength]="32"
  [helperText]="'Shown on the token'"
  [(value)]="name"
/>

app-select:

options: SelectOption[] = [
  { value: 'small', label: 'Small' },
  { value: 'medium', label: 'Medium' },
];
size = model<'small' | 'medium'>('medium');
<app-select label="Size" [options]="options" [(value)]="size" />

Menus (@/ui/menu)

Use the wrapper directives/components so menus look and behave consistently:

  • appDropdownContainer
  • appMenuTrigger + [appMenuTriggerFor]
  • app-menu-panel
  • appMenuItem
<div appDropdownContainer align="end">
  <button appMenuTrigger [appMenuTriggerFor]="menu" class="btn btn-ghost btn-circle">
    Menu
  </button>

  <ng-template #menu>
    <app-menu-panel width="12rem">
      <li class="menu-title">Actions</li>
      <li><button appMenuItem (click)="doThing()">Do thing</button></li>
      <li><a appMenuItem routerLink="/tools">Go to tools</a></li>
    </app-menu-panel>
  </ng-template>
</div>

Related Skills

View on GitHub
GitHub Stars0
CategoryDevelopment
UpdatedNaNy ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low