Haochuan Zhang avatar

Haochuan Zhang

Community

@lunarmoon26

12Followers
|
33Public Repos
|
9Published Skills

Haochuan Zhang's skill registry covers polyglot code standards, image asset processing, architecture documentation, and evidence-driven engineering research practices.

Skills Distribution
DomainDeveloper To...Polyglot Code Stan.. (30%)Architecture Docum.. (25%)Image Asset Proces.. (20%)Research & Spec-Dr.. (15%)

Agent Skills by Haochuan Zhang

Showing 9 vetted skills indexed across 2 GitHub repositories.

Frequently Asked Questions About Haochuan Zhang

FAQPage Schema
What tasks can I accomplish with lunarmoon26's skills?▼

You can enforce Python, TypeScript, Java, and C# coding conventions; edit images including resizing, masking, Magic Wand-style selection, transparent icons, and sprite sheet splitting; write architecture briefs and ADRs; conduct evidence-led codebase research; run document-driven spec-first engineering; and write Chinese from-scratch technical breakdowns.

Who should use these skills?▼

Polyglot software engineers maintaining code quality standards, developers producing image and icon assets, and architects documenting system design decisions benefit most. Technical writers creating Chinese-language derivations of frameworks, runtimes, or protocols for general CS audiences are also a target persona.

What are the runtime prerequisites for the photo-processing skill?▼

The photo-processing skill requires uv installed on the system. Its bundled scripts pin the Pillow imaging library using PEP 723 inline metadata, so dependencies resolve automatically at execution time without manual environment setup or separate package installation steps.

When should I use research-driven-development versus document-driven-development?▼

Use research-driven-development to investigate codebases, compare implementations, find prior art, or validate designs against source before consequential choices. Use document-driven-development for spec-first work, PRDs, docs-to-code drift repair, and externally visible behavior changes requiring contract updates.

When should the lightweight-architecture skill not be used?▼

Do not use lightweight-architecture for routine feature documentation or exhaustive comparative codebase research. It is scoped to architecture briefs, arc42-style views, system boundaries, quality scenarios, risks, architecture reviews, ADRs, and superseding accepted decisions without a heavyweight research program.