refactor(skills): unify cursor rules and claude skills

.claude/skills/development-workflow/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: development-workflow
-description: Build, development, and code quality commands for StackOne SDK
+description: Build commands, testing, linting, git workflow, commit conventions, and file naming standards. (project)
+globs: ""
+alwaysApply: true
 ---
 
 # Development Workflow
@@ -107,7 +109,29 @@ feat(parser): add support for custom parameter transformers
 4. Verify with `git status` before committing
 
 ### TypeScript Issues
-Use the TypeScript exhaustiveness pattern (`satisfies never`) when branching on unions. See `openapi-architecture` skill for examples.
+Use the TypeScript exhaustiveness pattern (`satisfies never`) when branching on unions. See `typescript-patterns` skill for examples.
+
+## Pull Request Guidelines
+
+### PR Title Format
+Use the same format as commit messages: `type(scope): description`
+
+Types: `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `ci`, `perf`
+
+Examples:
+- `feat(tools): add support for custom OpenAPI specs`
+- `fix(parser): handle empty response bodies`
+- `refactor(skills): unify cursor rules and claude skills`
+
+### PR Body
+Include:
+- **Summary**: 1-3 bullet points describing changes
+- **Test plan**: How to verify the changes work
+- Reference related issues with `Closes #123` or `Fixes #123`
+
+## File Naming Conventions
+
+- Use `.yaml` extension instead of `.yml` for all YAML files (e.g., `lefthook.yaml`, GitHub Actions workflows)
 
 ## Working with Tools
 

.claude/skills/file-operations/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: file-operations
-description: HTTP request standards for StackOne SDK
+description: Use when making HTTP requests. Covers native fetch API patterns and error handling. (project)
+globs: "*.ts"
+alwaysApply: false
 ---
 
 # HTTP Request Standards

.claude/skills/orama-integration/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: orama-integration
-description: Orama API integration reference for StackOne
+description: Use when integrating with Orama. Links to official docs for search, indexing, answer engine. (project)
+globs: ""
+alwaysApply: false
 ---
 
 # Orama Integration

.claude/skills/typescript-patterns/SKILL.md

@@ -1,11 +1,13 @@
 ---
 name: typescript-patterns
-description: TypeScript patterns and best practices for StackOne SDK
+description: Use when writing or reviewing TypeScript code. Covers type safety, exhaustiveness checks, avoiding any/non-null assertions, clean code practices. (project)
+globs: "*.ts"
+alwaysApply: false
 ---
 
 # TypeScript Patterns and Best Practices
 
-This skill provides guidance on TypeScript patterns and best practices for writing clean, type-safe code in the StackOne SDK.
+Guidelines for writing clean, type-safe TypeScript code in this repository.
 
 ## Exhaustiveness Checking with `satisfies never`
 
@@ -207,12 +209,20 @@ function removeProperty(obj: Record<string, JSONSchema7Definition>): void {
 }
 ```
 
-## Recommendations
+## Remove Unused Code
 
-1. Use `satisfies never` for all union type switches
-2. Prefer `unknown` over `any` and use type guards
-3. Use optional chaining (`?.`) and nullish coalescing (`??`)
+After refactoring, always remove unused code:
+- Delete unused variables, parameters, functions, classes, imports
+- Don't comment out old code - delete it (git history preserves it)
+- Remove unreachable code paths
+
+## Quick Reference
+
+1. Use `satisfies never` for union type switches
+2. Prefer `unknown` over `any` with type guards
+3. Use `?.` and `??` instead of non-null assertions
 4. Always specify return types
-5. Use destructuring for immutable property removal
-6. Write functions as simple exports, not class static methods
-7. Create new variables instead of reassigning parameters
+5. Use destructuring for property removal
+6. Use simple exports instead of static-only classes
+7. Don't reassign parameters - create new variables
+8. Remove unused code after refactoring

.claude/skills/typescript-testing/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: typescript-testing
-description: Vitest test runner and MSW-based testing patterns for StackOne SDK
+description: Use when writing or running tests. Covers Vitest commands, MSW HTTP mocking, fs-fixture for file system tests. (project)
+globs: "*.spec.ts"
+alwaysApply: false
 ---
 
 # TypeScript Testing with Vitest and MSW

.cursor/rules/development-workflow.mdc

@@ -0,0 +1 @@
+../../.claude/skills/development-workflow/SKILL.md