cp-toolkit 2.2.13 → 2.2.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cp-toolkit",
-  "version": "2.2.13",
+  "version": "2.2.14",
   "description": "Copilot Toolkit - AI Agent framework for GitHub Copilot, Claude, Gemini CLI, and other AI assistants",
   "keywords": [
     "ai-agents",

package/src/commands/init.js

@@ -83,13 +83,12 @@ export async function initCommand(directory, options) {
     await fs.ensureDir(agentsTargetDir);
     await fs.copy(agentsSourceDir, agentsTargetDir, { overwrite: true });
 
-    // 2. Setup .github/instructions/ (from skills that have instruction content)
+    // 2. Setup .github/instructions/
     spinner.text = 'Copying instructions...';
+    const instructionsSourceDir = path.join(templatesDir, 'instructions');
     const instructionsTargetDir = path.join(targetDir, '.github', 'instructions');
     await fs.ensureDir(instructionsTargetDir);
-
-    // Create standard instruction files
-    await createInstructionFiles(instructionsTargetDir);
+    await fs.copy(instructionsSourceDir, instructionsTargetDir, { overwrite: true });
 
     // 4. Setup .github/skills/ (essential skills referenced by agents)
     spinner.text = 'Copying essential skills...';
@@ -263,432 +262,4 @@ export async function initCommand(directory, options) {
   }
 }
 
-async function createInstructionFiles(instructionsDir) {
-  const instructions = {
-    'typescript-development.instructions.md': `---
-name: typescript-development
-description: Strict guidelines for TypeScript development including type safety, modules, and error handling.
-version: 1.0
-applyTo: "**/*.ts,**/*.tsx,**/*.mts,**/*.cts"
----
-
-# TypeScript Development Guidelines
-
-## Strict Mode & Type Safety
-- Enable \`strict: true\` in tsconfig.json
-- No \`any\` types - use \`unknown\` and narrow with type guards
-- Explicit return types for public functions
-- Use \`strictNullChecks\` and \`noImplicitAny\`
-
-## Code Patterns
-- Prefer \`interface\` over \`type\` for object shapes
-- Use \`as const\` for literal types and enums
-- Leverage discriminated unions for state management
-- Use mapped types for transformations
-- Prefer \`readonly\` for immutable data
-
-## Imports & Modules
-- Use type-only imports: \`import type { X } from 'y'\`
-- Barrel exports for public APIs only
-- Avoid relative imports with \`../\` - use absolute paths
-
-## Error Handling
-- Use custom error classes extending \`Error\`
-- Prefer Result types over throwing exceptions
-- Use try/catch only for external operations
-`,
-
-    'javascript-development.instructions.md': `---
-name: javascript-development
-description: Best practices for modern JavaScript development including ES6+ features and functional patterns.
-version: 1.0
-applyTo: "**/*.js,**/*.mjs,**/*.cjs"
----
-
-# JavaScript Development Guidelines
-
-## ES6+ Features
-- Use \`const\` and \`let\` instead of \`var\`
-- Arrow functions for callbacks and anonymous functions
-- Template literals over string concatenation
-- Destructuring for objects and arrays
-- Spread/rest operators for manipulation
-
-## Code Patterns
-- Prefer functional programming approaches
-- Use async/await over Promises for readability
-- Implement proper error handling with try/catch
-- Use Map/Set for collections when appropriate
-- Leverage object destructuring for configuration
-
-## Best Practices
-- Strict mode: \`'use strict'\` at file/module level
-- Consistent naming: camelCase for variables/functions
-- Meaningful variable names over abbreviations
-- Single responsibility principle for functions
-
-## Performance
-- Avoid global variables
-- Use efficient algorithms and data structures
-- Minimize DOM manipulation
-- Cache expensive operations
-`,
-
-    'react-development.instructions.md': `---
-name: react-development
-description: Component patterns, state management, and accessibility standards for React development.
-version: 1.0
-applyTo: "**/*.jsx,**/*.tsx,**/*react*"
----
-
-# React Development Guidelines
-
-## Component Patterns
-- Functional components with hooks over class components
-- Custom hooks for reusable logic
-- Compound components for complex UI patterns
-- Container/Presentational separation when appropriate
-
-## State Management
-- useState for local component state
-- useReducer for complex state logic
-- Context API for theme/configuration
-- External libraries (Zustand, Redux) for app-wide state
-
-## Performance
-- React.memo for expensive components
-- useMemo for expensive calculations
-- useCallback for event handlers
-- Lazy loading with React.lazy and Suspense
-- Code splitting for large applications
-
-## Hooks Best Practices
-- Custom hooks for side effects
-- useEffect cleanup functions
-- Dependency arrays correctly specified
-- Avoid conditional hook calls
-
-## Accessibility
-- Semantic HTML elements
-- ARIA attributes when needed
-- Keyboard navigation support
-- Screen reader compatibility
-`,
-
-    'nextjs-development.instructions.md': `---
-name: nextjs-development
-description: Guidelines for Next.js development including App Router, Server Components, and SEO optimization.
-version: 1.0
-applyTo: "**/app/**,**/components/**,**/lib/**,**/utils/**"
----
-
-# Next.js Development Guidelines
-
-## App Router (App Directory)
-- Server Components by default
-- Client Components with 'use client' directive
-- Server Actions for form handling
-- Route Groups for organization: (auth), (dashboard)
-
-## File Structure
-- \`app/\` for routing and layouts
-- \`components/\` for reusable UI
-- \`lib/\` for utilities and configurations
-- \`utils/\` for helper functions
-- \`types/\` for TypeScript definitions
-
-## Data Fetching
-- Server Components for initial data
-- Client Components for interactive data
-- SWR or React Query for client-side fetching
-- Server Actions for mutations
-
-## Performance
-- Image optimization with next/image
-- Font optimization with next/font
-- Code splitting automatic
-- Static generation when possible
-- ISR for dynamic content
-
-## SEO & Metadata
-- Metadata API for dynamic meta tags
-- Static metadata exports
-- Open Graph and Twitter cards
-- Structured data with JSON-LD
-`,
-
-    'python-development.instructions.md': `---
-name: python-development
-description: Best practices for Python development including type hints, async/await, and testing.
-version: 1.0
-applyTo: "**/*.py"
----
-
-# Python Development Guidelines
-
-## Type Hints & Annotations
-- Use type hints for all function signatures
-- Use \`from __future__ import annotations\` for forward refs
-- Prefer \`typing.Optional\` over \`X | None\` for Python 3.9 compat
-- Generic types with \`TypeVar\` when needed
-
-## Code Patterns
-- Use dataclasses or Pydantic for data structures
-- Async/await for I/O bound operations
-- Context managers (\`with\` statements) for resource management
-- List/dict comprehensions for transformations
-- Generator functions for large datasets
-
-## Best Practices
-- Follow PEP 8 style guidelines
-- Use Black for code formatting
-- Google/NumPy style docstrings
-- Meaningful variable names
-- Single responsibility principle
-
-## Error Handling
-- Custom exception classes
-- Specific exception types over generic Exception
-- Proper exception chaining
-- Logging with appropriate levels
-
-## Testing
-- pytest framework preferred
-- Unit tests for functions/classes
-- Integration tests for workflows
-- Mock external dependencies
-`,
-
-    'security-development.instructions.md': `---
-name: security-development
-description: Comprehensive security guidelines including auth, data protection, and web security.
-version: 1.0
-applyTo: "**/auth/**,**/security/**,**/*auth*,**/*token*,**/*session*,**/middleware/**"
----
-
-# Security Development Guidelines
-
-## Authentication & Authorization
-- JWT with short expiry + refresh tokens
-- HttpOnly cookies for web sessions
-- Rate limiting on authentication endpoints
-- RBAC or ABAC patterns implemented
-- Server-side permission checks always
-
-## Data Protection
-- Input sanitization and validation
-- Output encoding by context (HTML, SQL, JSON)
-- Never log sensitive data (passwords, tokens, PII)
-- Encryption at rest and in transit
-- Secure password hashing (bcrypt, Argon2)
-
-## Web Security
-- CSRF tokens for state-changing operations
-- Content Security Policy (CSP) headers
-- HTTPS enforcement (HSTS)
-- Secure headers (X-Frame-Options, etc.)
-- XSS prevention with proper escaping
-
-## API Security
-- API versioning for breaking changes
-- Request/response validation schemas
-- CORS configuration for allowed origins
-- API rate limiting and throttling
-- Proper error messages (no sensitive info)
-
-## OWASP Top 10
-- Injection prevention (parameterized queries)
-- Broken authentication handling
-- Sensitive data exposure protection
-- XML external entity prevention
-- Access control enforcement
-`,
-
-    'database-development.instructions.md': `---
-name: database-development
-description: Standards for schema design, query optimization, and database migrations.
-version: 1.0
-applyTo: "**/prisma/**,**/*.sql,**/migrations/**,**/schema.*,**/db/**,**/models/**"
----
-
-# Database Development Guidelines
-
-## Schema Design
-- UUID or ULID for primary keys (not auto-increment)
-- Timestamps: createdAt, updatedAt on all tables
-- Soft delete with deletedAt when needed
-- Proper foreign key relationships
-- Normalized schemas with good indexing
-
-## Query Optimization
-- Use parameterized queries only (never string concat)
-- Select only needed fields (avoid SELECT *)
-- Use cursor-based pagination for large datasets
-- Proper indexing on frequently queried fields
-- Query execution plan analysis
-
-## ORM Best Practices
-- Use transactions for multi-table operations
-- N+1 query problem avoidance
-- Proper eager/lazy loading
-- Migration scripts for schema changes
-- Database constraints and validations
-
-## Migration Safety
-- One migration per feature/change
-- Never modify already-applied migrations
-- Test migrations on production-like data
-- Rollback scripts for emergency recovery
-- Version control for migration files
-
-## Performance
-- Connection pooling configuration
-- Query result caching strategies
-- Database indexing strategy
-- Read/write splitting when appropriate
-- Monitoring and alerting setup
-`,
-
-    'testing-development.instructions.md': `---
-name: testing-development
-description: Guidelines for test structure, frameworks, and code coverage best practices.
-version: 1.0
-applyTo: "**/*.test.*,**/*.spec.*,**/tests/**,**/__tests__/**"
----
-
-# Testing Development Guidelines
-
-## Test Structure
-- Unit tests for individual functions/classes
-- Integration tests for component interactions
-- End-to-end tests for user workflows
-- Performance tests for critical paths
-- Accessibility tests for UI components
-
-## Testing Frameworks
-- Jest for JavaScript/TypeScript
-- pytest for Python
-- RSpec for Ruby
-- JUnit for Java
-- Appropriate framework per language
-
-## Test Patterns
-- Arrange-Act-Assert (AAA) pattern
-- Descriptive test names (not test1, test2)
-- One assertion per test when possible
-- Mock external dependencies
-- Test edge cases and error conditions
-
-## Code Coverage
-- Aim for 80%+ coverage on critical code
-- Focus on business logic over getters/setters
-- Integration tests for coverage gaps
-- Coverage reports in CI/CD pipeline
-
-## Best Practices
-- Tests run independently (no shared state)
-- Fast execution for developer experience
-- CI/CD integration with quality gates
-- Test data management and cleanup
-- Documentation of test scenarios
-`,
-
-    'api-development.instructions.md': `---
-name: api-development
-description: RESTful API design standards including versioning, error handling, and documentation.
-version: 1.0
-applyTo: "**/api/**,**/routes/**,**/controllers/**,**/services/**,**/*api*,**/*endpoint*"
----
-
-# API Development Guidelines
-
-## RESTful Design
-- Proper HTTP methods (GET, POST, PUT, DELETE)
-- Resource-based URLs (/users, /users/{id})
-- Status codes: 200, 201, 400, 401, 403, 404, 500
-- Content-Type and Accept headers
-- Idempotent operations where appropriate
-
-## API Versioning
-- URL versioning: /api/v1/users
-- Header versioning when needed
-- Backward compatibility maintenance
-- Deprecation notices for breaking changes
-- Version documentation
-
-## Request/Response
-- JSON as primary format
-- Consistent response structure
-- Pagination for list endpoints
-- Filtering and sorting parameters
-- Rate limiting headers
-
-## Error Handling
-- Consistent error response format
-- Appropriate HTTP status codes
-- User-friendly error messages
-- Error logging and monitoring
-- Graceful degradation
-
-## Documentation
-- OpenAPI/Swagger specifications
-- Interactive API documentation
-- Authentication examples
-- Rate limiting information
-- Changelog for API versions
-`,
-
-    'github-actions.instructions.md': `---
-name: github-actions
-description: Standards for GitHub Actions workflows including security, performance, and best practices.
-version: 1.0
-applyTo: ".github/workflows/**/*.yml,.github/workflows/**/*.yaml"
----
-
-# GitHub Actions Development Guidelines
-
-## Workflow Structure
-- Descriptive workflow names and jobs
-- Matrix builds for multiple environments
-- Proper job dependencies with needs
-- Conditional execution with if statements
-- Timeout settings for long-running jobs
-
-## Security
-- Use trusted actions from GitHub Marketplace
-- Pin action versions to specific SHAs
-- Use secrets for sensitive data
-- CodeQL for security scanning
-- Dependency review for PRs
-
-## Best Practices
-- Cache dependencies for faster builds
-- Use self-hosted runners when appropriate
-- Proper artifact management
-- Notification configuration
-- Workflow reusability with composite actions
-
-## CI/CD Pipeline
-- Build → Test → Deploy stages
-- Parallel job execution
-- Failure handling and notifications
-- Rollback capabilities
-- Environment-specific configurations
-
-## Performance
-- Efficient caching strategies
-- Minimal artifact sizes
-- Parallel job execution
-- Resource optimization
-- Build time monitoring
-`
-  };
-
-  for (const [filename, content] of Object.entries(instructions)) {
-    await fs.writeFile(path.join(instructionsDir, filename), content);
-  }
-}
-
 export default initCommand;
-
-

package/templates/instructions/api-development.instructions.md

@@ -0,0 +1,43 @@
+---
+name: api-development
+description: RESTful API design standards including versioning, error handling, and documentation.
+version: 1.0
+applyTo: "**/api/**,**/routes/**,**/controllers/**,**/services/**,**/*api*,**/*endpoint*"
+---
+
+# API Development Guidelines
+
+## RESTful Design
+- Proper HTTP methods (GET, POST, PUT, DELETE)
+- Resource-based URLs (/users, /users/{id})
+- Status codes: 200, 201, 400, 401, 403, 404, 500
+- Content-Type and Accept headers
+- Idempotent operations where appropriate
+
+## API Versioning
+- URL versioning: /api/v1/users
+- Header versioning when needed
+- Backward compatibility maintenance
+- Deprecation notices for breaking changes
+- Version documentation
+
+## Request/Response
+- JSON as primary format
+- Consistent response structure
+- Pagination for list endpoints
+- Filtering and sorting parameters
+- Rate limiting headers
+
+## Error Handling
+- Consistent error response format
+- Appropriate HTTP status codes
+- User-friendly error messages
+- Error logging and monitoring
+- Graceful degradation
+
+## Documentation
+- OpenAPI/Swagger specifications
+- Interactive API documentation
+- Authentication examples
+- Rate limiting information
+- Changelog for API versions

package/templates/instructions/database-development.instructions.md

@@ -0,0 +1,43 @@
+---
+name: database-development
+description: Standards for schema design, query optimization, and database migrations.
+version: 1.0
+applyTo: "**/prisma/**,**/*.sql,**/migrations/**,**/schema.*,**/db/**,**/models/**"
+---
+
+# Database Development Guidelines
+
+## Schema Design
+- UUID or ULID for primary keys (not auto-increment)
+- Timestamps: createdAt, updatedAt on all tables
+- Soft delete with deletedAt when needed
+- Proper foreign key relationships
+- Normalized schemas with good indexing
+
+## Query Optimization
+- Use parameterized queries only (never string concat)
+- Select only needed fields (avoid SELECT *)
+- Use cursor-based pagination for large datasets
+- Proper indexing on frequently queried fields
+- Query execution plan analysis
+
+## ORM Best Practices
+- Use transactions for multi-table operations
+- N+1 query problem avoidance
+- Proper eager/lazy loading
+- Migration scripts for schema changes
+- Database constraints and validations
+
+## Migration Safety
+- One migration per feature/change
+- Never modify already-applied migrations
+- Test migrations on production-like data
+- Rollback scripts for emergency recovery
+- Version control for migration files
+
+## Performance
+- Connection pooling configuration
+- Query result caching strategies
+- Database indexing strategy
+- Read/write splitting when appropriate
+- Monitoring and alerting setup

package/templates/instructions/github-actions.instructions.md

@@ -0,0 +1,43 @@
+---
+name: github-actions
+description: Standards for GitHub Actions workflows including security, performance, and best practices.
+version: 1.0
+applyTo: ".github/workflows/**/*.yml,.github/workflows/**/*.yaml"
+---
+
+# GitHub Actions Development Guidelines
+
+## Workflow Structure
+- Descriptive workflow names and jobs
+- Matrix builds for multiple environments
+- Proper job dependencies with needs
+- Conditional execution with if statements
+- Timeout settings for long-running jobs
+
+## Security
+- Use trusted actions from GitHub Marketplace
+- Pin action versions to specific SHAs
+- Use secrets for sensitive data
+- CodeQL for security scanning
+- Dependency review for PRs
+
+## Best Practices
+- Cache dependencies for faster builds
+- Use self-hosted runners when appropriate
+- Proper artifact management
+- Notification configuration
+- Workflow reusability with composite actions
+
+## CI/CD Pipeline
+- Build → Test → Deploy stages
+- Parallel job execution
+- Failure handling and notifications
+- Rollback capabilities
+- Environment-specific configurations
+
+## Performance
+- Efficient caching strategies
+- Minimal artifact sizes
+- Parallel job execution
+- Resource optimization
+- Build time monitoring

package/templates/instructions/javascript-development.instructions.md

@@ -0,0 +1,34 @@
+---
+name: javascript-development
+description: Best practices for modern JavaScript development including ES6+ features and functional patterns.
+version: 1.0
+applyTo: "**/*.js,**/*.mjs,**/*.cjs"
+---
+
+# JavaScript Development Guidelines
+
+## ES6+ Features
+- Use `const` and `let` instead of `var`
+- Arrow functions for callbacks and anonymous functions
+- Template literals over string concatenation
+- Destructuring for objects and arrays
+- Spread/rest operators for manipulation
+
+## Code Patterns
+- Prefer functional programming approaches
+- Use async/await over Promises for readability
+- Implement proper error handling with try/catch
+- Use Map/Set for collections when appropriate
+- Leverage object destructuring for configuration
+
+## Best Practices
+- Strict mode: `'use strict'` at file/module level
+- Consistent naming: camelCase for variables/functions
+- Meaningful variable names over abbreviations
+- Single responsibility principle for functions
+
+## Performance
+- Avoid global variables
+- Use efficient algorithms and data structures
+- Minimize DOM manipulation
+- Cache expensive operations

package/templates/instructions/nextjs-development.instructions.md

@@ -0,0 +1,40 @@
+---
+name: nextjs-development
+description: Guidelines for Next.js development including App Router, Server Components, and SEO optimization.
+version: 1.0
+applyTo: "**/app/**,**/components/**,**/lib/**,**/utils/**"
+---
+
+# Next.js Development Guidelines
+
+## App Router (App Directory)
+- Server Components by default
+- Client Components with 'use client' directive
+- Server Actions for form handling
+- Route Groups for organization: (auth), (dashboard)
+
+## File Structure
+- `app/` for routing and layouts
+- `components/` for reusable UI
+- `lib/` for utilities and configurations
+- `utils/` for helper functions
+- `types/` for TypeScript definitions
+
+## Data Fetching
+- Server Components for initial data
+- Client Components for interactive data
+- SWR or React Query for client-side fetching
+- Server Actions for mutations
+
+## Performance
+- Image optimization with next/image
+- Font optimization with next/font
+- Code splitting automatic
+- Static generation when possible
+- ISR for dynamic content
+
+## SEO & Metadata
+- Metadata API for dynamic meta tags
+- Static metadata exports
+- Open Graph and Twitter cards
+- Structured data with JSON-LD

package/templates/instructions/python-development.instructions.md

@@ -0,0 +1,40 @@
+---
+name: python-development
+description: Best practices for Python development including type hints, async/await, and testing.
+version: 1.0
+applyTo: "**/*.py"
+---
+
+# Python Development Guidelines
+
+## Type Hints & Annotations
+- Use type hints for all function signatures
+- Use `from __future__ import annotations` for forward refs
+- Prefer `typing.Optional` over `X | None` for Python 3.9 compat
+- Generic types with `TypeVar` when needed
+
+## Code Patterns
+- Use dataclasses or Pydantic for data structures
+- Async/await for I/O bound operations
+- Context managers (`with` statements) for resource management
+- List/dict comprehensions for transformations
+- Generator functions for large datasets
+
+## Best Practices
+- Follow PEP 8 style guidelines
+- Use Black for code formatting
+- Google/NumPy style docstrings
+- Meaningful variable names
+- Single responsibility principle
+
+## Error Handling
+- Custom exception classes
+- Specific exception types over generic Exception
+- Proper exception chaining
+- Logging with appropriate levels
+
+## Testing
+- pytest framework preferred
+- Unit tests for functions/classes
+- Integration tests for workflows
+- Mock external dependencies

package/templates/instructions/react-development.instructions.md

@@ -0,0 +1,39 @@
+---
+name: react-development
+description: Component patterns, state management, and accessibility standards for React development.
+version: 1.0
+applyTo: "**/*.jsx,**/*.tsx,**/*react*"
+---
+
+# React Development Guidelines
+
+## Component Patterns
+- Functional components with hooks over class components
+- Custom hooks for reusable logic
+- Compound components for complex UI patterns
+- Container/Presentational separation when appropriate
+
+## State Management
+- useState for local component state
+- useReducer for complex state logic
+- Context API for theme/configuration
+- External libraries (Zustand, Redux) for app-wide state
+
+## Performance
+- React.memo for expensive components
+- useMemo for expensive calculations
+- useCallback for event handlers
+- Lazy loading with React.lazy and Suspense
+- Code splitting for large applications
+
+## Hooks Best Practices
+- Custom hooks for side effects
+- useEffect cleanup functions
+- Dependency arrays correctly specified
+- Avoid conditional hook calls
+
+## Accessibility
+- Semantic HTML elements
+- ARIA attributes when needed
+- Keyboard navigation support
+- Screen reader compatibility

package/templates/instructions/security-development.instructions.md

@@ -0,0 +1,43 @@
+---
+name: security-development
+description: Comprehensive security guidelines including auth, data protection, and web security.
+version: 1.0
+applyTo: "**/auth/**,**/security/**,**/*auth*,**/*token*,**/*session*,**/middleware/**"
+---
+
+# Security Development Guidelines
+
+## Authentication & Authorization
+- JWT with short expiry + refresh tokens
+- HttpOnly cookies for web sessions
+- Rate limiting on authentication endpoints
+- RBAC or ABAC patterns implemented
+- Server-side permission checks always
+
+## Data Protection
+- Input sanitization and validation
+- Output encoding by context (HTML, SQL, JSON)
+- Never log sensitive data (passwords, tokens, PII)
+- Encryption at rest and in transit
+- Secure password hashing (bcrypt, Argon2)
+
+## Web Security
+- CSRF tokens for state-changing operations
+- Content Security Policy (CSP) headers
+- HTTPS enforcement (HSTS)
+- Secure headers (X-Frame-Options, etc.)
+- XSS prevention with proper escaping
+
+## API Security
+- API versioning for breaking changes
+- Request/response validation schemas
+- CORS configuration for allowed origins
+- API rate limiting and throttling
+- Proper error messages (no sensitive info)
+
+## OWASP Top 10
+- Injection prevention (parameterized queries)
+- Broken authentication handling
+- Sensitive data exposure protection
+- XML external entity prevention
+- Access control enforcement

package/templates/instructions/testing-development.instructions.md

@@ -0,0 +1,42 @@
+---
+name: testing-development
+description: Guidelines for test structure, frameworks, and code coverage best practices.
+version: 1.0
+applyTo: "**/*.test.*,**/*.spec.*,**/tests/**,**/__tests__/**"
+---
+
+# Testing Development Guidelines
+
+## Test Structure
+- Unit tests for individual functions/classes
+- Integration tests for component interactions
+- End-to-end tests for user workflows
+- Performance tests for critical paths
+- Accessibility tests for UI components
+
+## Testing Frameworks
+- Jest for JavaScript/TypeScript
+- pytest for Python
+- RSpec for Ruby
+- JUnit for Java
+- Appropriate framework per language
+
+## Test Patterns
+- Arrange-Act-Assert (AAA) pattern
+- Descriptive test names (not test1, test2)
+- One assertion per test when possible
+- Mock external dependencies
+- Test edge cases and error conditions
+
+## Code Coverage
+- Aim for 80%+ coverage on critical code
+- Focus on business logic over getters/setters
+- Integration tests for coverage gaps
+- Coverage reports in CI/CD pipeline
+
+## Best Practices
+- Tests run independently (no shared state)
+- Fast execution for developer experience
+- CI/CD integration with quality gates
+- Test data management and cleanup
+- Documentation of test scenarios

package/templates/instructions/typescript-development.instructions.md

@@ -0,0 +1,31 @@
+---
+name: typescript-development
+description: Strict guidelines for TypeScript development including type safety, modules, and error handling.
+version: 1.0
+applyTo: "**/*.ts,**/*.tsx,**/*.mts,**/*.cts"
+---
+
+# TypeScript Development Guidelines
+
+## Strict Mode & Type Safety
+- Enable `strict: true` in tsconfig.json
+- No `any` types - use `unknown` and narrow with type guards
+- Explicit return types for public functions
+- Use `strictNullChecks` and `noImplicitAny`
+
+## Code Patterns
+- Prefer `interface` over `type` for object shapes
+- Use `as const` for literal types and enums
+- Leverage discriminated unions for state management
+- Use mapped types for transformations
+- Prefer `readonly` for immutable data
+
+## Imports & Modules
+- Use type-only imports: `import type { X } from 'y'`
+- Barrel exports for public APIs only
+- Avoid relative imports with `../` - use absolute paths
+
+## Error Handling
+- Use custom error classes extending `Error`
+- Prefer Result types over throwing exceptions
+- Use try/catch only for external operations