Skills design-system-starter

📦

design-system-starter

Name: design-system-starter
Author: AI Agent Hub

v1.0.0 Content revision r2 Safe ⚙️ External commands📁 Filesystem access🌐 Network access

Build an Accessible Design System

Inconsistent interface decisions slow teams and weaken accessibility. This skill provides token structures, React patterns, templates, and checklists for a scalable design system.

Supports: Claude Codex Code(CC)

📊 76 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "design-system-starter" from https://skillstore.io/skills/ariegoldkin-design-system-starter.md and its manifest at https://skillstore.io/api/skills/ariegoldkin-design-system-starter/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/ariegoldkin-design-system-starter.md Signed manifest GET /api/skills/ariegoldkin-design-system-starter/manifest Signed lockfile GET /api/skills/ariegoldkin-design-system-starter/lockfile

Test it

Using "design-system-starter". Create foundations for a business dashboard with light and dark themes.

Expected outcome:

A token hierarchy covering brand, text, surfaces, feedback, typography, spacing, radii, and shadows.
Semantic light and dark theme mappings with contrast requirements.
A first component set covering buttons, inputs, navigation, tables, dialogs, and feedback.

Using "design-system-starter". Review an existing React component library for accessibility and consistency.

Expected outcome:

A prioritized inventory of token, component, documentation, and governance gaps.
Accessibility findings covering contrast, keyboard support, focus management, semantics, and ARIA.
A staged remediation plan with migration and deprecation guidance.

Using "design-system-starter". Define a reusable form component family.

Expected outcome:

Clear responsibilities for labels, inputs, hints, errors, and grouped controls.
Consistent properties for sizes, validation states, disabled behavior, and required fields.
Keyboard, screen-reader, documentation, and testing requirements for every component.

Security Audit

Safe

v9 • 7/23/2026 Open versioned report

All 63 static findings are false positives caused by documentation syntax, relative imports, keyboard-event properties, public links, schema metadata, or design-system language. The reviewed files contain no command execution, path traversal, secret handling, unauthorized networking, prompt injection, or malicious intent.

Files scanned

2,557

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (50)

references/component-examples.md:493-500 SKILL.md:25 SKILL.md:26 SKILL.md:27 SKILL.md:28 SKILL.md:75-95 SKILL.md:95-98 SKILL.md:98-128 SKILL.md:128-137 SKILL.md:137-175 SKILL.md:175-181 SKILL.md:181-199 SKILL.md:199-202 SKILL.md:202-216 SKILL.md:216-220 SKILL.md:220-233 SKILL.md:233-237 SKILL.md:237-248 SKILL.md:248-270 SKILL.md:270-279 SKILL.md:279-281 SKILL.md:281-292 SKILL.md:292-301 SKILL.md:301-303 SKILL.md:303-332 SKILL.md:332-340 SKILL.md:340-343 SKILL.md:343-357 SKILL.md:357-360 SKILL.md:360-378 SKILL.md:378-382 SKILL.md:382-385 SKILL.md:385-387 SKILL.md:387-395 SKILL.md:395-428 SKILL.md:428-433 SKILL.md:433-443 SKILL.md:443-446 SKILL.md:446-450 SKILL.md:450-453 SKILL.md:453-460 SKILL.md:460-476 SKILL.md:476-491 SKILL.md:491-495 SKILL.md:495-496 SKILL.md:496-497 SKILL.md:497-498 SKILL.md:498-501 SKILL.md:501 SKILL.md:505-523

📁 Filesystem access (2)

references/component-examples.md:13 templates/component-template.tsx:15

🌐 Network access (2)

SKILL.md:473 templates/design-tokens-template.json:2

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/ariegoldkin-design-system-starter/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/ariegoldkin-design-system-starter/security.svg)](https://skillstore.io/skills/ariegoldkin-design-system-starter?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/ariegoldkin-design-system-starter?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/ariegoldkin-design-system-starter/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/ariegoldkin-design-system-starter.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

AI Agent Hub. (2026). design-system-starter security audit report (audit version 9) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/ariegoldkin-design-system-starter/audits/9

BibTeX citation

@techreport{ai-agent-hub-ariegoldkin-design-system-starter-2026,
  author = {AI Agent Hub},
  title = {design-system-starter security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/ariegoldkin-design-system-starter/audits/9},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "design-system-starter security audit report (audit version 9)"
version: "1.0.0"
type: report
authors:
  - name: "AI Agent Hub"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/ariegoldkin-design-system-starter/audits/9"
identifiers:
  - type: other
    value: "skillstore:ariegoldkin-design-system-starter:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Establish Product Foundations

Define shared visual tokens and component principles before designing a new application.

Build Reusable Components

Create typed React components with consistent variants, composition patterns, theming, and accessibility behavior.

Audit System Coverage

Review an existing library for missing tokens, components, documentation, testing, governance, and accessibility requirements.

Try These Prompts

Start a Design System

Create a design-system foundation for [product]. Define principles, token categories, core components, and accessibility requirements. Explain each decision briefly.

Define Design Tokens

Design primitive and semantic tokens for [brand]. Include color, typography, spacing, radii, shadows, and light and dark themes. Note accessibility constraints.

Specify a Component Family

Specify the React and TypeScript architecture for [component family]. Cover APIs, variants, composition, states, keyboard behavior, ARIA, documentation, and tests.

Plan a System Migration

Audit [existing interface] against the included checklist. Prioritize gaps, map legacy styles to tokens, define deprecations, and propose a staged adoption plan.

Best Practices

Separate primitive values from semantic tokens so themes and brands can change without rewriting components.
Build accessibility into component APIs, examples, tests, and documentation from the first implementation.
Document migration, versioning, deprecation, and ownership rules before broad adoption.

Avoid

Do not expose raw palette values throughout product code when semantic tokens can express intent.
Do not create highly configurable components that replace clear composition with many unrelated properties.
Do not claim accessibility compliance without keyboard, screen-reader, contrast, and browser testing.