global-healing

Enforces ESG GO project standards for TypeScript, Next.js, and bilingual documentation across workspaces.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/DingJun1028/esggo-kv --skill global-healing-dingjun1028
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: global-healing
Source: https://github.com/DingJun1028/esggo-kv/tree/main/.agents/skills/esggo-standards
Command: npx skills add https://github.com/DingJun1028/esggo-kv --skill global-healing-dingjun1028

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams working across multiple workspaces and agents often drift into inconsistent naming, weak typing, and mismatched UI styles. This Skill enforces the ESG GO project's core architectural and linguistic principles so every contribution follows the same standards. ## Core Features & Use Cases - Bilingual Content Standard: Standard documentation and code naming in English, with user-facing content in professional Traditional Chinese. - Full-stack Type Safety: Enforces strict bidirectional TypeScript between frontend and backend, banning any and requiring shared type definitions. - Next.js & UI Consistency: Mandates Next.js App Router best practices and requires all UI/UX to be generated with Google Stitch (StitchMCP) for a unified premium aesthetic. - Use Case: When an agent scaffolds a new Next.js feature in any workspace, this Skill ensures it uses typed props, English identifiers, Traditional Chinese UI copy, and Stitch-generated design components. ## Quick Start Apply the global-healing standards to review this Next.js component for type safety, naming conventions, and bilingual content compliance.

Frequently Asked Questions about global-healing

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

FAQPage Schema
How do I enforce coding standards across multiple workspaces?▼

Apply this Skill globally so every agent and workspace follows the same rules: English code naming, strict TypeScript without any, Next.js App Router structure, and StitchMCP-generated UI. It acts as a shared guideline layer rather than a linter.

What language should user-facing content use in this project?▼

User-facing content must be written in Traditional Chinese with professional phrasing, while documentation, variable names, functions, and classes use descriptive English. This bilingual split is a core principle of the standard.

Does this standard require a specific UI design tool?▼

Yes, all UI/UX designs must be managed and generated using Google Stitch (StitchMCP). Screens should use StitchMCP tools to generate, edit, and apply design systems for a consistent premium aesthetic.

Can I use the any type in TypeScript under this standard?▼

No, the standard explicitly prohibits any. All props, data models, and API responses must use interfaces and types, with shared type definitions between client and server for bidirectional type safety.

When should this Skill not be applied?▼

It is designed specifically for the ESG GO project ecosystem. Applying it to unrelated projects with different language requirements, non-Next.js stacks, or different design tooling would impose irrelevant constraints.