cursor-kit-cli 1.2.0-beta → 1.2.0-beta.2

package/templates/rules/testing.mdc

@@ -1,54 +0,0 @@
----
-description: Testing standards and patterns
-globs: ["**/*.test.ts", "**/*.test.tsx", "**/*.spec.ts", "**/*.spec.tsx"]
-alwaysApply: false
----
-
-# Testing Guidelines
-
-## Test Structure
-- Follow AAA pattern: Arrange, Act, Assert
-- One assertion per test when practical
-- Use descriptive test names that explain the expected behavior
-- Group related tests with `describe` blocks
-
-## Naming Convention
-```typescript
-describe('ComponentName', () => {
-  describe('methodName', () => {
-    it('should [expected behavior] when [condition]', () => {
-      // test
-    });
-  });
-});
-```
-
-## What to Test
-- Public interfaces and APIs
-- Edge cases and boundary conditions
-- Error handling paths
-- User interactions (for UI)
-- Integration points
-
-## What NOT to Test
-- Implementation details
-- Third-party libraries
-- Simple getters/setters
-- Private methods directly
-
-## Mocking
-- Mock external dependencies (APIs, databases)
-- Use dependency injection for easier mocking
-- Prefer spies over stubs when possible
-- Reset mocks between tests
-
-## Test Quality
-- Tests should be independent (no shared state)
-- Tests should be deterministic (same result every time)
-- Tests should be fast
-- Tests should be readable (tests are documentation)
-
-## Coverage Goals
-- Aim for high coverage on critical business logic
-- Don't chase 100% coverage blindly
-- Focus on meaningful tests over line coverage

package/templates/rules/typescript.mdc

@@ -1,36 +0,0 @@
----
-description: TypeScript best practices and code style
-globs: ["**/*.ts", "**/*.tsx"]
-alwaysApply: false
----
-
-# TypeScript Guidelines
-
-## Type Safety
-- Prefer explicit types on public functions, props, and return values
-- Avoid `any` and implicit `any` - use `unknown` when type is truly unknown
-- Use strict TypeScript configuration
-- Leverage type inference for local variables
-
-## Code Style
-- Use guard clauses over nested conditionals
-- Keep functions small and focused (single responsibility)
-- Use descriptive variable and function names
-- Event handlers should use "handle" prefix (e.g., `handleClick`, `handleSubmit`)
-
-## Naming Conventions
-- `camelCase` for variables, functions, and methods
-- `PascalCase` for classes, interfaces, types, and React components
-- `UPPER_SNAKE_CASE` for constants
-- Prefix interfaces with `I` only when necessary to distinguish from classes
-
-## Organization
-- Group related code in logical modules
-- Keep imports organized (external, internal, relative)
-- Co-locate related files (component + styles + tests)
-
-## Avoid
-- Magic numbers and strings (use named constants)
-- Deep nesting (max 2-3 levels)
-- Premature optimization
-- Unnecessary comments that restate the obvious