shadcn-component-boundaries
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.
التثبيت باستخدام Agent لدي
انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.
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.يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.
موارد مهيّأة لـ Agents
استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.
اختبرها
جارٍ استخدام "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.
التدقيق الأمني
آمن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)
شارك واستشهد بهذا التقرير
شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.
نسخ رابط التقرير
https://skillstore.io/skills/c3sc0-v4113-shadcn-component-boundaries/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportشارة Markdown
[](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.
جرّب هذه الموجّهات
Use shadcn-component-boundaries to classify [component] in this project. Resolve component aliases and recommend its final path and allowed dependencies.
Create [shared product component] using existing shadcn primitives. Resolve aliases, place product behavior outside ui, and report ownership, final path, and dependency direction.
Review [component scope] against shadcn-component-boundaries. Identify misplaced product components and reverse imports, then propose specific moves with ownership classifications and final paths.
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?
Does it require a fixed component directory?
Where do reusable product components belong?
Can registry primitives contain product behavior?
Does this skill provide automatic lint enforcement?
What should the agent report after a change?
تفاصيل المطور
المؤلف
c3sc0-v4113الترخيص
Apache-2.0
إصدار المؤلف
v1.0
مراجعة Skillstore
r1
تنبيه الإصدار
الإصدار الذي أعلنه المؤلف ليس SemVer صالحًا.
مرجع
a55c18fe8a4c497c5ad4ca58af00009046d9fcf2
حداثة الصيانة
٢/١٠/٢٠٢٦
الاستخدام
0 تنزيلات · 0 مشاهدات
بنية الملفات