chinayin
- 6 skills
- 0 followers
- 9 hours ago last updated
- ▌ Go · chinayin bundleTeam Go microservice architecture and coding standards. Use this whenever designing or writing Go code in this repo — HTTP services and handlers (gin), CLI commands (cobra), configuration (gox/config), database migrations (goose), or project scaffolding (Makefile/CI). Consult it any time you touch Go code or plan a Go module — including small changes like reading a single environment variable, secret, or config value — even if the user never says "standards".
- ▌
- ▌ Skill · chinayinRules for naming an agent skill, choosing its body language, and keeping environment facts out of it. Use whenever a skill is created, renamed, split, reviewed, or edited — writing a SKILL.md or its frontmatter, adding a skill to a repo or plugin, splitting an overloaded skill in two, versioning one, or deciding what a new skill should be called — even when the user only says "add a skill for X" or asks what to name it. Use it together with skill-creator, which owns the authoring process; naming and language are decided here.
- ▌ Delegate · chinayinToken-saving subagent routing. Use when facing token-heavy, read-heavy, conclusion-only work (reading Lark/Feishu in full or writing to it, wide code searches, log/long-document analysis) to decide whether to offload the work to a cheaper-model subagent and which tier to use.
- ▌ Frontend · chinayin bundleTeam frontend architecture and coding standards. Use this whenever designing or writing frontend code in this repo — React/Vue components, TypeScript/JavaScript, styling (CSS/SCSS), state management, data fetching, or build/tooling config (package.json, tsconfig, vite/eslint). Consult it any time you touch frontend code — including small changes like one component prop or a style tweak — even if the user never says "standards". Currently a skeleton — core rules are TODO; confirm conventions with the team instead of guessing.
- ▌