AI Agent Hub
Back to skills
🏢

Real Estate Engineering Assistant

Business Operations Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @kunlungrowth/kunlun-realestate-agent according to https://skillhub.cn/install/skillhub.md.

About this skill

Problem area

Real estate engineering work often spans listings, showings, follow-up, contracts, and commission calculations. Engineers can stall when PR review lacks clear criteria, API contracts keep changing, production errors are hard to locate, or architecture options need cost and scale tradeoffs. This skill supplies reusable engineering methods, templates, and checklists for those situations.

How it works and limits

It routes by trigger phrases. review produces severity-based feedback; design/solution produces background, goals, choices, and risks; debug/troubleshooting produces reproduction steps, a decision tree, and validation; architecture/selection produces pros, scale, and cost; API/interface produces resource contracts, fields, and error codes; standards/best practices produces checklists and anti-patterns. For PR / diff, it prioritizes intent, correctness, security, and maintainability before giving blocking, suggested, and optional findings; for production incidents, it requires stable reproduction, isolation of environment/data/version, and validation with logs and metrics. It favors correctness and evidence over style, and prefers incremental architecture migration. It does not process real secrets, connect to external services, or replace professional qualifications; owners remain responsible for merge and business decisions.

Use Cases

  • Review listing and showing module PRs, producing blocking, suggested, and optional issues by correctness, security, and maintainability.
  • Trace a production commission settlement error using stable reproduction, variable isolation, log evidence, and fix validation.
  • Design customer follow-up APIs with REST resources, field contracts, error codes, and version compatibility notes.
  • Compare monolith and microservice migration paths, producing scale, pros/cons, cost, and rollback options.

Best For

  • Frontend engineers owning listing and contract backend APIs who need field contracts and error codes before integration.
  • Technical leads for showing workflows who need selection tradeoffs and rollback plans before architecture changes.
  • DevOps engineers maintaining real estate systems who need production errors turned into reproduction steps, evidence, and validation.
  • Full-stack engineers building brokerage admin tools who need review checklists and anti-pattern checks for PRs and standards.