{"owner":"latitude-dev","repo":"typescript","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1326,"categories":["mcp-config","marketplace","plugin-manifest","cursor-rule"],"hasMcp":true,"mcpConfig":{"mcpServers":{"typescript":{"command":"npx","args":["-y","@modelcontextprotocol/server-typescript"]}}},"found":[".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json",".cursorrules (typescript.mdc)"],"skills":{".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.claude-plugin/plugin.json)",".cursorrules (typescript.mdc)":"---\ndescription: \"TypeScript coding standards and best practices for modern web development\"\nglobs: **/*.ts, **/*.tsx, **/*.d.ts\nalwaysApply: false\n---\n# TypeScript Best Practices\n\n## Type System\n- Prefer interfaces over types for object definitions\n- Use type for unions, intersections, and mapped types\n- Avoid using `any`, prefer `unknown` for unknown types\n- Use strict TypeScript configuration\n- Leverage TypeScript's built-in utility types\n- Use generics for reusable type patterns\n\n## Naming Conventions\n- Use PascalCase for type names and interfaces\n- Use camelCase for variables and functions\n- Use UPPER_CASE for constants\n- Use descriptive names with auxiliary verbs (e.g., isLoading, hasError)\n- Prefix interfaces for React props with 'Props' (e.g., ButtonProps)\n\n## Code Organization\n- Keep type definitions close to where they're used\n- Export types and interfaces from dedicated type files when shared\n- Use barrel exports (index.ts) for organizing exports\n- Place shared types in a `types` directory\n- Co-locate component props with their components\n\n## Functions\n- Use explicit return types for public functions\n- Use arrow functions for callbacks and methods\n- Implement proper error handling with custom error types\n- Use function overloads for complex type scenarios\n- Prefer async/await over Promises\n\n## Best Practices\n- Enable strict mode in tsconfig.json\n- Use readonly for immutable properties\n- Leverage discriminated unions for type safety\n- Use type guards for runtime type checking\n- Implement proper null checking\n- Avoid type assertions unless necessary\n\n## Error Handling\n- Create custom error types for domain-specific errors\n- Use Result types for operations that can fail\n- Implement proper error boundaries\n- Use try-catch blocks with typed catch clauses\n- Handle Promise rejections properly\n\n## Patterns\n- Use the Builder pattern for complex object creation\n- Implement the Repository pattern for data access\n- Use the Factory pattern for object creation\n- Leverage dependency injection\n- Use the Module pattern for encapsulation\n"},"files":{".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.claude-plugin/plugin.json)",".cursorrules (typescript.mdc)":"---\ndescription: \"TypeScript coding standards and best practices for modern web development\"\nglobs: **/*.ts, **/*.tsx, **/*.d.ts\nalwaysApply: false\n---\n# TypeScript Best Practices\n\n## Type System\n- Prefer interfaces over types for object definitions\n- Use type for unions, intersections, and mapped types\n- Avoid using `any`, prefer `unknown` for unknown types\n- Use strict TypeScript configuration\n- Leverage TypeScript's built-in utility types\n- Use generics for reusable type patterns\n\n## Naming Conventions\n- Use PascalCase for type names and interfaces\n- Use camelCase for variables and functions\n- Use UPPER_CASE for constants\n- Use descriptive names with auxiliary verbs (e.g., isLoading, hasError)\n- Prefix interfaces for React props with 'Props' (e.g., ButtonProps)\n\n## Code Organization\n- Keep type definitions close to where they're used\n- Export types and interfaces from dedicated type files when shared\n- Use barrel exports (index.ts) for organizing exports\n- Place shared types in a `types` directory\n- Co-locate component props with their components\n\n## Functions\n- Use explicit return types for public functions\n- Use arrow functions for callbacks and methods\n- Implement proper error handling with custom error types\n- Use function overloads for complex type scenarios\n- Prefer async/await over Promises\n\n## Best Practices\n- Enable strict mode in tsconfig.json\n- Use readonly for immutable properties\n- Leverage discriminated unions for type safety\n- Use type guards for runtime type checking\n- Implement proper null checking\n- Avoid type assertions unless necessary\n\n## Error Handling\n- Create custom error types for domain-specific errors\n- Use Result types for operations that can fail\n- Implement proper error boundaries\n- Use try-catch blocks with typed catch clauses\n- Handle Promise rejections properly\n\n## Patterns\n- Use the Builder pattern for complex object creation\n- Implement the Repository pattern for data access\n- Use the Factory pattern for object creation\n- Leverage dependency injection\n- Use the Module pattern for encapsulation\n"},"items":[{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":202},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":188},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":181},{"name":".cursorrules","path":".cursorrules (typescript.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/typescript.mdc","title":"Awesome Cursorrules: typescript","category":"cursor-rule","format":"markdown","content":"---\ndescription: \"TypeScript coding standards and best practices for modern web development\"\nglobs: **/*.ts, **/*.tsx, **/*.d.ts\nalwaysApply: false\n---\n# TypeScript Best Practices\n\n## Type System\n- Prefer interfaces over types for object definitions\n- Use type for unions, intersections, and mapped types\n- Avoid using `any`, prefer `unknown` for unknown types\n- Use strict TypeScript configuration\n- Leverage TypeScript's built-in utility types\n- Use generics for reusable type patterns\n\n## Naming Conventions\n- Use PascalCase for type names and interfaces\n- Use camelCase for variables and functions\n- Use UPPER_CASE for constants\n- Use descriptive names with auxiliary verbs (e.g., isLoading, hasError)\n- Prefix interfaces for React props with 'Props' (e.g., ButtonProps)\n\n## Code Organization\n- Keep type definitions close to where they're used\n- Export types and interfaces from dedicated type files when shared\n- Use barrel exports (index.ts) for organizing exports\n- Place shared types in a `types` directory\n- Co-locate component props with their components\n\n## Functions\n- Use explicit return types for public functions\n- Use arrow functions for callbacks and methods\n- Implement proper error handling with custom error types\n- Use function overloads for complex type scenarios\n- Prefer async/await over Promises\n\n## Best Practices\n- Enable strict mode in tsconfig.json\n- Use readonly for immutable properties\n- Leverage discriminated unions for type safety\n- Use type guards for runtime type checking\n- Implement proper null checking\n- Avoid type assertions unless necessary\n\n## Error Handling\n- Create custom error types for domain-specific errors\n- Use Result types for operations that can fail\n- Implement proper error boundaries\n- Use try-catch blocks with typed catch clauses\n- Handle Promise rejections properly\n\n## Patterns\n- Use the Builder pattern for complex object creation\n- Implement the Repository pattern for data access\n- Use the Factory pattern for object creation\n- Leverage dependency injection\n- Use the Module pattern for encapsulation\n","tokens":426,"sizeBytes":2067}],"systemPromptSnippet":"<yakaai_skills repo=\"latitude-dev/typescript\">\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/latitude-dev/typescript/HEAD/.cursor/mcp.json)\n\n<!-- File: .cursorrules (typescript.mdc) (Tokens: ~426 | Category: cursor-rule) -->\n---\ndescription: \"TypeScript coding standards and best practices for modern web development\"\nglobs: **/*.ts, **/*.tsx, **/*.d.ts\nalwaysApply: false\n---\n# TypeScript Best Practices\n\n## Type System\n- Prefer interfaces over types for object definitions\n- Use type for unions, intersections, and mapped types\n- Avoid using `any`, prefer `unknown` for unknown types\n- Use strict TypeScript configuration\n- Leverage TypeScript's built-in utility types\n- Use generics for reusable type patterns\n\n## Naming Conventions\n- Use PascalCase for type names and interfaces\n- Use camelCase for variables and functions\n- Use UPPER_CASE for constants\n- Use descriptive names with auxiliary verbs (e.g., isLoading, hasError)\n- Prefix interfaces for React props with 'Props' (e.g., ButtonProps)\n\n## Code Organization\n- Keep type definitions close to where they're used\n- Export types and interfaces from dedicated type files when shared\n- Use barrel exports (index.ts) for organizing exports\n- Place shared types in a `types` directory\n- Co-locate component props with their components\n\n## Functions\n- Use explicit return types for public functions\n- Use arrow functions for callbacks and methods\n- Implement proper error handling with custom error types\n- Use function overloads for complex type scenarios\n- Prefer async/await over Promises\n\n## Best Practices\n- Enable strict mode in tsconfig.json\n- Use readonly for immutable properties\n- Leverage discriminated unions for type safety\n- Use type guards for runtime type checking\n- Implement proper null checking\n- Avoid type assertions unless necessary\n\n## Error Handling\n- Create custom error types for domain-specific errors\n- Use Result types for operations that can fail\n- Implement proper error boundaries\n- Use try-catch blocks with typed catch clauses\n- Handle Promise rejections properly\n\n## Patterns\n- Use the Builder pattern for complex object creation\n- Implement the Repository pattern for data access\n- Use the Factory pattern for object creation\n- Leverage dependency injection\n- Use the Module pattern for encapsulation\n</yakaai_skills>"}