wenrizc

用于把尚未清晰的想法、新需求、产品/交互/技术方案、实现计划等收敛成可执行设计。适用于从零到一或尚未定型的讨论、需求澄清、方案取舍和设计记录草拟等

创建具有鲜明风格和生产级品质的前端界面。用户要求构建 Web 组件、页面或应用时使用本 skill。生成有创意、打磨充分、贴合场景的代码。

使用 TDD 和通用工程规范创建、修改、重构或评审代码。用户要求实现功能、修复 bug、补测试、重构代码、评审改动，或希望在前端、后端、脚本、工具和应用开发中遵循测试优先与工程质量标准时使用本 skill。

当用户想进行系统设计模拟面试、系统设计题目练习时使用。

基于近期公开网络来源创建英文付费金融媒体风格的全球市场简报。需要调研当前市场新闻、宏观催化、行业主题和热点，并识别分析相关全球股票、ETF、基金、商品、加密资产或其他市场工具，形成带引用的精炼 Markdown 编辑观察清单时使用。除非用户明确要求其他语言，默认输出英文。

审查已有软件项目、已有仓库或已有实现的当前设计。用户要求基于现有代码或文档审查架构形态、模块边界、依赖方向、数据流、状态流、业务工作流、系统边界、设计债、遗留系统现状，或按传入目标找设计问题时使用。调用时应根据用户已经给出的审查目标直接确定范围并完成审查。

帮助用户发现并安装 agent skills。用户询问“如何做 X”“找一个做 X 的 skill”“有没有能做某事的 skill”，或表达想扩展能力时使用本 skill。

Use when Codex needs to clarify, shape, pressure-test, or converge a vague idea, feature request, product direction, system design, implementation plan, or creative proposal before execution. Trigger when the user asks to be grilled, challenged, questioned, brainstormed, scoped, designed, or clarified; when the user asks for grouped questions with options; or when important design choices remain unclear before coding or producing a deliverable. This skill inspects available context, selects an Explore/Decide/Document mode, adapts question volume to complexity, may propose 1-2 candidate directions before asking targeted questions, handles large designs by phase or module, tests assumptions, converges decisions, and writes design records when the discussion size or handoff/implementation needs justify it.

Use when the user wants realistic system design interview practice, mock interview simulation, adaptive interviewer-style probing, scenario design questions, or post-interview debriefs and scorecards for architecture interviews.

Review an existing software project's design as a staged consultant. Use when the user asks Codex to audit a whole project, explain how features are implemented, discuss architecture or module boundaries, compare implementation approaches, find design debt, research comparable open-source or company systems, or create an improvement roadmap. Prioritize architecture, dependency direction, business workflows, feature design, tradeoffs, and staged discussion over narrow line-by-line code review.

Use when given course materials such as PPT, PDF, Markdown notes, or mixed lecture files and asked to produce a review outline, study plan, knowledge-point summary, selected high-frequency exam problems, formula sheets, or other exam-prep artifacts from them, especially when course context or likely test focus must be supplemented with web research.