Agent skill

Ban Pattern

Install Ban Pattern

skills CLI

$ npx skills add tsubotax/melta-ui --skill ban-pattern -a claude-code

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

GitHub CLI

$ gh skill install tsubotax/melta-ui ban-pattern --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/tsubotax/melta-ui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ban-pattern .claude/skills/ban-pattern && 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/

Paste into Claude Code

Install the "ban-pattern" agent skill from https://github.com/tsubotax/melta-ui/tree/main/skills/ban-pattern into .claude/skills/ban-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ban-pattern", 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

$skill-installer install https://github.com/tsubotax/melta-ui/tree/main/skills/ban-pattern

Type 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.

skills CLI

$ npx skills add tsubotax/melta-ui --skill ban-pattern -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install tsubotax/melta-ui ban-pattern --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tsubotax/melta-ui.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ban-pattern .agents/skills/ban-pattern && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ban-pattern" agent skill from https://github.com/tsubotax/melta-ui/tree/main/skills/ban-pattern into .agents/skills/ban-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ban-pattern", 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.

skills CLI

$ npx skills add tsubotax/melta-ui --skill ban-pattern -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install tsubotax/melta-ui ban-pattern --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tsubotax/melta-ui.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ban-pattern .cursor/skills/ban-pattern && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ban-pattern" agent skill from https://github.com/tsubotax/melta-ui/tree/main/skills/ban-pattern into .cursor/skills/ban-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ban-pattern", 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

$ gemini skills install https://github.com/tsubotax/melta-ui.git --path skills/ban-pattern

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add tsubotax/melta-ui --skill ban-pattern -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install tsubotax/melta-ui ban-pattern --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tsubotax/melta-ui.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ban-pattern .gemini/skills/ban-pattern && rm -rf skills-src

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

Paste into Gemini CLI

Install the "ban-pattern" agent skill from https://github.com/tsubotax/melta-ui/tree/main/skills/ban-pattern into .gemini/skills/ban-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ban-pattern", 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.

GitHub CLI

$ gh skill install tsubotax/melta-ui ban-pattern

Installs 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).

skills CLI

$ npx skills add tsubotax/melta-ui --skill ban-pattern -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/tsubotax/melta-ui.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ban-pattern .github/skills/ban-pattern && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "ban-pattern" agent skill from https://github.com/tsubotax/melta-ui/tree/main/skills/ban-pattern into .github/skills/ban-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ban-pattern", 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.

skills CLI

$ npx skills add tsubotax/melta-ui --skill ban-pattern -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install tsubotax/melta-ui ban-pattern --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tsubotax/melta-ui.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ban-pattern .opencode/skills/ban-pattern && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ban-pattern" agent skill from https://github.com/tsubotax/melta-ui/tree/main/skills/ban-pattern into .opencode/skills/ban-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ban-pattern", 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.

Facts

Skill name: ban-pattern
GitHub stars: 202
Token cost: ~1.4k tokens
SKILL.md length: 265 words
Files: 1
Skills in repo: 3
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 5 steps: パターンを特定する → 既存ルールと重複がないか確認する → 禁止ルールを登録する → …
User says AIっぽい
SKILL.md covers 手順 and トラブルシューティング
Calls npm

What it does

Ban Pattern is an agent skill from tsubotax/melta-ui. Register AI-generated-looking UI patterns as prohibited rules in the design system. Use when user says "AIっぽい", "AI臭い", "これ禁止", "このパターンやめたい", "ban this pattern", "add to prohibited", or points out a generic/cookie-cutter UI element.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Design systems. It works with Tailwind CSS. The repository describes itself as: 人間にも、AIにも、読めるデザインシステム — AI-Ready Design System for Claude Code & Cursor. The licence is MIT.

When your agent uses it

User says AIっぽい
Ban this pattern
Add to prohibited
Points out a generic/cookie-cutter UI element

Example prompts

“ban this pattern”
“add to prohibited”
“/ban-pattern”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

パターンを特定する
既存ルールと重複がないか確認する
禁止ルールを登録する
既存サンプルを走査・修正する
結果を報告する

What it can do on your machine

Read from SKILL.md and the folder at commit a44f290. 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:
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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

Ban Pattern loads about 1.4k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 265 words of instructions outside code blocks.

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

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

The full file from tsubotax/melta-ui at commit a44f290, republished under its MIT licence (© tsubotax). 265 words, ~1,434 tokens.

Download SKILL.mdSave it as .claude/skills/ban-pattern/SKILL.md (or your agent's skills folder).

name: ban-pattern
description: Register AI-generated-looking UI patterns as prohibited rules in the design system. Use when user says "AIっぽい", "AI臭い", "これ禁止", "このパターンやめたい", "ban this pattern", "add to prohibited", or points out a generic/cookie-cutter UI element.
user-invocable: true

AI生成UIに頻出する「それっぽい」装飾パターンを特定し、DS全体の禁止ルールとして登録する。

手順

Step 1: パターンを特定する

ユーザーの説明（テキスト or スクリーンショット）から、禁止対象のパターンを特定する。

以下を明確にする:

何が問題か: どの視覚要素がAI生成っぽいのか
該当する Tailwind クラス / CSS: 具体的な実装パターン（例: border-l-4, bg-gradient-to-r）
代替パターン: DS準拠の代わりの実装

不明点があれば AskUserQuestion で確認する。推測で進めない。

Step 2: 既存ルールと重複がないか確認する

以下を読み込む:

design/contracts/rules.json の rules[]（SSOT。機械可読版。同じ pattern / 趣旨のルールが無いか）
foundations/prohibited.md の「AI生成パターンの排除」セクション（人間向けミラー）

既に同じ or 類似のルールが存在する場合は、ユーザーに報告して既存ルールの更新で対応するか確認する。

Step 3: 禁止ルールを登録する

SSOT は design/contracts/rules.json。CI / MCP check_rule / PostToolUse hook はすべて rules.json を参照する。ここに機械可読ルールを足して初めて「ban → 即 enforcement」が成立する。 prohibited.md は人間向けの解説ミラーであり、enforcement の実体ではない。順序厳守:

3-1. `design/contracts/rules.json` — 機械可読ルールを追加（最優先）

rules[] 配列にルールオブジェクトを 1 件追加する。スキーマは design/schemas/rule.schema.json。

detector の選び方（これで自動検出されるか・人手参照に留まるかが決まる）:

detector	いつ使う	必須フィールド	例
`tailwind-class`	単一の固定クラスを禁止	`pattern`（クラス名）	`border-l-4`, `shadow-2xl`
`tailwind-class-prefix`	前方一致で複数バリアントを一網打尽	`pattern`（接頭辞）。任意値回避経路があれば `prefixPatterns` も	`bg-gradient-`
`tailwind-class-segment`	クラスを `-` 分割したセグメント一致（色名等）	`matchPatterns`（セグメント配列）、`pattern: null`	`purple`/`violet`
`manual`	静的検出が原理的に不能（文脈判断）	`pattern: null`、`contractLint: "skip"`	「色だけで状態を伝達」

フィールド規約:

id: 大文字スネーク（^[A-Z][A-Z0-9_]+$）。AI生成装飾は AI_NO_*、特定コンポーネントは <COMPONENT>_NO_*
category: ai-pattern（AI装飾）/ または該当カテゴリ（color spacing form 等、schema の enum 参照）
severity: error（明確なNG）/ warn（文脈次第・段階導入）
alternative: DS準拠の代替実装（必須・具体的に）
contractLint: enforce（自動検出可・contract も検査）/ warn / skip（manual・html-attr・文脈依存）

テンプレ（自動検出する典型の AI パターン）:

json

{
  "id": "AI_NO_GLASS_BLUR",
  "category": "ai-pattern",
  "severity": "error",
  "description": "ガラスモーフィズム（backdrop-blur）はAI生成UIの典型tell。安っぽく散漫に見える",
  "detector": "tailwind-class-prefix",
  "pattern": "backdrop-blur",
  "alternative": "不透明な bg-white / bg-slate-50 + border border-slate-200 で面を作る",
  "contractLint": "enforce"
}

テンプレ（manual = 文脈判断が要るもの）:

json

{
  "id": "FORM_NO_PLACEHOLDER_AS_LABEL",
  "category": "form",
  "severity": "warn",
  "description": "プレースホルダーのみでラベル省略は入力開始で消え目的がわからなくなる",
  "detector": "manual",
  "pattern": null,
  "alternative": "<label> を必ず使用",
  "contractLint": "skip"
}

3-2. 人間向けドキュメントと件数の整合

foundations/prohibited.md の該当セクション（AIパターンなら「## AI生成パターンの排除」、無ければ ## コンポーネント の直前に同テンプレで新設）のテーブルに prose 行を追加する:
```
| 禁止パターン（具体的な Tailwind クラス） | 理由（なぜAI生成っぽいか） | 代替（DS準拠の実装） |
```
detector が manual のルールは orphan 0 検証の対象なので、行末に （HTMLコメント・レンダリング不可視・表非破壊）を必ず付け、drift-check が参照経路を見つけられるようにする。 auto 系（tailwind-*）は contract / lint で到達できるためコメントは任意。
ルール総数が 1 件増えるので、prose に書かれた件数を全て +1 する: DESIGN.md（全ルール（N 件））/ README.md（N 禁止ルール N ルール 複数箇所）/ AGENTS.md（N 禁止ルール N ルール）/ README.en.md（英語: N prohibition rules / N rules）。どこが古いかは 3-4 の design:drift がファイル名・数値付きで指摘するので（英語入口の数値整合も検証する）、それに従って直す。
パターンが特定コンポーネントに紐づく場合、該当 components/*.md の禁止事項にも追記する（任意）。

3-3. 生成ビューを再生成する

bash

npm run design:build            # llms.txt / llms-full.txt / metadata/components.json
npm run design:update-showcase  # docs/index.html の数値
npm run design:coverage         # README の検証カバレッジ表（manual を足すと manual 件数が動く）

3-4. 検証 — 「即 CI / MCP 反映」を自分で確認する

bash

npm run design:drift   # 件数 drift を全部指摘。NO DRIFT になるまで 3-2 を直す
npm run design:check   # rules.json スキーマ + contract lint が PASSED であること

どちらも green になって初めて登録完了。落ちたら指摘に従って直してから報告する。
auto detector のルールは、違反 HTML を 1 つ作って npm run design:lint-generated -- <file> で実際に発火することを確認すると「enforcement に乗った」証拠になる（任意・デモ向け）。

Step 4: 既存サンプルを走査・修正する

examples/ と docs/ 配下のHTMLファイルを Grep で走査し、禁止パターンに該当する実装が既にないか確認する。

該当がある場合:

全箇所をリストアップしてユーザーに報告する
ユーザーの承認後、DS準拠の代替パターンに修正する

該当がない場合:

「既存サンプルに該当なし」と報告する

Step 5: 結果を報告する

以下のフォーマットで報告する:

## 禁止パターン登録完了

**ルール ID**: `[RULE_ID]`（rules.json に追加 → CI / MCP check_rule / hook で即 enforcement）
**パターン**: [禁止したパターンの説明]
**detector**: `[tailwind-class / -prefix / -segment / manual]`（[自動検出 / 人手参照のみ]）
**代替**: `[DS準拠の代替]`

### 更新ファイル
- design/contracts/rules.json — 機械可読ルールを追加（SSOT・enforcement の実体）
- foundations/prohibited.md — 人間向け解説に追加（[manual の場合: <!-- RULE_ID --> 付き]）
- DESIGN.md / README.md / AGENTS.md — ルール件数を N→N+1
- llms / docs/index.html / README カバレッジ表 — 再生成

### 検証
- npm run design:drift — NO DRIFT ✅
- npm run design:check — PASSED ✅
- [auto の場合: npm run design:lint-generated で発火確認]

### サンプル修正
- [修正した箇所のリスト or 「該当なし」]

トラブルシューティング

問題	対処
`design/contracts/rules.json` のスキーマ検証で落ちる	`design:check` のエラー文に従う。`id` は大文字スネーク、detector に応じた必須フィールド（tailwind-class→pattern / segment→matchPatterns / manual→pattern:null + contractLint:skip）を確認
`design:drift` が件数 mismatch を出す	指摘されたファイル・数値の「N ルール」「全ルール（N 件）」を実数に直し、`design:build` / `update-showcase` / `design:coverage` を再実行
manual ルールを足したら orphan 0 検証で落ちる	prohibited.md（または該当 foundations/patterns md）の行末に `<!-- RULE_ID -->` を付けて参照経路を作る
禁止パターンの Tailwind クラスが特定できない	AskUserQuestion でスクリーンショットや具体例を求める。単一クラスでなく色名なら `tailwind-class-segment`、接頭辞バリアント群なら `tailwind-class-prefix` を検討
既存ルールと部分的に重複する	既存ルールの拡張（pattern / matchPatterns の追加）で対応するか、新規ルールにするかをユーザーに確認する

Files

Just SKILL.md in skills/ban-pattern of tsubotax/melta-ui.

Open the folder on GitHubat commit a44f290

Compare with similar skills

Ban Pattern 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.

Ban Pattern compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ban Pattern this skilltsubotax/melta-ui	202	—	~1.4k	Automated safety check: Pass	MIT	11 days ago
UI StylingOhh-889/skyroc	795	13 repos	~2.5k	Automated safety check: Pass	MIT	1 mo ago
Design SystemOhh-889/skyroc	795	11 repos	~1.7k	Automated safety check: Pass	MIT	1 mo ago
Creative Tim UI Blockscreativetimofficial/ui	12k	—	~2.1k	Automated safety check: Notes	MIT	6 mo ago
Scalar Design Systemscalar/scalar	16k	—	~2.7k	Automated safety check: Pass	MIT	today
Activepieces Design Systemactivepieces/activepieces	25k	—	~3.6k	Automated safety check: Pass	Custom licence	today

Similar skills

UI Styling
Ohh-889/skyroc
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.
795 GitHub starsUsed in 13 repos~2.5k tokens
Frontend & DesignAuto-check passed
Design System
Ohh-889/skyroc
Token architecture, component specifications, and slide generation.
795 GitHub starsUsed in 11 repos~1.7k tokens
Frontend & DesignAuto-check passed
Creative Tim UI Blocks
creativetimofficial/ui
Helps install, generate and review Creative Tim UI blocks: shadcn/ui-based React and Tailwind sections that follow a restrained, production-minded design philosophy.
12k GitHub stars~2.1k tokensUpdated 6 mo ago
Frontend & DesignAuto-check: notes
Scalar Design System
scalar/scalar
Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library.
16k GitHub stars~2.7k tokensUpdated today
Frontend & DesignAuto-check passed
Activepieces Design System
activepieces/activepieces
Design system for Activepieces (open-source AI automation platform, "open source replacement for Zapier").
25k GitHub stars~3.6k tokensUpdated today
Frontend & DesignAuto-check passed
Coss
crafter-station/petdex
Helps implement coss UI components correctly. An agent skill from crafter-station/petdex.
4.2k GitHub stars~1.4k tokensUpdated 9 days ago
Frontend & DesignAuto-check passed

Questions about Ban Pattern

What does Ban Pattern do?

Register AI-generated-looking UI patterns as prohibited rules in the design system. Ban Pattern is an agent skill from tsubotax/melta-ui. Register AI-generated-looking UI patterns as prohibited rules in the design system.

When should I use Ban Pattern?

Ban Pattern fits situations like: user says AIっぽい; ban this pattern; add to prohibited; points out a generic/cookie-cutter UI element.

How do I install Ban Pattern in Claude Code?

Run `npx skills add tsubotax/melta-ui --skill ban-pattern -a claude-code`. Or copy the skill folder (skills/ban-pattern in tsubotax/melta-ui) into .claude/skills/ban-pattern in your project. Claude Code loads it when a task matches its description.

How do I install Ban Pattern in Codex?

Run `npx skills add tsubotax/melta-ui --skill ban-pattern -a codex`. Or copy the skill folder (skills/ban-pattern in tsubotax/melta-ui) into .agents/skills/ban-pattern in your project. Codex loads it when a task matches its description.

Can I use Ban Pattern 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 tsubotax/melta-ui --skill ban-pattern -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ban-pattern, .gemini/skills/ban-pattern, .github/skills/ban-pattern and .opencode/skills/ban-pattern in your project.

What does Ban Pattern need to run?

Going by SKILL.md and its folder, Ban Pattern needs the command-line tools its instructions call (npm).

Does Ban Pattern access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Ban Pattern 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 Ban Pattern use?

Ban Pattern is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ban Pattern use?

About 1.4k tokens (SKILL.md is roughly 5.7k 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 Ban Pattern?

Skills that share tags, products or a category with Ban Pattern: UI Styling (Ohh-889/skyroc, 795 stars), Design System (Ohh-889/skyroc, 795 stars), Creative Tim UI Blocks (creativetimofficial/ui, 12k stars) and Scalar Design System (scalar/scalar, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ban Pattern?

tsubotax (a GitHub user) maintains it in tsubotax/melta-ui, which has 202 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 27, 2026.

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

Ban Pattern

Install Ban Pattern

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

手順

Step 1: パターンを特定する

Step 2: 既存ルールと重複がないか確認する

Step 3: 禁止ルールを登録する

3-1. `design/contracts/rules.json` — 機械可読ルールを追加（最優先）

3-2. 人間向けドキュメントと件数の整合

3-3. 生成ビューを再生成する

3-4. 検証 — 「即 CI / MCP 反映」を自分で確認する

Step 4: 既存サンプルを走査・修正する

Step 5: 結果を報告する

トラブルシューティング

Files

Compare with similar skills

Similar skills

UI Styling

Design System

Creative Tim UI Blocks

Scalar Design System

Activepieces Design System

Coss

More from tsubotax/melta-ui

Design Review

Build Screen

Questions about Ban Pattern

Install Ban Pattern

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

手順

Step 1: パターンを特定する

Step 2: 既存ルールと重複がないか確認する

Step 3: 禁止ルールを登録する

3-1. design/contracts/rules.json — 機械可読ルールを追加（最優先）

3-2. 人間向けドキュメントと件数の整合

3-3. 生成ビューを再生成する

3-4. 検証 — 「即 CI / MCP 反映」を自分で確認する

Step 4: 既存サンプルを走査・修正する

Step 5: 結果を報告する

トラブルシューティング

Files

Compare with similar skills

Similar skills

More from tsubotax/melta-ui

Related

Questions about Ban Pattern

3-1. `design/contracts/rules.json` — 機械可読ルールを追加（最優先）