Tom Huang
6f6bf31dd2
* Refactor project name from "Open Claude Design" to "Open Design" - Updated project name in package.json, package-lock.json, and README files. - Changed CLI commands and references from "ocd" to "od". - Adjusted file structure references in documentation and code to reflect new naming conventions. - Enhanced .gitignore to include new runtime data files. - Updated metadata in LICENSE file to match new project name. * Add contributing guidelines in English and Chinese - Introduced CONTRIBUTING.md and CONTRIBUTING.zh-CN.md to provide clear instructions for contributors. - Outlined contribution types, local setup instructions, and merging criteria for skills and design systems. - Enhanced README files to reference the new contributing guidelines.
75 lines
2.6 KiB
Markdown
75 lines
2.6 KiB
Markdown
---
|
||
name: dashboard
|
||
description: |
|
||
Admin / analytics dashboard in a single HTML file. Fixed left sidebar,
|
||
top bar with user/search, main grid of KPI cards and one or two charts.
|
||
Use when the brief asks for a "dashboard", "admin", "analytics", or
|
||
"control panel" screen.
|
||
triggers:
|
||
- "dashboard"
|
||
- "admin panel"
|
||
- "analytics"
|
||
- "control panel"
|
||
- "后台"
|
||
- "管理后台"
|
||
od:
|
||
mode: prototype
|
||
platform: desktop
|
||
scenario: operations
|
||
preview:
|
||
type: html
|
||
entry: index.html
|
||
design_system:
|
||
requires: true
|
||
sections: [color, typography, layout, components]
|
||
---
|
||
|
||
# Dashboard Skill
|
||
|
||
Produce a single-screen admin / analytics dashboard.
|
||
|
||
## Workflow
|
||
|
||
1. **Read the active DESIGN.md** (injected above). Colors, typography, spacing,
|
||
component styling all come from it. Do not invent new tokens.
|
||
2. **Classify** what the dashboard monitors (sales, traffic, usage, incidents,
|
||
ops, etc.) from the brief. Generate specific, plausible metric names and
|
||
values — no "Metric A / Metric B" placeholders.
|
||
3. **Lay out** the required regions:
|
||
- **Left sidebar** (220–260px): brand mark at top, 6–8 nav links with
|
||
icons, active state uses the DS accent.
|
||
- **Top bar**: page title on the left, search input + user avatar / status
|
||
on the right.
|
||
- **Main**:
|
||
- Row 1: 3–4 KPI cards (label + big number + delta vs. prior period).
|
||
- Row 2: one primary chart (full width or 2/3) — render as an inline SVG
|
||
line / bar / area chart drawn from real-looking numbers.
|
||
- Row 3: one secondary chart or table (recent events, top items, etc.).
|
||
4. **Write** one self-contained HTML document:
|
||
- `<!doctype html>` through `</html>`, CSS in one inline `<style>` block.
|
||
- CSS Grid for the overall layout; Flexbox inside cards.
|
||
- Semantic HTML: `<aside>`, `<header>`, `<main>`, `<section>`.
|
||
- Tag each logical region with `data-od-id="slug"` for comment mode.
|
||
5. **Charts**: inline SVG only, no JS libraries. A line chart is ~10 lines of
|
||
`<polyline>` with a subtle area fill. A bar chart is N `<rect>`s with
|
||
DS-accent fill. Label axes lightly (muted text, smaller scale).
|
||
6. **Self-check**:
|
||
- Every color comes from DESIGN.md tokens.
|
||
- Accent used at most twice (sidebar active + one chart highlight).
|
||
- Sidebar + top bar are sticky; main scrolls independently.
|
||
- Density matches the DS mood — airy DSes get more padding, dense DSes
|
||
(trading, crypto) tighten rows.
|
||
|
||
## Output contract
|
||
|
||
Emit between `<artifact>` tags:
|
||
|
||
```
|
||
<artifact identifier="dashboard-slug" type="text/html" title="Dashboard Title">
|
||
<!doctype html>
|
||
<html>...</html>
|
||
</artifact>
|
||
```
|
||
|
||
One sentence before the artifact, nothing after.
|