Software Development Skills

Use when the user challenges an existing proposal, asks whether it is the best solution, asks for a better approach, or wants second-pass review of the chosen best-standard, tradeoffs, scope, compatibility, risk, or refactor depth before implementation.

Use when the user asks to write or edit development-time content, website or page copy, requirement notes, implementation docs, version notes, release notes, or temporary project documentation, especially when reference material, examples, chat history, or implementation process could pollute the target artifact.

Use when the user asks how to design or implement a new feature, capability, workflow, page, API, or behavior before coding. Do not use for bug fixes, intentional changes to existing behavior, pure refactors, or second-pass solution challenges.

Use when the user asks why existing behavior is broken, incorrect, flaky, regressed, unexpected, or runtime/build behavior is failing and wants a bug-fix approach before coding. Do not use for planned feature changes, pure refactors, or second-pass solution challenges.

Use when the user asks how to improve, extend, adjust, or redesign an existing feature or behavior before coding. Do not use for brand-new features, broken behavior, pure refactors, or second-pass solution challenges.

Use when the user asks how to refactor, split modules, clarify architecture, move ownership, reduce coupling, or fix unclear state, data-flow, or component boundaries before coding. Do not use for ordinary feature work, bug fixes, or second-pass solution challenges.

Use when the user asks to review implemented code for code style, redundancy, unnecessary abstractions, wrappers, helpers, adapters, parsers, type guards, TypeScript type noise, or composable usage clarity. Do not use for solution design, bug diagnosis, refactor planning, or commit messages.

Use when the user wants user-facing docs for an implemented feature. Inspect the real implementation first, then write help-center, site-copy, and in-product docs under doc/{requirement-name}/.

Convert UI drafts such as screenshots, HTML drafts, local file:// prototype pages, or mockups into frontend pages inside an existing project. Reuse existing components and styles, and keep the provided layout structure close to the source draft unless the user asks for redesign.

Generate or improve structured daily work reports from brief task notes, tomorrow plans, screenshots, report forms, historical reports, or review feedback. Use when the user asks to write, organize, polish, or improve a daily report, 日报, or daily work summary and needs factual completion results, gaps, blockers, actionable next steps, reflections, or project-aware wording.

Use as always-on project rules for agent behavior in any repository. Enforce Chinese replies, senior engineer style, simple maintainable production-oriented solutions, low-complexity code, clear APIs, and no state-changing git commands unless explicitly requested.

Use when generating reusable signature-style SVG assets, Vue components, or React components from font files, including personal signatures, handwritten wordmarks, font-derived SVG paths, or mask-based handwriting animations. Use only when the user wants font-based output, not general logo design.

Use when the user asks for an implementation plan, bug-fix approach, best solution, root-cause analysis, refactor strategy, tradeoff discussion, or wants to discuss how to solve a problem before coding.

Split an imported Pencil .pen design file into one folder per top-level Frame, including exact current Pencil selections by node IDs, each containing index.pen and local image assets referenced by that frame.