Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics.
审查或改进前端 UI 的语义结构、键盘支持、焦点管理、标签以及常见的 WCAG 相关问题，并将报告保存为 Markdown 文件。当用户提到无障碍、accessibility、a11y、WCAG，或在实现交互组件时自动激活。
Make your AI dare not slack off. Enhanced version for Web architecture refactoring. Triggers: (1) Task failed 2+ times or repeated fine-tuning same approach; (2) About to say 'I can't solve', suggest manual operation, attribute to environment without verification; (3) Passive waiting - no search, no reading, just waiting for instructions; (4) User frustration: 'try harder', 'stop giving up', 'change approach'; (5) Web refactoring: changed JS forgot HTML/CSS, multi-file omissions. Applies to all tasks, especially frontend refactoring.
Track tickets, issues, and progress for your project. Load project context, manage sessions, guide setup.
E2E 除錯說明書——用 agent-browser CLI 在 DDD 工作流中系統性地除錯前端問題。 Use when E2E tests fail, when you need to visually verify UI behavior, debug form submissions, inspect page state, or trace frontend issues during "/DDD.work". Also use when the user says "debug E2E", "check the page", "why is the test failing", "open the browser", "take a screenshot", "inspect the DOM", or invokes "/DDD.agent-browser". --- # DDD:AgentBrowser — E2E 除錯說明書 在 DDD 工作流的開發階段（`/DDD.work`），當 Playwright E2E 測試失敗或需要視覺驗證時， 用 `agent-browser` CLI 直接操作瀏覽器來定位問題。 這份說明書不是瀏覽器自動化教學，而是**除錯流程指南**——幫你從「測試掛了」走到「找到根因」。 ## 核心除錯循環 ``` 測試失敗 → 重現場景 → 觀察狀態 → 定位根因 → 修正 → 驗證 ``` 每一步都有對應的 agent-browser 指令，按順序走就對了。 ## Step 1：重現場景 先把瀏覽器帶到測試失敗的那個畫面。 ```bash # 開啟目標頁面
Use when looking up library documentation, API references, framework patterns, or code examples for ANY library (React, Next.js, Vue, Django, Laravel, etc.). Fetches current docs via Context7 REST API. Triggers on: how to use library, API docs, framework pattern, import usage, library example.
Scaffolds a new TypeScript application using the @rotorsoft/act event sourcing framework. Translates functional specs — event modeling diagrams, event storming artifacts, or user stories — into a working monorepo with domain logic, tRPC API, and React client. Use when the user wants to build a new app, create a new project, or translate a domain model into code using Act.
Autonomous Agile Project Lifecycle — transforms a raw idea into a deployed project following the AIOX Agentic Agile process. Runs 5 phases autonomously: Discovery (web research), Planning (PRD + Architecture + Frontend Spec), Sharding (stories in waves), Development (build + QA loop), Delivery (deploy + release notes). Decides stack, prioritizes features, writes code, reviews quality, and ships — all without human intervention. Supports greenfield and brownfield projects. Use when: starting a new project from scratch, adding features to existing project, or wanting full agile cycle automated.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Debugging guide for broken gdansk integrations. Use when a gdansk widget fails to register, the frontend bundle or SSR runtime does not start, a `Ship` views path is wrong, widget output or CSS is missing, host and port configuration disagree, or an existing gdansk MCP app needs error-driven diagnosis.
Scaffold a complete StrataSync app with Next.js client and Fastify server (models, sync, IndexedDB, WebSocket, PostgreSQL)
分析前端项目源码并全量生成或重建 widget-knowledge-system Skill（路由索引与页面级操作文档）；适用于首次建库、历史文档质量较差或发生大范围重构后的整体重建
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills:
