Design e Frontend

65 plugins that turn Claude Code into an autonomous development team. 24 agents, 34 skills, 5 hooks. Includes 12-plugin anti-hallucination suite. One-line install.

Extract Lanhu design HTML, CSS, and assets through Lanhu MCP for Claude Code design-to-code workflows. Called by design-to-code.

Aplica o TRIZ de Altshuller (Teoria da Resolução Inventiva de Problemas) para resolver contradições de engenharia e gerar conceitos inventivos, evitando soluções de compromisso. É acionado ao descrever um trade-off técnico, contradição física, gargalo de design ou explicitamente.

Implements features in vertical slices, always starting with homepage. Enforces anti-placeholder rules — no lorem ipsum, no TODO stubs, no gray boxes. Real content, real images, real interactions. TypeScript strict mode, Zod validation, and structured file organization.

开发任务执行 skill。读取 task README 与 dev-checklist，按依赖实现、写 verify 证据，并由 README risk 驱动交付或 Gate ②。 触发：`x-dev <功能名称>` 或现有 task 目录。

系统方案规划 skill。产出 docs/spec/<spec-name>/ 下的独立需求包（目标与 DoD + 组件设计 + 接口/数据结构 + 核心流程时序 + 验证策略 + task 映射）。 当用户给的是模糊想法而非具体功能需求时使用。触发场景： "这个东西怎么设计"、"帮我梳理整体方案"、"先别写代码把方案理清"、 "这个系统该怎么拆"、"x-spec"、架构级改造、 一个系统切面会派生多个 task 需要先建 spec 需求包。上下文不足时先进入头脑风暴模式，收敛后再保存 spec 文档。 入口选择：小功能小修复由 x-req 定级 Q0/Q1；已有明确需求走 x-req。

Archive a completed, rejected, or covered feature into .feature-radar/archive/ with mandatory learning extraction. MUST use this skill whenever a feature reaches a terminal state — done, rejected, covered, deferred, or N/A. Even casual mentions like "we shipped X" or "X is done" should trigger this. The skill extracts learnings, derives new opportunities, and updates refs. Use when the user: - Say

Scan your support inbox and batch-process tickets with quick actions (reply, tag, assign, close)

Full-cycle feature discovery, evaluation, and prioritization. Builds a persistent knowledge base at .feature-radar/ and runs a 6-phase workflow to recommend what to build next. Modes: full (all phases), quick (scan only), evaluate (prioritize), #N (deep-dive one). MUST use this skill whenever the user asks about feature priorities, roadmaps, what to build, or wants to evaluate/compare feature idea

Novel writing assistant supporting creating novels from scratch, continuing chapters, character design, and worldbuilding. Works with all genres (sci-fi, fantasy, mystery, romance, wuxia, etc.). Triggers: (1) User requests to write a novel, e.g., "help me write a sci-fi novel", "create a mystery story"; (2) Continue or modify existing content, e.g., "write the next chapter", "modify this character

Use this skill when asked to "validate plugin", "check plugin structure", "verify plugin", "audit plugin", "is my plugin correct", "plugin issues", or when troubleshooting plugin problems.

Record external observations, ecosystem trends, and creative inspiration into .feature-radar/references/. MUST use this skill when the user mentions something interesting from outside their project — other tools, articles, approaches, or trends. Even casual mentions like "I saw a cool thing in X" should trigger this skill. Use when the user: - Says "I saw this cool thing in X's API", "check out ho