omk-design-md
Generate, read, validate, diff, and apply Google DESIGN.md files for Kimi UI/frontend tasks, Tailwind themes, screenshots, and visual coding.
git clone --depth 1 https://github.com/dmae97/open-multi-agent-kit /tmp/omk-design-md && cp -r /tmp/omk-design-md/templates/skills/kimi/omk-design-md ~/.claude/skills/omk-design-mdSKILL.md
## Use When Use this skill when: - creating UI - modifying frontend components - reviewing screenshots - converting mockups into code - generating landing pages - working with Tailwind, shadcn/ui, React, Next.js, or design tokens ## Rules 1. Read `DESIGN.md` before UI implementation if it exists. 2. If `DESIGN.md` does not exist, infer a minimal design system from existing UI. 3. Do not invent arbitrary colors if tokens exist. 4. Validate `DESIGN.md` when the CLI is available: ```bash npx @google/design.md lint DESIGN.md ``` 5. For major design changes, create `DESIGN.next.md` and compare: ```bash npx @google/design.md diff DESIGN.md DESIGN.next.md ``` 6. When using Tailwind, export tokens if needed: ```bash npx @google/design.md export --format tailwind DESIGN.md > tailwind.theme.json ``` 7. When a named visual reference is requested, use the bundled `awesome-design-md` skill and OMK catalog commands: ```bash omk design search <keyword> omk design apply <name> ``` ## Output ```txt Design source: Tokens used: Components affected: Accessibility risk: Commands run: ```
Persistent memory, recall, session replay, and memory-governance workflow adapted from rohitg00/agentmemory for OMK. Use when setting up agent memory, deciding what to remember, importing/replaying sessions, reducing repeated context, or auditing memory safety.
Minimal, goal-driven, surgical coding workflow adapted from forrestchang/andrej-karpathy-skills for OMK. Use for coding, refactoring, debugging, and review tasks where assumptions, overengineering, or broad edits could cause regressions.
Legal workflow drafting, triage, review, research planning, legal operations, law-student or clinic support, and legal AI governance adapted from Anthropic claude-for-legal. Use for commercial, privacy, product, corporate, employment, regulatory, AI governance, IP, litigation, legal-clinic, and law-student tasks. Draft-only; attorney review and current source verification required.
Real-engineering alignment, shared-language, TDD, diagnosis, and architecture-review workflow adapted from mattpocock/skills for OMK. Use before non-trivial implementation, ambiguous product work, debugging loops, test-first changes, or codebase architecture cleanup.
Managed-agent teamwork, issue assignment, progress tracking, reusable-skill compounding, and handoff workflow adapted from multica-ai/multica for OMK. Use when coordinating multiple agents, converting work into agent-ready tasks, tracking blockers, or turning repeated solutions into skills.
Review AdaptOrch, OMK, and similar DAG multi-agent orchestration frameworks. Use when assessing DAG node responsibility, dependency edges, worker write authority, fallback/retry/timeout/evidence gates, review/merge boundaries, or reproducible decision traces.
Optional read-only OMK web/social/video research workflow inspired by Panniantong/Agent-Reach. Use for web search, current social evidence, YouTube/Bilibili/Reddit/Twitter/X/RSS/GitHub public research, and Agent Reach availability checks without auto-installing or collecting credentials.
Backend API review for NestJS, Express, FastAPI, database access, validation, auth, error handling, and API contracts.