better-colors
Build Consistent Color Systems and Check Contrast
Scattered colors and unclear token roles make themes difficult to maintain. This skill guides palette generation, semantic naming, and contrast reviews using your project conventions.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "better-colors" from https://skillstore.io/skills/jakubkrehel-better-colors.md and its manifest at https://skillstore.io/api/skills/jakubkrehel-better-colors/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「better-colors」を使用しています。 A component uses the blue primitive directly for its primary button. Suggest a token structure without changing its appearance.
期待される結果:
- Keep the blue value in the primitive layer.
- Map the accent solid role to that primitive.
- Have the button reference the semantic role so themes can change the mapping centrally.
- Contrast remains unverified until the foreground-background pair is measured.
「better-colors」を使用しています。 Our theme reverses the light palette for dark mode and shares one increased-contrast override. Review this approach without editing.
期待される結果:
- Dark mode needs tuned chroma and surface spacing, not only reversed steps.
- Give each appearance its own increased-contrast values.
- Remeasure text against its rendered background in both appearances.
- Rendered contrast is not verified without theme values and browser measurements.
セキュリティ監査
安全All 51 static findings are false positives involving Markdown code spans, CSS examples, or color-system terminology. No evidence found of command execution, reconnaissance, exfiltration, or prompt injection in the reviewed files. The approval language governs color-review outcomes, not marketplace security decisions.
リスク要因
⚙️ 外部コマンド (28)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/jakubkrehel-better-colors/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/jakubkrehel-better-colors?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/jakubkrehel-better-colors?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/jakubkrehel-better-colors/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/jakubkrehel-better-colors.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形式の引用
jakubkrehel. (2026). better-colors security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jakubkrehel-better-colors/audits/1BibTeX形式の引用
@techreport{jakubkrehel-jakubkrehel-better-colors-2026,
author = {jakubkrehel},
title = {better-colors security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/jakubkrehel-better-colors/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "better-colors security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "jakubkrehel"
date-released: "2026-10-09"
url: "https://skillstore.io/skills/jakubkrehel-better-colors/audits/1"
identifiers:
- type: other
value: "skillstore:jakubkrehel-better-colors:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Plan a Product Palette
Generate necessary neutral, accent, and status ramps from a brand color, then assign each step a clear interface role.
Standardize Component Tokens
Review literal colors and primitive utilities, then propose semantic tokens that preserve existing notation and support theme changes.
Review Theme Contrast
Inspect foreground-background pairs across light, dark, and increased-contrast appearances, reporting measured failures and checks that remain unverified.
これらのプロンプトを試す
Review these colors and their uses: [colors and roles]. Suggest primitive and semantic token names. Keep the existing notation.
Build a palette around [brand color] using [Tailwind or Radix] steps. Use a color library. Include only required roles and explain gamut checks.
Review [components] in light and dark themes. Measure actual foreground-background pairs against [standard]. Report failures and unverified checks. Do not change colors.
Inventory [project scope] colors, cluster near-duplicates, and propose semantic mappings. Include dark and increased-contrast variants, measured checks, and migration risks. Await approval before editing.
ベストプラクティス
- Preserve established notation and token conventions unless a migration is explicitly in scope.
- Generate palette values with a color library and assign every retained step a role.
- Measure actual rendered pairs in every appearance and mark unavailable checks as Not verified.
回避
- Apply hue-based primitives directly in components instead of semantic role tokens.
- Estimate contrast or assume a pair passes because its palette step usually works.
- Convert formats or consolidate colors across unrelated screens without approval.
よくある質問
Which assistants can use this skill?
Must my project switch to OKLCH?
Does the package include a color calculation tool?
Can it review contrast without a browser?
Will it automatically fix failing colors?
Does a successful review prove accessibility compliance?
開発者情報
作成者
jakubkrehelライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
e406bf64b5db6e514879399e87b346fa7ff7c2fb
メンテナンスの新しさ
2026/10/11
利用状況
0 ダウンロード · 0 閲覧
ファイル構成