NITRR-Official

Build React components in Next.js using CampusOS patterns. Use when implementing UI components, working with the App Router, styling with Tailwind CSS v4, or managing forms with react-hook-form and Zod.

Comprehensive frontend development hub — UI/UX design, React/Next.js patterns, Tailwind CSS v4, shadcn/ui components, Three.js 3D graphics, creative web experiences, data visualization, diagramming, Figma integration, accessibility, game development, scroll animations, and design systems. Use for ANY frontend task: building components, designing interfaces, styling, theming, animations, charts, responsive layouts, mobile design, or implementing design patterns.

Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.

Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.

Generate commit titles and descriptions from uncommitted changes. Use when the user asks to generate a commit message, wants help writing a commit, or says 'commit', 'commit message', 'what should I commit', or similar.

Generate PR titles and descriptions from commit history. Use when the user asks to generate a PR description, wants help writing a pull request, provides commit titles/messages, or says 'PR', 'pull request', 'PR description', or similar.

RESTful API patterns, request/response formatting, authentication flows, versioning for CampusOS. Use when designing API endpoints, planning request bodies, structuring error responses, or implementing authentication.

Express server scaffolding, plugin architecture, middleware patterns for CampusOS. Use when starting backend development, adding middleware, troubleshooting server startup, or creating new plugin modules.

RESTful API patterns, request/response formatting, authentication flows, versioning for Resource-Adda. Use when designing API endpoints, planning request bodies, structuring error responses, or implementing authentication.

Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.

Express server scaffolding, plugin architecture, middleware patterns for Resource-Adda. Use when starting backend development, adding middleware, troubleshooting server startup, or creating new plugin modules.

Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.

GitHub Actions workflows, testing automation, deployment triggers for Resource-Adda. Use when setting up CI/CD, automating tests, configuring deployments, or managing workflow triggers.

Linting rules, architecture enforcement, code patterns, tech debt tracking for Resource-Adda. Use when enforcing code conventions, managing tech debt, refactoring, or scaling code patterns.

Comprehensive code review for architecture, security, quality, and documentation in Resource-Adda. Use when submitting PRs, preparing releases, onboarding team members, or conducting periodic audits.

Generate commit titles and descriptions from uncommitted changes. Use when the user asks to generate a commit message, wants help writing a commit, or says 'commit', 'commit message', 'what should I commit', or similar.