Design e Frontend

This skill should be used when exploring requirements and approaches through collaborative dialogue before planning implementation.

This skill should be used when Pencil MCP tools are unavailable. Detects Pencil Desktop or a Pencil-extension IDE and registers the MCP server with Claude Code CLI.

Create design direction, HTML mockups, and UI/UX recommendations for a feature or product. Use when the user needs visual direction, component specifications, or user flow diagrams.

This skill should be used when working with DSPy.rb, a Ruby framework for type-safe, composable LLM applications.

This skill should be used when draining a labeled issue backlog (deferred-scope-out, code-review, type/security) in one cleanup PR. Groups by code area and delegates to /soleur:one-shot.

Invoke when the user asks about game economy, currency design, monetization, virtual currency, inflation, sink/source balance, F2P economy, premium currency, loot boxes, season pass, battle pass economics, dual currency, or resource flow modeling. Triggers on: "economy", "currency", "monetization", "F2P", "premium", "loot box", "battle pass", "sink/source", "inflation", "resource flow". Do NOT inv

Designs churn prevention flows, payment recovery sequences, referral programs, and free tool strategies for customer retention and growth loops. Use pipeline-analyst for deal-level expansion metrics; use cmo for overall strategy; use this agent for systematic retention programs.

Use this agent when you need a brutally honest Rails code review from the perspective of David Heinemeier Hansson. Use kieran-rails-reviewer for strict convention and taste checks; use this agent for opinionated architectural critique.

Invoke for guided game design document authoring -- section-by-section GDD creation with validation, pillar alignment, and scope tier marking. Triggers on: "write GDD", "create GDD", "game design document", "document my game", "GDD authoring", "fill in GDD". Do NOT invoke for reviewing an existing GDD (use game-design-review) or designing specific game systems (use game-designer). Part of the Alte

This skill should be used when decomposing feature requirements into granular, implementable user stories. It applies Elephant Carpaccio slicing, INVEST criteria, and story prioritization.

Use when the user asks to design, plan, or explore approaches before implementing — creating features, building components, or adding functionality that would benefit from design exploration first.

This skill should be used when provisioning Hetzner sub-projects and tokens for tenant infrastructure.