cursor-sim API contract reference. Use when implementing services that consume cursor-sim data (analytics-core, viz-spa), ensuring API alignment, or verifying response formats. Source of truth for data models and endpoint contracts. (project)
jb-612/cursor-analytics-platform
SkillsMP has collected 14 skills from jb-612/cursor-analytics-platform. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 14
- GitHub stars
- 1
- GitHub forks
- 0
Skills in this repository
Showing 14 of 14 collected skills.
Cursor Business API implementation patterns. Use when implementing API endpoints, writing HTTP handlers, handling authentication, pagination, error responses, or CSV exports. Covers response formats for AI Code Tracking, Analytics, and Admin APIs. (project)
Identifies required updates to related files after primary changes. Use after completing any code changes to detect documentation drift, missing test updates, and cross-file dependencies. Triggers on refactoring, model changes, or interface modifications.…
Go coding standards for cursor-sim service. Use when writing Go code, implementing HTTP handlers, creating structs, handling errors, or writing Go tests. Covers naming conventions, error handling, concurrency, and testing patterns. (project)
Guide for selecting the right Claude model (Haiku, Sonnet, Opus) for different tasks. Use when starting a new task, planning implementation, or optimizing costs. Helps choose between fast/cheap Haiku and powerful Sonnet/Opus. (project)
React and Vite best practices for cursor-viz-spa dashboard. Use when implementing React components, Apollo Client queries, Tailwind styling, or Vite configuration. Covers hooks, state management, and data visualization patterns. (project)
Post-task completion checklist for Spec-Driven Development. Use after completing any implementation task to ensure proper commit hygiene. Triggers on "task complete", "step done", "ready to commit", or moving to next task. (project)
Create or revise technical design documents. Use when planning architecture, making component decisions, designing interfaces, or documenting ADRs (Architecture Decision Records). Produces design.md files with rationale and alternatives. (project)
Core SDD (Spec-Driven Development) process. Use when starting development work, planning features, or asking about workflow. Covers the fundamental sequence of Spec, Test, Code, Refactor, Commit. (project)
TDD (Test-Driven Development) workflow for implementation. Use when writing code, implementing features, or fixing bugs. Covers RED-GREEN-REFACTOR cycle, test patterns, and coverage requirements. (project)
Determines if SPEC.md needs updating after implementation changes. Triggers automatically when completing tasks that modify endpoints, models, services, or complete phases. Use when finishing any implementation task. (project)
Create or revise task breakdowns for feature implementation. Use when decomposing features into work units, planning sprints, or tracking implementation progress. Produces task.md files with progress tracker and TDD approach. (project)
Create or revise user stories following EARS format. Use when writing PRDs, feature narratives, acceptance criteria, or product requirements. Produces user-story.md files with As-a/I-want/So-that and Given-When-Then criteria. (project)
TypeScript and GraphQL best practices for cursor-analytics-core. Use when implementing GraphQL schemas, resolvers, TypeScript services, or data fetching. Covers type safety, error handling, and Apollo Server patterns. (project)