Art & Design

>- Designs and ships original SVG UI icons, from one custom icon to a consistent set. Icons are drawn on a 24px grid with pro design rules, then linted, optimized, previewed as PNG and emitted as zero-dependency React, Vue, Svelte or HTML-sprite components with accessible defaults. Use when the user needs sidebar icons, nav or navbar icons, dashboard icons, menu, toolbar or settings icons, an icon set, a custom icon or an SVG icon, or says "make an icon for…", "design icons for my app", or wants to replace emoji or placeholder icons, even if they never say SVG. It always draws its own icons instead of installing an icon library, and matches the style of a library the project already uses. Not for logos, brand marks, favicons or app-store artwork, illustrations, raster images, or icon-font setup.

Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

Design, pre-register, run or analyze an experiment (RQ1, RQ2, RQ3). Use when writing a pre-registration, choosing arms, measures, sample size or statistics, planting facts, or interpreting results.

Universal game-design rules for any 2D or 3D game, any genre. Use when designing or implementing game mechanics, collision, physics, movement, game loop, state machines, win/lose conditions, or scoring, or when reviewing a game's rule structure for consistency.

Analyze supplied UI or graphic references and turn aesthetic observations into reusable design decisions and review criteria. Use for 学习设计审美、提炼设计特点、培养 agent 审美 or explaining why a visual works and how to adapt it to another context.

引導 AI 代理進行高品質的 UI/UX 與遊戲設計。當使用者提到「畫面不好看」、「介面想優化」、「設計 UI」、「開發遊戲」、「想要精緻感覺的 UIUX」或要求開發任何網頁/遊戲前端時，必須啟用此技能以確保產出具備現代感、精緻度、微動畫與優質人機互動體驗的成品。

Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

Use when user says brainstorm, plan, design, roadmap, architecture, ideas, tradeoffs, structure. Collaborative planning mode for any markdown-supported CLI agent.

Builds a branded Arabic Instagram carousel from any topic: the user gives the topic, and the skill analyzes it and designs the slides, asking only for brand details it cannot infer. Use for any carousel request.

Build a personal mindOS workspace and design system from the requesting person's own MINDPRINT. Use when someone wants software shaped around their own decision and working habits.

Automatic principal-level engineering baseline for production-code tasks in applications, APIs, workers, and monorepos. Apply during implementation, fixes, refactoring, and architecture review without requiring a skill name or trigger phrase. Group by domain then function, using scoped services, shared modules, and reusable engines. Trace created modules and changed paths for integration gaps, bugs, and required behavior; preserve explicit agent handoffs. Apply small fixes locally without triggering a repository restructure. Excludes prose-only work and generated or vendor edits.

Act as Ruwan, the UI/UX Designer for Openmuns. Use when researching user needs, planning user flows, creating wireframes or prototypes, defining visual design systems, reviewing usability, or coordinating design handoff with web and app developers.

Automatically apply an evidence contract whenever creating, reviewing, or revising a nontrivial implementation plan, before substantial code edits begin. Grounds plan claims in repository evidence, labels assumptions as observed/inferred/unknown, identifies affected files and dependencies, and gives every plan item an executable success check. Use automatically for architecture plans, feature plans, bug-fix plans, refactors, migrations, implementation proposals, and requests to "plan", "design the implementation", "figure out how to build", or "review this plan". Skip for trivial, obvious single-line changes. Can also be invoked manually with /evidence-contract.

Create branded architecture, architecture delta, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, exploded axonometric, axonometric plan, Venn, pyramid/funnel, treemap and marimekko, heatmap, bar and dumbbell, waterfall, line (slopegraph, ridgeline, streamgraph, bump), Gantt and scatter charts (bubble, beeswarm), high-level, process, medallion, data flow, DP integration, DP security matrix, Sankey, fishbone, Wardley map, kanban, user journey, service blueprint, deployment, dependency graph, UML class, story map, or database schema diagrams as HTML/SVG/PNG, with .drawio, Mermaid, and .excalidraw import, plus lifecycle phase maps, block decomposition trees, and onboarding guidance.

Build an interactive, multi-slide "how it works" website for the current project — the idea behind it, the architecture, each component, with live simulations of its real logic — and publish it with GitHub Pages or GitLab Pages. Trigger on "how it works page/site", "explain this project as a slideshow", "interactive docs for this repo", "make a GitHub/GitLab Pages explainer", "/how-it-works-site".

도식, 다이어그램, 흐름도(플로차트), 조직도, 업무 프로세스, 구조도, 타임라인, 비교표 그림, 마인드맵 같은 그림을 그릴 때 사용한다. 한국어로 '도식 그려줘', '흐름도 만들어줘', '조직도 그려줘', '구조를 그림으로 보여줘'라고 해도 사용한다. Create branded diagrams (architecture, flowchart, org chart, timeline, funnel, journey and more) as HTML/SVG/PNG.

어떤 도메인의 프로젝트든 하네스 구조로 설계·구축하는 메타 스킬. Layer 1(메타): Planner→Generator→Evaluator 순환으로 워크스페이스를 설계한다. Layer 2(운영): 완성된 구조 안에서 도메인 에이전트들이 실제 업무를 수행한다. 두 레이어는 완전히 분리된다. Evaluator 90점+ PASS 후 cartesian-review 스킬을 자동 호출해 데카르트 5렌즈(열거·명증·종합·분석·방법적 회의)로 추가 품질 검증을 수행한다. cartesian-review 스킬이 설치되어 있어야 이 단계가 활성화된다. "하네스 만들어줘", "워크스페이스 설계", "에이전트 시스템 구축", "CLAUDE.md 만들어줘", "프로젝트 구조 잡아줘", "Council 구조 만들어줘", "반복 가능한 시스템", "자동화 워크플로우", "멀티 에이전트", "독립 분석", "다각도 분석", "build a harness", "design workspace", "agent system" 표현 시 반드시 사용.

코딩 에이전트가 코드를 안정적으로 생성·테스트·배포할 수 있는 하네스 구조를 설계하는 메타 스킬. Layer 1(메타): Planner→Generator→Evaluator 순환으로 코딩 하네스를 설계·구축·검증한다. Layer 2(운영): 완성된 하네스 안에서 코딩 에이전트가 실제 개발을 수행한다. "코딩 하네스 만들어줘", "개발 워크스페이스 설계", "에이전트 코딩 환경 구축", "CLAUDE.md 코딩 프로젝트용", "CI 파이프라인 설계", "코드 리뷰 루프 구축", "자율 코딩 환경", "에이전트 개발 환경", "coding harness", "agent-first development", "build harness for coding", "dev workspace setup", "autonomous coding environment" 표현 시 반드시 사용.

UI 以外のユーザー接点(API・設定ファイル/設定項目・拡張機能/プラグイン)を、UX の 6 原則に沿って設計・レビューする。API 設計、REST/SDK/クライアントライブラリの使いやすさ、config.yml や環境変数や設定項目の追加、拡張ポイント/プラグイン機構の設計、「設定を足すべきか」「デフォルト値をどうするか」「APIのバージョニング」「開発者体験(DX)」「オンボーディング」「驚き最小の原則」などの話題が出たら、明示的に UX と言われなくても必ず使う。システム設計の初期段階で UX を先に決めたいときにも使う。

데카르트 방법서설의 4규칙(열거·명증·종합·분석)에 방법적 회의를 더한 5렌즈로 어떤 문서·설계·계획이든 체계적으로 검토해 실행 가능한 결론을 도출하는 분석 스킬. 다음 표현이 나오면 반드시 이 스킬을 사용한다: - "데카르트 분석", "데카르트 관점으로", "방법적으로 검토" - "네 가지 관점으로 검토", "4가지 관점 분석" - "더하면 좋은 것 / 빼면 좋은 것 / 빼면 안 좋은 것 / 더하면 안 좋은 것" - "빠진 것 찾아줘", "군더더기 찾아줘", "핵심이 뭔지 봐줘" - "다른 관점에서 분석해줘", "외부 시각으로 봐줘" - "이 문서 체계적으로 검토해줘", "이 설계 분석해줘" - "/cartesian-review" - 하네스 Evaluator 단계에서 자동 호출 (harness-designer-workspace 통합) 호출 전에 사용자 의도를 3가지 관점(①검토 대상: 코드·문서·설계·의사결정 / ②검증 깊이: 경량·표준·엄격 / ③목적: 빠진 것 찾기·개선 제안·최종 승인)으로 간단히 확인한 뒤 진행한다. 사용자가 이미 명시한 경우 확인을 생략할 수 있다.

Makes Arabic output correct the first time. Covers right-to-left layout, connected letter shaping, mixed Arabic/English/number ordering, Arabic fonts and typography, numerals, dates, currency, and natural Arabic wording. Use it whenever the output will contain Arabic text or is meant for Arabic speakers. That includes websites and apps (HTML, CSS, Tailwind, React, Next.js, Vue, React Native, Flutter), Word/PowerPoint/PDF files, charts and images (matplotlib, Pillow, SVG, canvas), emails, SMS/WhatsApp/social posts, markdown, and plain text. Use it when the request is written in Arabic (e.g. "صمم صفحة", "اكتب رسالة", "تقرير", "بالعربي"). Use it when an English request mentions Arabic, RTL, right-to-left, bilingual English/Arabic, i18n for Arabic, or users in Saudi Arabia, the UAE, Egypt, the Gulf, the Levant, North Africa or the MENA region. Also use it to fix broken Arabic: reversed or disconnected letters, boxes instead of glyphs, wrong alignment, or punctuation and numbers on the wrong side.

Use this skill when building AI agents, designing multi-agent systems, integrating LLMs into applications, building RAG pipelines, working with vector databases, implementing MCP servers, or designing agent communication and orchestration patterns. Trigger on keywords like: agent, LLM, RAG, embeddings, vector DB, orchestration, tool use, memory, intent clarification, MCP, LangChain, LangGraph, CrewAI, AutoGen, Microsoft Agent Framework.

Interview the user about something they are ABOUT TO BUILD, before any of it is built — a feature, a system, an automation, a workflow, a document structure. Use when a plan exists only in their head or as a rough idea and the design decisions are still open: \"grill me\", \"interview me about this\", \"help me think this through before I build it\", \"what am I not deciding\", \"ask me what you need to know\". Works the design as a dependency tree, asking one answerable question per round (the one that unblocks the most decisions first) with a recommended answer attached, and never asking anything it could look up itself. BOUNDARY — this is front-loaded, for decisions not yet made. Reviewing a plan that already exists and stress-testing it for holes is the plc skill. Interrogating information someone else handed you is critical-thinking-walkthrough. If the thing is already written down and the question is \"is this any good\", it is not this skill.

Extracts the visual system from a reference site or pasted HTML (colour roles, type scale, spacing scale, radii, shadows, button/card/eyebrow anatomy, tone) and maps it onto the current project's existing tokens as a short token table. Use when the user shares a reference ("make it look like <site>", "in this style", a URL or HTML paste) before a redesign.