skills.rest
getyak
getyakOFFICIAL
Explore all skills by this author →
WebsiteGitHub

talent-signal-conventions

Applies TypeScript coding conventions, testing patterns, and commit guidelines for the talent-signal repository.

1|Updated Aug 3, 2026
Search Tags:#typescript#vitest#testing#commit messages#code style#monorepo#conventions
One-click install
npx skills add https://github.com/getyak/talent-signal --skill talent-signal-conventions-getyak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: talent-signal-conventions
Source: https://github.com/getyak/talent-signal/tree/main/.agents/skills/talent-signal
Command: npx skills add https://github.com/getyak/talent-signal --skill talent-signal-conventions-getyak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors to the talent-signal repository need to match its established TypeScript style, vitest testing patterns, import conventions, and commit message format without manually auditing existing code. ## Core Features & Use Cases - Code Style Guidance: Enforces camelCase files and functions, PascalCase classes, SCREAMING_SNAKE_CASE constants, named exports, and @/ path alias imports. - Testing Conventions: Documents the vitest framework, *.test.ts file naming, and describe/it/expect test structure used across the project. - Commit & Error Handling Patterns: Captures free-form imperative commit messages and standard try-catch error handling with user-friendly messages. - Use Case: When adding a new feature to the talent-signal monorepo, activate this skill so generated code follows the existing import style, test layout, and naming rules automatically. ## Quick Start Use the talent-signal conventions skill to write a new vitest unit test and TypeScript module that follow this repository's established patterns.

Frequently Asked Questions about talent-signal-conventions

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

FAQPage Schema
How do I write tests for the talent-signal repository?▼

Write tests using vitest with the describe/it/expect structure in files matching the *.test.ts pattern. Tests should cover individual functions and components in isolation, following the unit test style documented in the project conventions.

What import style does the talent-signal codebase use?▼

The codebase uses path aliases such as @/ and ~/ instead of long relative imports, combined with named exports. For example, import components as import { Button } from '@/components/Button'.

What commit message format should I use in this repository?▼

Use free-form commit messages in imperative mood, keeping the first line concise at around 36 characters. Examples include 'Expand candidate evidence workspace' and 'Document shared product architecture'.

What naming conventions apply to TypeScript files in talent-signal?▼

Files and functions use camelCase, classes use PascalCase, and constants use SCREAMING_SNAKE_CASE. Following these conventions keeps new code consistent with the existing hybrid module organization.

When should I not rely on this conventions skill?▼

The conventions were auto-generated from a small sample of two commits, so they may not cover every pattern in the repository. For unusual architectural decisions, review existing code directly and discuss deviations with the team.

Related Skills

Explore More Software Engineering Skills→
Eng0AIEng0AI
15

nextjs-supabase

Scaffold a Next.js and Supabase project with environment configuration.

Official
Intermediate
HugoRCDHugoRCD
1.8k

contributing

Guides contributors through evlog commit conventions, changesets, testing rules, and PR workflows.

Community
Intermediate
guichefferguicheffer
3

imports-exports

Enforce ESLint rules for TypeScript import ordering and named exports.

Community
Intermediate
TheCardGoatTheCardGoat
14

nx-import

Import external repositories into Nx workspaces while preserving git history.

Official
Advanced