wakeup-jin/team-skill-init

Overview

This skill captures a team's full-stack TypeScript development standards for React frontends, Koa backends, Prisma database access, RESTful APIs, auth modules, and Git workflows. It helps authors write, review, and validate code against the team's conventions to ensure consistency, reliability, and predictable delivery.

How this skill works

The skill inspects code and PRs against a compact decision matrix for backend layering, a fixed hook→event→render order for React components, and a three-level state guidance (local → Context → global). It validates API route naming, response envelope format, error code scheme, commit message style, branch naming, and available project configs and scripts for linting and formatting.

When to use it

• When implementing a new React component or front-end feature
• When building Koa controllers, routing-controllers endpoints, or backend services
• When designing or reviewing RESTful API endpoints and response contracts
• When authoring Prisma queries and database access logic
• When adding or auditing authentication and authorization modules
• When creating commits, branches, or preparing a PR for team review

Best practices

• Apply the backend layering decision tree: Controller + (DoService +) Service for complex business or transactions
• Follow Hooks → event handlers → rendering order inside React components
• Keep state scope minimal: prefer local, escalate to Context, then use global stores like Zustand/Redux
• Use /api prefix, plural resource names, and lowercase-kebab for routes; responses must be { code, message, data }
• Use five-digit error codes XXYYZ (XX HTTP, YY module, Z subcode) and conventional commit messages
• Run provided lint and format scripts before committing and include checks in CI

Example use cases

• Implement a paginated Products API: create controller, service, and Prisma queries following the response envelope
• Add a new React form component: structure with hooks first, wire event handlers, then render UI
• Design an auth guard: follow the auth module reference and map errors to the team's error code ranges
• Review a PR to ensure routes use /api, resource names are plural, and commit message follows the type: subject format
• Refactor a service that spans transactions: add DoService for orchestration and ensure transaction boundaries