This repository contains standardized cursor rules for Tekdi projects, organized by technology stack and framework.
Skill Claude CodeCodex
Turns business requirement (BRD, feature ask, one-liner, or attached requirement doc) into implementation-ready task list — generic across stacks until tailored to specific repo. Grounds itself in whatever context repo actually provides (project wiki, CLAUDE.md/ AGENTS.md, README, or live repo scan if none exists)…
Skill Claude CodeCodex
Use when someone asks to understand a software project — "explain the project", "how does X work", "what is ", "walk me through the architecture / db design / domain / data model", "onboard me", "give me an overview", or invokes /explain-project. For engineers, QA, and client-side technical readers. Wiki-aware, falls…
Skill Claude CodeCodex
End-to-end feature development skill — generic across stacks until tailored to a specific repo. Trigger this skill whenever the user asks to "add a feature", "add a route/endpoint/API", "add a column/table", "wire this into the UI", "add a config option", "change the generation/processing pipeline", "add a page", or…
Skill Claude CodeCodex
Generates a complete AI-native service wiki from repository analysis for human onboarding and AI-agent long-term memory. Use when the user asks to generate a wiki, service documentation, repository documentation, ai-context.md, repository-map.md, onboarding docs, or LLM-native documentation for a codebase. Trigger on…
Skill Claude CodeCodex
Performs a comprehensive, evidence-based reliability assessment of a service repository against a standard SRE Reliability Matrix. Use when the user asks to run a reliability audit, reliability matrix assessment, reliability scorecard, production readiness review, SRE maturity assessment, or generate…
Skill Claude CodeCodex
Use when someone asks to review a software project's tech design — "review tech design", "review tech architect", or invokes /tech-design-review.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: