スキル shadcn-component-boundaries

📦

shadcn-component-boundaries

Name: shadcn-component-boundaries
Author: c3sc0-v4113

v1.0 コンテンツリビジョン r1 安全 ⚙️ 外部コマンド

Organize shadcn Components by Ownership

Mixing product behavior with registry primitives makes component placement unclear and registry updates harder to manage. This skill guides alias resolution, ownership classification, and component placement with one-way dependencies.

対応: Claude Codex Code(CC)

📊 74 十分

Maintain this Skill? Claim it 📊 74 十分

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

Review the Skillstore skill "shadcn-component-boundaries" from https://skillstore.io/skills/c3sc0-v4113-shadcn-component-boundaries.md and its manifest at https://skillstore.io/api/skills/c3sc0-v4113-shadcn-component-boundaries/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/c3sc0-v4113-shadcn-component-boundaries.md 署名済み manifest GET /api/skills/c3sc0-v4113-shadcn-component-boundaries/manifest 署名済み lockfile GET /api/skills/c3sc0-v4113-shadcn-component-boundaries/lockfile

テストする

「shadcn-component-boundaries」を使用しています。 Where should an app-wide ConfirmButton wrapping Button and AlertDialog go when aliases resolve to src/components and src/components/ui?

期待される結果:

Ownership: reusable product component.
Final path: src/components/common/confirm-button.tsx.
Dependency direction: common imports ui primitives; ui must not import the wrapper.

「shadcn-component-boundaries」を使用しています。 Where should a billing-only InvoiceTable go when the components alias resolves to src/components?

期待される結果:

Ownership: billing feature component.
Final path: src/components/billing/invoice-table.tsx.
Dependency direction: billing may use common components and ui primitives; neither lower layer may import billing.

「shadcn-component-boundaries」を使用しています。 Several features need the same new appearance for a registry Button.

期待される結果:

Ownership: registry primitive with a shared visual variant.
Final path: the existing Button file in the resolved ui directory.
Add a variant to the primitive rather than creating a styled copy in common.
Keep product behavior outside ui and retain one-way imports.

セキュリティ監査

安全

v1 • 2026/10/2 バージョン別レポートを開く

All 12 static findings are false positives caused by Markdown inline code, not Ruby or shell execution. No evidence found of prompt injection, credential access, data exfiltration, or malicious intent in the reviewed skill text. The skill provides component placement guidance and delegates optional tooling to existing project configuration.

スキャンされたファイル

解析済み行数

レビュー項目

誤検知を無視

リスク要因

⚙️ 外部コマンド (12)

SKILL.md:18 SKILL.md:19 SKILL.md:20 SKILL.md:21 SKILL.md:23 SKILL.md:24 SKILL.md:26 SKILL.md:32 SKILL.md:33 SKILL.md:34 SKILL.md:40 SKILL.md:44

最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

https://skillstore.io/skills/c3sc0-v4113-shadcn-component-boundaries/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/c3sc0-v4113-shadcn-component-boundaries/security.svg)](https://skillstore.io/skills/c3sc0-v4113-shadcn-component-boundaries?utm_source=security_passport_badge)

HTMLバッジ

<a href="https://skillstore.io/skills/c3sc0-v4113-shadcn-component-boundaries?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/c3sc0-v4113-shadcn-component-boundaries/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

埋め込みカード

<iframe src="https://skillstore.io/embed/skills/c3sc0-v4113-shadcn-component-boundaries.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

学術引用 (APA · BibTeX · CFF)

APA形式の引用

c3sc0-v4113. (2026). shadcn-component-boundaries security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/c3sc0-v4113-shadcn-component-boundaries/audits/1

BibTeX形式の引用

@techreport{c3sc0-v4113-c3sc0-v4113-shadcn-component-boundaries-2026,
  author = {c3sc0-v4113},
  title = {shadcn-component-boundaries security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/c3sc0-v4113-shadcn-component-boundaries/audits/1},
  note = {Author version 1.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "shadcn-component-boundaries security audit report (audit version 1)"
version: "1.0"
type: report
authors:
  - name: "c3sc0-v4113"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/c3sc0-v4113-shadcn-component-boundaries/audits/1"
identifiers:
  - type: other
    value: "skillstore:c3sc0-v4113-shadcn-component-boundaries:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

Place New Product Components

Classify a shared confirmation button and a billing-only table before choosing their component directories.

Protect Registry Component Boundaries

Review wrappers and variants so product behavior stays outside registry primitives during component maintenance.

Review Component Architecture

Check a proposed component move for ownership changes, resolved aliases, and reverse imports.

これらのプロンプトを試す

Choose a Component Location

Use shadcn-component-boundaries to classify [component] in this project. Resolve component aliases and recommend its final path and allowed dependencies.

Create a Shared Wrapper

Create [shared product component] using existing shadcn primitives. Resolve aliases, place product behavior outside ui, and report ownership, final path, and dependency direction.

Review Existing Boundaries

Review [component scope] against shadcn-component-boundaries. Identify misplaced product components and reverse imports, then propose specific moves with ownership classifications and final paths.

Promote a Feature Component

Refactor [feature component] for reuse by [second feature]. Remove feature-specific behavior, resolve aliases, move shared behavior to common, and check imports and configured styling rules.

ベストプラクティス

Resolve aliases before creating or moving components; do not assume a components or src/components directory.
Classify ownership and reuse scope first, then keep product behavior outside registry primitives.
Report final paths and verify one-way imports after every component creation or move.

回避

Putting product wrappers, domain behavior, or feature sections inside the registry ui directory.
Importing feature or common components from registry primitives.
Duplicating a registry primitive for styling instead of using a shared variant and semantic tokens.

よくある質問

When should I use this skill?

Use it when creating, moving, wrapping, or reviewing UI components in a project that uses shadcn.

Does it require a fixed component directory?

No. It resolves components and ui aliases from components.json or uses an installed shadcn skill's project-context command.

Where do reusable product components belong?

Place them under common in the resolved components directory. Keep feature-owned components in a named feature folder or colocated with their feature.

Can registry primitives contain product behavior?

No. Keep product behavior in wrappers outside ui. Shared visual variants may be added to the registry primitive.

Does this skill provide automatic lint enforcement?

No. It explains the boundary enforced by shadcn/no-restyle when @shadcn/lint is already configured.

What should the agent report after a change?

It should state each created or moved component's ownership classification and final path, then confirm the dependency direction holds.