houseprice-skill-template

Author HousePrice skill markdown files with YAML frontmatter and Chinese-first content.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/chuangkevin/project-bridge --skill houseprice-skill-template
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: houseprice-skill-template
Source: https://github.com/chuangkevin/project-bridge/tree/main/skill/houseprice/common/houseprice-skill-template
Command: npx skills add https://github.com/chuangkevin/project-bridge --skill houseprice-skill-template

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent authoring and discovery of HousePrice domain skills by prescribing structure, language conventions, and validation steps so that business knowledge not visible in code is captured reliably and searchable across the repo.

Core Features & Use Cases

  • Frontmatter requirement: Mandates YAML frontmatter with name and description for discovery and indexing.
  • Authoring rules: Defines language, content scope (what to include vs exclude), and guidance for when to split a large skill into subfiles.
  • Validation & sync workflow: Prescribes verification of inferred conclusions, updating blockers-and-questions, and recording dependency maps across projects.
  • Use case: Create or update a houseprice payment or listing skill that references code locations, marks legacy enums, and syncs blockers and dependencies with the project mapping.

Quick Start

Create a new houseprice skill by copying the SKILL.md template, filling the YAML frontmatter name and description, writing content in Chinese with technical terms in English, and adding sub-topic markdown files as needed while updating blockers-and-questions and dependency mappings.

Frequently Asked Questions about houseprice-skill-template

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize markdown skill authoring for a repository?

To standardize markdown skill authoring, use a template that mandates YAML frontmatter with name and description, Chinese-first content with English technical terms, and explicit validation steps to ensure consistent documentation and discovery.

What is the best way to document business knowledge not visible in code?

Documenting business knowledge not visible in code requires applying authoring rules that prescribe content scope, reference code locations, mark legacy enums, and sync blockers and dependency maps to capture domain logic reliably.

How do I split a large skill markdown file into indexed subfiles?

Splitting a large skill markdown file into subfiles requires following template guidance to create indexed sub-topic markdown files, ensuring the original YAML frontmatter and Chinese-first content conventions are maintained across the repository.

How do I validate inferred code conclusions when writing skill documentation?

Validating inferred code conclusions involves applying explicit verification steps prescribed by the authoring template, ensuring that inferred technical logic is tested and synced with project blockers-and-questions and dependency mappings.

Does a skill template require YAML frontmatter for repo mapping and indexing?

Yes, a skill template requires YAML frontmatter with name and description fields to enable proper repository indexing, coordinate dependency maps, and ensure consistent discovery of houseprice-related markdown files.

Can I use English technical terms in a Chinese-first skill documentation format?

Yes, the Chinese-first skill documentation format explicitly requires writing content in Chinese while retaining technical terms in English, ensuring domain knowledge is accessible and accurately mapped across the repository.