Loading...
Loading...
Found 3,836 Skills
Translate Figma designs into production-ready code with 1:1 visual fidelity. Useful for handing off Figma frames straight to a frontend agent.
Create, edit, and analyze Word documents with tracked changes, comments, and formatting. Useful for design briefs, copy docs, and review-ready deliverables.
A collection of Agent Skills for the Stitch MCP server: generate high-fidelity UI screens, create multi-page websites from a single prompt, produce DESIGN.md documentation, enhance vague UI prompts, convert designs to React/shadcn-ui components, and generate walkthrough videos via Remotion. Use when the user needs AI-assisted UI design generation, prompt refinement, or screen-to-code workflows. Triggers on: stitch, stitch-design, stitch-loop, enhance-prompt, react-components, remotion, shadcn-ui, screen generation, ui generation.
Evidence-first research, architecture discovery, vendor documentation review, benchmark reading, and unknown-system analysis.
Replace with a trigger-style description of when this skill should activate. Be specific — this is what the agent uses to decide whether to load the skill. Example: "Sui TypeScript SDK integration. Use when writing, reviewing, or debugging TypeScript code that interacts with Sui RPCs, transactions, or on-chain state."
Update or repair Luma / 拾光 / 拾光智能体 / 拾光工具 / 拾光运营套装 by updating luma-cli and syncing agent skills.
An AI Agent Skill that enforces a 'Risk Triage -> Align -> Act' protocol. Triggers when requests are vague, conflict-ridden, or high-impact. Do not activate for low-risk or precise, scoped requests.
Post-completion self-review for coding agents that runs simplify, harden, and micro-documentation passes on non-trivial code changes. Use when: a coding task is complete in a general agent session and you want a bounded quality and security sweep before signaling done. For CI pipeline execution, use simplify-and-harden-ci.
Play blackjack with the agent as dealer. The agent manages game state, deals cards, and sends card images.
Maintain /do routing tables and command references when skills or agents are added, modified, or removed. Use when skill/agent metadata changes, after skill-creator-engineer or agent-creator-engineer runs, or when routing tables need synchronization. Use for "update routes", "sync routing", "routing table", or "refresh /do". Do NOT use for creating new skills/agents, modifying skill logic, or manual /do table edits.
Session orientation and awareness — retro summaries, handoffs, git state, focus. Use when starting a session, after /jump, lost your place, switching context, or when user asks "now", "where are we", "what are we doing", "status", "recap". Do NOT trigger for "standup" or "morning check" (use /standup), or session mining "dig", "past sessions" (use /dig).
This is used when users want to learn about industry hotspots, check topic challenge rankings, view recent hot search events or public domain popularity trends. It supports two dimensions: topic challenges and hot list events. Manual trigger: /trending