normalize
Normalize Interfaces to Your Design System
Inconsistent interface details make products harder to maintain and use. This skill guides Claude, Codex, and Claude Code through structured UI normalization against existing design standards.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "normalize" from https://skillstore.io/skills/pbakaus-normalize.md and its manifest at https://skillstore.io/api/skills/pbakaus-normalize/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.
Test it
Using "normalize". Normalize the reports dashboard.
Expected outcome:
The dashboard now uses shared card, table, and button patterns. Spacing uses project tokens, empty states match existing language, and focus styles remain visible.
Using "normalize". Review this profile page for design system drift.
Expected outcome:
- Typography differs from the profile settings pattern.
- Primary actions use a custom color instead of the action token.
- The mobile layout does not follow the standard stacked form pattern.
Using "normalize". Make the checkout step match the rest of the app.
Expected outcome:
The checkout step now follows the shared form layout, uses standard error messaging, and keeps the responsive action bar consistent with other flows.
Security Audit
SafeThe only static finding is a false positive caused by design terminology about layout grid systems. I found no evidence of prompt injection, data exfiltration, external command execution, or malicious intent in SKILL.md.
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.
Copy report link
https://skillstore.io/skills/pbakaus-normalize/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/pbakaus-normalize?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/pbakaus-normalize?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/pbakaus-normalize/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/pbakaus-normalize.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
pbakaus. (2026). normalize security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/pbakaus-normalize/audits/4BibTeX citation
@techreport{pbakaus-pbakaus-normalize-2026,
author = {pbakaus},
title = {normalize security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/pbakaus-normalize/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: "normalize security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "pbakaus"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/pbakaus-normalize/audits/4"
identifiers:
- type: other
value: "skillstore:pbakaus-normalize:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Unify a New Feature
Align a recently built page with shared components, tokens, and interaction patterns before release.
Prepare Design Debt Work
Identify inconsistent UI decisions and create a focused plan for reducing one-off implementation debt.
Review Product Consistency
Check whether a product area follows established accessibility, responsive, and layout conventions.
Try These Prompts
Normalize the settings page so it follows our design system. First find the relevant design guidance, then propose and apply focused UI changes.
Analyze the billing flow against our design system. List the main inconsistencies by typography, color, spacing, components, responsive behavior, and accessibility before editing.
Find custom UI in the dashboard summary area that should use existing shared components. Replace it with design system equivalents where appropriate.
Normalize the account onboarding flow end to end. Use repository design guidance, update inconsistent UI, remove obsolete styles, and run the relevant checks.
Best Practices
- Gather design system context before making visual changes.
- Prefer shared components and tokens over new local styles.
- Verify accessibility, responsive behavior, and regression checks after edits.
Avoid
- Do not invent new components when suitable shared components already exist.
- Do not hard-code colors, spacing, or typography that should come from tokens.
- Do not chase visual polish while ignoring usability or accessibility differences.