AGENT SKILL

enterprise-design-systems

暂无简介

License 许可
Apache-2.0
最近更新
2026-11-14
Stars
★ 13
Forks
2

03 SKILL.md 正文

/enterprise-design-systems

When to Use

  • Building B2B SaaS, admin panels, or data-dense dashboards
  • Establishing component naming conventions for a design system
  • Auditing component accessibility or keyboard navigation
  • "This component library feels inconsistent across teams"

Do NOT use for

  • Consumer marketing pages (different visual language)
  • Prototypes with < 10 components

Component Naming Conventions (BEM + Carbon/Primer hybrid)

Block:     cds-button, pds-tag, primer-avatar
Element:   cds-button__icon, pds-tag__label
Modifier:  cds-button--primary, cds-button--sm, cds-button--loading
State:     is-disabled, is-loading, has-error

Rules (IBM Carbon + Salesforce):

  • Block prefix = design system abbreviation (never generic)
  • Modifiers describe intent, not appearance: --destructive not --red
  • State classes start with is- or has- (never modify base class directly)

Data-Dense Layout (Palantir Blueprint)

Blueprint's core principle: information density > whitespace aesthetics for power users.

// Dense table with inline actions — Blueprint pattern
<Table numRows={100} columnWidths={[200, 120, 80, 60]}>
  <Column name="Name"   cellRenderer={renderName} />
  <Column name="Status" cellRenderer={renderStatus} />
  <Column name="Score"  cellRenderer={renderScore} />
  <Column name=""       cellRenderer={renderActions} />
</Table>

// Compact spacing tokens for dense UIs
--spacing-dense-xs: 2px;
--spacing-dense-sm: 4px;
--spacing-dense-md: 8px;

Accessible Form Patterns (Workday Canvas + Zendesk Garden)

// Every input MUST have: label, error, description linkage via aria-
<FormField>
  <Label htmlFor="email">Email address</Label>
  <Input
    id="email"
    aria-describedby="email-hint email-error"
    aria-invalid={!!error}
  />
  <Hint id="email-hint">We'll only use this for login</Hint>
  {error && <Error id="email-error" role="alert">{error}</Error>}
</FormField>

Rules: Label always visible (never placeholder-only). Error role="alert". Hint always present for complex fields.


Headless Component Pattern (Reakit / React Aria)

// Adobe React Spectrum — behavior separate from styling
import { useButton } from '@react-aria/button'

function Button({ children, ...props }) {
  const ref = useRef()
  const { buttonProps } = useButton(props, ref)
  return (
    <button {...buttonProps} ref={ref} className="my-button">
      {children}
    </button>
  )
}
// Keyboard nav, ARIA, focus management = handled by hook
// Visual styling = entirely yours

Developer-Tool UI (GitHub Primer principles)

Primer's 4 rules for dev-tool interfaces:

  1. Monospace for code — always, never serif/sans for code snippets
  2. Muted palette — neutral grays dominate, color = signal only
  3. High information density — padding ≤ 8px in compact views
  4. Keyboard first — every action reachable without mouse
/* Primer compact mode */
.primer-compact { --base-size-4: 2px; --base-size-8: 4px; }

Chart/Viz Component (ECharts + Grommet)

// ECharts — always set explicit dimensions, never rely on container
const chart = echarts.init(container, null, {
  width: 600, height: 400,
  renderer: 'svg'  // SVG for accessibility, Canvas for 10k+ points
})

// Grommet DataChart — declarative data binding
<DataChart
  data={data}
  series={['date', { property: 'amount', label: 'Revenue' }]}
  chart={[{ property: 'amount', type: 'line', thickness: 'xsmall' }]}
  guide={{ x: { granularity: 'coarse' }, y: { granularity: 'fine' } }}
/>

Rich Text Editor (Basecamp Trix architecture)

Trix stores content as a document model, not HTML string.
Never store raw HTML — store structured attachments + string content.
Render via trix-content class for consistent output styling.

Anti-Pattern Checklist

❌ Modifier class describes color: --red, --blue (use --error, --primary)
❌ Form input without visible label
❌ Interactive component without keyboard support
❌ Chart with pixel dimensions hardcoded in CSS (not component props)
❌ Rich text storing raw HTML strings
❌ Dense data UI using consumer app spacing (> 16px padding)

04 同仓库更多 Skills

Horonomos-laps
Horonomos-laps/Yana-AI

openai--sentry--sentry

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

★ 13
Horonomos-laps
Horonomos-laps/Yana-AI

ito-basket-compare

Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.

★ 13
Horonomos-laps
Horonomos-laps/Yana-AI

implementing-network-traffic-baselining

Build network traffic baselines from NetFlow/IPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly/daily traffic pattern profiling

★ 13
Horonomos-laps
Horonomos-laps/Yana-AI

detecting-evasion-techniques-in-endpoint-logs

Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.

★ 13
Horonomos-laps
Horonomos-laps/Yana-AI

implementing-microsegmentation-with-guardicore

Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.

★ 13
Horonomos-laps
Horonomos-laps/Yana-AI

ramdisk-tmpfs-patterns

暂无简介

★ 13