Skills interface-design

📦

interface-design

Name: interface-design
Author: dammyjay93

Content revision r1 Safe ⚙️ External commands

Design Purpose-Built Product Interfaces

Generic dashboards make products feel interchangeable and harder to scan. This skill guides Claude, Codex, and Claude Code to design focused product interfaces with clear systems.

Supports: Claude Codex Code(CC)

📊 75 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 "interface-design" from https://skillstore.io/skills/dammyjay93-interface-design.md and its manifest at https://skillstore.io/api/skills/dammyjay93-interface-design/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/dammyjay93-interface-design.md Signed manifest GET /api/skills/dammyjay93-interface-design/manifest Signed lockfile GET /api/skills/dammyjay93-interface-design/lockfile

Test it

Using "interface-design". A product team needs a maintenance dashboard for field technicians.

Expected outcome:

Domain focus: equipment status, dispatch priority, site constraints, and maintenance history.
Design direction: a dense scan-first interface with restrained alerts and operational color choices.
Checks: hierarchy, signature elements, token language, and non-generic layout decisions.

Using "interface-design". An engineer asks for a review of an existing settings page.

Expected outcome:

Audit result: unclear hierarchy, weak focus states, and inconsistent spacing reduce usability.
Recommendations: use a smaller spacing scale, clearer control states, and calmer surface separation.

Using "interface-design". A founder wants future product screens to feel consistent.

Expected outcome:

Saved patterns should cover direction, depth, spacing, and repeated component behavior.
Future screens should reuse these choices unless the user approves a new direction.

Security Audit

Safe

v4 • 7/6/2026 Open versioned report

All 22 static findings appear to be false positives from Markdown examples, inline code formatting, and design prose. No evidence found for shell execution, system reconnaissance, prompt injection, network access, or data exfiltration.

Files scanned

683

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (13)

SKILL.md:14 SKILL.md:40 SKILL.md:227 SKILL.md:258-267 SKILL.md:267-270 SKILL.md:270-286 SKILL.md:286-288 SKILL.md:288-290 SKILL.md:290-303 SKILL.md:303-304 SKILL.md:304-308 SKILL.md:308-309 SKILL.md:309-310

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/dammyjay93-interface-design/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/dammyjay93-interface-design.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

dammyjay93. (2026). interface-design security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dammyjay93-interface-design/audits/4

BibTeX citation

@techreport{dammyjay93-dammyjay93-interface-design-2026,
  author = {dammyjay93},
  title = {interface-design security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/dammyjay93-interface-design/audits/4},
  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: "interface-design security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
  - name: "dammyjay93"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/dammyjay93-interface-design/audits/4"
identifiers:
  - type: other
    value: "skillstore:dammyjay93-interface-design:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Design a Focused Dashboard

Explore the product domain, choose a signature direction, and define layout, color, and hierarchy before building.

Improve an Admin Panel

Audit spacing, surfaces, controls, states, and typography so the interface feels intentional and consistent.

Standardize Product UI Patterns

Capture reusable interface decisions so future screens follow the same product logic and visual system.

Try These Prompts

Explore an Interface Direction

Use the interface-design skill to explore the domain for a new product interface. Identify the user, task, color world, signature element, and defaults to reject.

Design a Dashboard System

Design a dashboard with a clear navigation model, surface hierarchy, spacing scale, control states, and domain-specific visual language.

Audit an Existing Screen

Review this interface for generic patterns, weak hierarchy, inconsistent tokens, missing states, and unclear product intent. Recommend concrete changes.

Create a Reusable Interface System

Extract reusable patterns from this interface and propose what should be saved for future screens, including spacing, depth, components, and visual direction.

Best Practices

Start with the product domain and user task before choosing layout or style.
Define surface, spacing, typography, color, and state rules as one system.
Run craft checks before showing the user the final interface.

Avoid

Do not apply a standard dashboard template before exploring the product context.
Do not use random colors, spacing values, shadows, or border styles.
Do not save one-off experiments as reusable interface patterns.