kirklin

Codify Kirk Lin's JavaScript/TypeScript project conventions and tooling configurations.

1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/kirklin/skills --skill kirklin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kirklin
Source: https://github.com/kirklin/skills/tree/main/skills/kirklin
Command: npx skills add https://github.com/kirklin/skills --skill kirklin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Kirk Lin's opinionated tooling provides a clear, ready-to-use blueprint for JS/TS projects, reducing decision fatigue and setup time by codifying conventions.

Core Features & Use Cases

  • Standardized project templates for ESLint/Prettier alternatives, TypeScript configuration, and monorepo scaffolding.
  • Guidance for library publishing, Git hooks, and pnpm catalogs to improve DX and consistency.
  • References to centralized setup guidelines and best practices for app development, linting, and tooling choices.

Quick Start

Follow Kirk Lin's recommended project setup to initialize a new repository with the described conventions.

Frequently Asked Questions about kirklin

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

FAQPage Schema
How do I set up a TypeScript monorepo with pnpm and consistent linting?

To set up a TypeScript monorepo with pnpm and consistent linting, you can apply opinionated tooling conventions that codify strict TypeScript configurations, centralized pnpm catalogs, and standardized ESLint setups to reduce decision fatigue and scaffolding time.

What is the best way to configure ESLint alternatives for a new JavaScript project?

Configuring ESLint alternatives for a new JavaScript project is best handled by applying codified, opinionated tooling blueprints that provide ready-to-use project templates and centralized setup guidelines for consistent linting across the codebase.

How do I configure Git hooks for a TypeScript library publishing workflow?

To configure Git hooks for a TypeScript library publishing workflow, apply opinionated tooling conventions that codify Git hook setups and publishing workflows, ensuring consistent execution and improved developer experience during releases.

Can I use these opinionated tooling conventions for existing JavaScript projects?

These opinionated tooling conventions primarily apply to starting new JavaScript projects, configuring monorepos, and scaffolding library publishing workflows, rather than retrofitting existing codebases with strict TypeScript configurations.

Why use centralized pnpm catalogs in a JavaScript monorepo setup?

Centralized pnpm catalogs in a JavaScript monorepo setup improve developer experience and dependency consistency by codifying tooling conventions, ensuring explicit runtime indicators, and maintaining standardized project templates across all workspace packages.

Do I need strict TypeScript configurations when scaffolding a new monorepo?

Strict TypeScript configurations are required when scaffolding a new monorepo with these opinionated tooling conventions, as the setup explicitly satisfies requirements for strict setups, consistent linting, and standardized project templates to reduce future configuration errors.