nexu-io/open-design

orbit-general

Use it for design tasks; the detail page covers purpose, installation, and practical steps.

81Collecting
See how to use itView GitHub source
npx skills add https://github.com/nexu-io/open-design --skill "design-templates/orbit-general"
Automated source guideDesignDeep source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded design guide: orbit-general

Cross-connector morning briefing that lives at the top of "我的设计". Pulls the past 24 hours of activity from every authenticated connector and lays them out as one editorial bento dashboard.

npx skills add https://github.com/nexu-io/open-design --skill "design-templates/orbit-general"
Check the pinned source

The pinned source contains enough sections and task detail for a source-grounded deep guide; automated content is still not an independent test.

1,315 source words · 7 usable sections

Design process

Read orbit-general through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

Implementation constraints (paired do / don't)

Review the “Implementation constraints (paired do / don't)” section in the pinned source before continuing.

SKILL.md · Implementation constraints (paired do / don't)
Review and apply the “Implementation constraints (paired do / don't)” source section.
02

⚠️ Source-of-truth protocol (read this first)

Step 1. Open and read the shipped example.html in this folder before writing any output. That file is the canonical design — your job is to reproduce it, not reinterpret it.

SKILL.md · ⚠️ Source-of-truth protocol (read this first)
Same DOM hierarchy and class namesSame number and order of sectionsSame number of bento modules in the same order
03

⚠️ Design system policy

This skill ships with its own complete visual language baked into example.html. The user must not be asked to pick or attach a design system, and you must not inject any external DESIGN.md tokens into the output.

SKILL.md · ⚠️ Design system policy
If the active project has a design system attached, ignore it.If the user supplies brand tokens or a Figma file, ignore them.Use exclusively the colors / fonts / radii / chrome defined in
04

Canvas tokens (use these exact values)

Type stack: - Display serif: 'Cormorant', Georgia, serif — KPI numerals, Hero h1, Top 3 serial numbers, italic comment quotes - Body sans: 'Inter', -apple-system, system-ui, sans-serif - Numbers: always font-variant-numeric: tabular-nums

SKILL.md · Canvas tokens (use these exact values)
Display serif: 'Cormorant', Georgia, serif — KPI numerals, Hero h1,Body sans: 'Inter', -apple-system, system-ui, sans-serifNumbers: always font-variant-numeric: tabular-nums
05

Page sections (top to bottom)

1. Hero — single row, 80px tall. Left: ☀ 你好 (Cormorant 38px). Right of greeting: · 2026 年 5 月 6 日 · 星期三 (muted, 18px). Far right: round avatar (40px) + small ⚙ + ✕ icons.

SKILL.md · Page sections (top to bottom)
Hero — single row, 80px tall.KPI strip — single row, 120px tall, 5 columns equal width.Today's timeline — full width, 140px tall.

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Source-grounded prompt

Use for a design task while explicitly checking the source sections.

Use orbit-general for this design task: [task]. Inputs and constraints: [details]. Work through these pinned SKILL.md sections: “Implementation constraints (paired do / don't)”, “⚠️ Source-of-truth protocol (read this first)”, “⚠️ Design system policy”, “Canvas tokens (use these exact values)”, “Page sections (top to bottom)”. Cite the concrete requirements that shape each step, do not invent capabilities absent from the source, and verify the result against: [acceptance criteria].

Design checklist

Verify each item before delivery

The source section “Implementation constraints (paired do / don't)” has been checked.

The source section “⚠️ Source-of-truth protocol (read this first)” has been checked.

The source section “⚠️ Design system policy” has been checked.

The source section “Canvas tokens (use these exact values)” has been checked.

Choose a different workflow

When another Skill is the better fit

orbit-general

Use it for design tasks; the detail page covers purpose, installation, and practical steps.

A separate implementation from nexu-io/open-design; compare its source, maintenance signals, and permission requirements.

Open source detail

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does the orbit-general source document cover?

Cross-connector morning briefing that lives at the top of "我的设计". Pulls the past 24 hours of activity from every authenticated connector and lays them out as one editorial bento dashboard.

How do I install orbit-general?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "design-templates/orbit-general". Inspect the command and pinned source before running it.

Repository stars
82,073
Repository forks
9,485
Quality
81/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

81/100
Documentation26/30
Specificity18/25
Maintenance20/20
Trust signals17/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

orbit-general by nexu-io

Use it for design tasks; the detail page covers purpose, installation, and practical steps.

ab-testing by coreyhaines31

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

churn-prevention by coreyhaines31

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

design-intelligence by event4u-app

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

design-system-capture by event4u-app

Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 7 min

Orbit General Briefing

Cross-connector morning briefing that lives at the top of "我的设计". Pulls the past 24 hours of activity from every authenticated connector and lays them out as one editorial bento dashboard.

⚠️ Source-of-truth protocol (read this first)

Step 1. Open and read the shipped example.html in this folder before writing any output. That file is the canonical design — your job is to reproduce it, not reinterpret it.

Step 2. Mirror the example's structure 1:1:

  • Same DOM hierarchy and class names
  • Same number and order of sections
  • Same number of bento modules in the same order
  • Same connector list (do not add or drop connectors)
  • Same KPI labels, same Top 3 entries, same "people waiting" set
  • Same footer string
  • Same <script> block at the end (link injection)

Step 3. You may freshen mock data values (counts, names, times) so they read as "today" — but you must not invent new UI elements, sections, modules, badges, callouts, ribbons, banners, decorations or chrome that aren't already in example.html. If a detail is not in the example, it does not belong in your output.

Identity guard. Treat every person name or handle in example.html as mock content only. Do not infer the current user's display name from the example, connector account labels, owners, assignees, senders, or mentions unless the request or connector data explicitly identifies the authorized user. If no explicit current-user name is available, use neutral wording such as you, your, current user, , or .

The body sections below are a reference for the visual language and tokens — they are not a license to add features the example doesn't already render.

⚠️ Design system policy

This skill ships with its own complete visual language baked into example.html. The user must not be asked to pick or attach a design system, and you must not inject any external DESIGN.md tokens into the output.

  • If the active project has a design system attached, ignore it.
  • If the user supplies brand tokens or a Figma file, ignore them.
  • Use exclusively the colors / fonts / radii / chrome defined in example.html.

This is a hard constraint: an Orbit briefing must read as Open Orbit's own editorial bento language, not as the user's brand.

Canvas tokens (use these exact values)

--bg:        #FAF7F2     /* off-white page */
--surface:   #FFFFFF     /* card */
--fg:        #1A1816     /* ink */
--muted:     #6B6660     /* secondary text */
--border:    #EAE5DD     /* 1px hairline only */
--orange:    #D86A47     /* accent (CTAs, hero highlight, meeting blocks) */
--green:     #2E7D5B     /* ok / done */
--yellow:    #C9982E     /* waiting */
--red:       #C0473A     /* alert / fail */
--radius-l:  24px        /* outer container */
--radius-m:  16px        /* bento cards */
--radius-s:  12px        /* inner blocks */

Type stack:

  • Display serif: 'Cormorant', Georgia, serif — KPI numerals, Hero h1, Top 3 serial numbers, italic comment quotes
  • Body sans: 'Inter', -apple-system, system-ui, sans-serif
  • Numbers: always font-variant-numeric: tabular-nums

No shadows. No gradients. No emoji as primary visuals. Connector icons must be monochrome line SVG (1.5 stroke).

Page sections (top to bottom)

  1. Hero — single row, ~80px tall. Left: ☀ 你好 (Cormorant 38px). Right of greeting: · 2026 年 5 月 6 日 · 星期三 (muted, 18px). Far right: round avatar (40px) + small ⚙ + ✕ icons.

  2. KPI strip — single row, ~120px tall, 5 columns equal width. Each cell: serif number (Cormorant 64px, --fg) over a muted uppercase tracking label (Inter 11px, letter-spacing 0.06em). Optional ▲/▼ delta tag in --green/--red next to the number. Suggested labels: 待办 / 待 review / 会议 / @ 我 / agent 跑完.

  3. Today's timeline — full width, ~140px tall. Horizontal time axis from 09:00 → 19:00, hour ticks below. Meeting blocks: filled --orange rounded rectangles spanning their start/end, with the meeting name + attendee count inside. Deep-work suggestions: pale-green translucent bands behind the axis. "Now" indicator: a 1px vertical --red line with a pulsing dot (@keyframes pulse 2s ease-in-out infinite) and a tiny 现在 label.

  4. Top 3 — 3 equal cards, ~220px tall. Each card: huge serif numeral 1 / 2 / 3 (Cormorant 96px, in --fg) left-aligned; one-sentence task headline (Inter 18px medium); a meta row at the bottom with the connector source label + line-icon

    • 等待 Xh waiting time. Cards have --border 1px outline only.
  5. Connector modules — adaptive bento, the heart of the briefing. Render 10–16 modules. Sizes vary: data-rich connectors take a 2-column or 2-row span, simple ones stay 1×1. No two modules should look identical. Pick UI per the data family below.

  6. People waiting on you — full-width strip ~110px tall. Title left: 5 人在等你 · 最久 22h (serif 24px). Right: 5 overlapping circular avatars (44px, ~8px overlap), each with the person's name + waiting reason underneath in 12px muted.

  7. Footer — single line, ~52px. Left: Open Orbit · auto-generated 06:42 · N connectors. Right: 由 Nexu Labs 出品. Border-top 1px, all text 12px muted.

Connector → UI mapping (pick the matching family)

FamilyExamplesUI form
Code collabGitHub, GitLab, BitbucketStatus-dot list (open/merged/closed/CI fail) + reviewer count, optional 2–3 line diff preview
Task mgmtLinear, Jira, Asana, ClickUpIssue list with colored status dot + priority bars; for cycle, add a small ring or progress strip
CommsGmail, Slack, 飞书 IM, OutlookRound avatar + one-line quote, accent color for "awaiting reply"
KnowledgeNotion, Confluence, 飞书 DocDoc title + 2-line excerpt block; comment quote in italic serif
TimeCalendarAlready lives in the global timeline; module form: agenda list with start time gutter
AlertsSentry, Datadog, PagerDutyBig red Cormorant number (e.g. 4), 7 small squares as 7-day heatmap, plus 1 latest error line
StatusVercel, GH Actions, NetlifyColored status dot per recent build/deploy + branch + duration
FilesDrive, Dropbox, BoxFilename list with tiny thumbnail squares + "edited by" attribution
BoardTrello, Miro, FigJam3 compact kanban columns with rounded card chips
FinanceStripe, PayPal, banking, BrexCormorant currency number + 7-day sparkline + last 3 transactions list
CRM / SalesSalesforce, HubSpot, Pipedrive3-column deal pipeline (Open / Negotiation / Won) + 1–2 priority contact cards
SupportZendesk, Intercom, Help ScoutTicket queue list with SLA timer pill (green / yellow / red) + assignee avatar
AnalyticsGoogle Analytics, Mixpanel, AmplitudeMini funnel chart (4 bars descending) + 1-line cohort delta (▲ 12% W/W)
InfrastructureAWS, GCP, Kubernetes, DockerResource meters (CPU / mem / disk percent bars) + last 2 deployment lines
Security1Password, Auth0, OktaEvent list with red shield for high-severity items + audit timestamp
Voice/Miscunknown connectorSee Fallback heuristics below

Fallback heuristics (for unknown connectors)

When a connector doesn't match any family above, infer by the data shape it returns:

  • Returns numbers + a time series → treat as Alerts (big number + heatmap)
  • Returns rows with status field → treat as Task mgmt (status-dot list)
  • Returns rows with from / subject → treat as Comms (avatar + quote)
  • Returns documents / file names → treat as Files (list + thumbnails)
  • Returns a small set of named "states" (deploy / build / cycle) → treat as Status
  • Returns dated events → treat as Time (agenda list)

If still ambiguous, fall back to a status-dot list (the safest default).

Implementation constraints (paired do / don't)

Don'tDo
Render every module as the same card shapeVary by family — Alert = big red number + heatmap; Status = status-dot list; Files = thumbnail grid; Comms = avatar + quote
Render Sentry / PagerDuty as a plain listBig red Cormorant number + 7-day heatmap + latest error line (TypeError: …)
Render Calendar as a plain text agendaVisualize on the horizontal timeline at the top; module form is an agenda list with start-time gutter
Use placeholder names like "Service A / Project X"Infer plausible real names from the connector type — GitHub → nexu-io/open-design, Sentry → frontend-prod, Linear → ENG / DES cycle 24, Stripe → Pro plan / Acme Co.
Use lorem ipsum fillerWrite specific mock copy that reads as a real workday — names, numbers, errors, paths, percentages
Mix emoji and SVG icons in the same module setUse monochrome line SVGs (1.5 stroke) consistently for all connector icons; emoji are reserved for hero greeting and section anchors only
Square or rounded-square avatarsAlways circles; sizes 28 / 32 / 40 / 44 px depending on context
Drop shadows / gradients / glows on cardsFlat surfaces only; differentiate cards with the 1px #EAE5DD hairline border
Use brand colors from the user's design systemUse exclusively the canvas tokens above (#FAF7F2, #1A1816, #D86A47 …) — Orbit's own editorial language
Skill path
design-templates/orbit-general/SKILL.md
Commit SHA
89d6d4ef21ba
Repository license
Apache-2.0
Data collected