awesome-design-md
Use VoltAgent awesome-design-md as a curated DESIGN.md template catalog for OMK, Kimi, and Open Design UI/prototype work.
git clone --depth 1 https://github.com/dmae97/open-multi-agent-kit /tmp/awesome-design-md && cp -r /tmp/awesome-design-md/templates/skills/kimi/awesome-design-md ~/.claude/skills/awesome-design-mdSKILL.md
# /awesome-design-md Use the VoltAgent `awesome-design-md` catalog when a UI, prototype, or visual task needs a named reference style. ## Commands ```bash omk design list omk design search <keyword> omk design apply <name> omk design lint DESIGN.md omk design diff DESIGN.md DESIGN.next.md ``` ## Workflow 1. Read the local `DESIGN.md` first when it exists. 2. If the user requests a style reference, search the catalog: ```bash omk design search vercel ``` 3. Apply only when replacing the project design source is intended: ```bash omk design apply vercel ``` 4. For exploratory work, copy the selected template into `DESIGN.next.md`, compare it, then adapt. 5. In Open Design, choose the **Awesome DESIGN.md Web UI Reference (OMK)** prompt template, set the catalog name, and run it with the OMK CLI agent. ## Guardrails - Treat catalog entries as design-system references, not brand-cloning permission. - Preserve product-specific content, accessibility, responsive behavior, and local tokens. - Do not paste secrets, credentials, private screenshots, or private customer data into prompts. - Cite the selected catalog name and any local files inspected in the final result. ## Output ```txt Catalog source: Selected template: Local DESIGN.md action: Open Design template: Commands run: Risk: ```
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.