TastefulKit 1 view · 24h
← AI skills

Naming Convention — Designer Skills

Defines consistent naming rules for design tokens, components, layers and assets, with patterns intended to improve searchability and handoff.

design-systemsdesign-tokenshandoff
View skill source ↗ Repository ↗

2945 GitHub stars (repository-wide; checked Oct 17, 2026)

1940 skills.sh installs (checked Oct 17, 2026)

When to use it

Use when reconciling inconsistent Figma layer names, token identifiers and code component names. This is naming guidance, not an automated migration or linter; adapt separators and casing to existing tooling and preserve references when renaming. Upstream content reviewed; not installed or runtime-tested. GitHub stars measure the whole repository, not this skill.

Compatible agents

Claude CodeGemini CLI

Installation

In Claude Code, run /plugin marketplace add Owl-Listener/designer-skills, then open /plugin → Discover and install design-systems. Ask the agent to use naming-convention. The repository README also documents its Gemini CLI extension setup.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Oct 16, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.