CRM Ant Design Admin Spec
name: crm-antdesign-admin-spec
by benisonli · published 2026-04-01
$ claw add gh:benisonli/benisonli-crm-antdesign-admin-spec---
name: crm-antdesign-admin-spec
description: Design, structure, review, and generate B2B CRM or admin pages using an Ant Design-style system with page taxonomy, reusable layout rules, token guidance, component mapping, and AI-generation constraints. Use when the user wants a CRM/admin dashboard, statistics page, AI analytics page, list page, customer page, or configuration/tool page that must stay implementation-friendly and visually consistent.
---
# CRM Ant Design Admin Spec
What this skill is for
Use this skill when the user needs help with:
This skill is especially useful when:
What this skill is NOT for
Do **not** use this as the main skill for:
Default design direction
Prefer:
Avoid:
Core operating rule
First classify the page type, then apply the matching structure and constraints.
Do **not** treat every page like a dashboard.
Page type decision
Choose one of these before designing:
1. **Statistics page**
- KPI cards
- charts
- time filters
- org tree / left filter panel
- management overview
2. **AI analytics page**
- analytics dashboard
- insights / risks / recommendations
- KPI + charts + AI summary blocks
- slightly enhanced visual tone allowed
3. **List page**
- customer lists
- operational tables
- search / filters / pagination
- CRUD-oriented workflow
4. **Configuration / tool page**
- parameter setup
- upload areas
- forms + tables
- left functional menu + right config content
If uncertain, default to the simplest page type that matches the task.
How to use this skill
For design tasks
For review tasks
Check for:
For AI generation tasks
Use prompt patterns from `references/prompt-templates.md`.
For design-system alignment
Use `references/token-and-components.md`.
For page skeleton and visual rules
Use `references/admin-guidelines.md`.
For concrete examples
Use `references/examples.md`.
Recommended output pattern
When generating a page spec or design direction:
1. Identify the page type
2. Pick the matching skeleton
3. Apply token / color / radius / typography rules
4. Map to likely Ant Design components
5. Add AI-specific enhancement only if the page truly needs it
6. State what should *not* be done for this page type
Deliverable styles this skill can support
This skill can guide outputs such as:
References
More tools from the same signal band
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...