切图命名规范

切图命名规范 is a small reference resource AImed at the handoff between design and front-end development. It focuses on one nARRow but peRSIstent problem: how to name sliced image assets so that everyone on a project can recognize, locate, and reuse them without guesswork. Rather than generating visuals, it offers a naming convention that teams can adopt when exporting icons, backgrounds, and other UI fRAGments.

What it does

The page lays out a naming scheme for cut images, often called slices, that come out of Design Tools and go into a website or APP build. Consistent naming reduces confusion during implementation, makes asset libraries eASIer to search, and lowers the chance that a developer picks the wrong file. The guidance is written for a Chinese-speaking audience and is presented as quick-reference material rather than an interACTive application.

Key capabilities

• Naming conventions: Suggests structured patterns for labeling exported image files.
• Design-to-development handoff: Targets the moment when visual assets are passed from designers to coders.
• Shared vocabulary: Helps both roles remember and apply the Same rules.
• Quick reference fORMat: Intended for fast lookup during daily production work.

Who it is for

The material suits UI designers, front-end developers, and small product teams that manage their own assets. It is also useful for students learning production Workflows or for anyone tidying a folder of exported icons and backgrounds. Teams with an established design system may find the IDEas familiar, but the page can still serve as a checklist for onboarding new members.

How to get started

Open the reference page in a browser, read through the proposed patterns, and compare them with your current file structure. Pick the parts that fit your project, then document the agreed rules somewhere your team can find them, such as a shared style guide or repository readme. Applying one scheme consistently matters more than copying every detail.

Pricing and access caveat

The resource appears to be freely accessible on the web, with no account required. Availability, language support, and any future changes to the site may vary, so confirm current access before relying on it for a production workflow. No version, developer, or pricing details are asserted here.