CampusOS

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.

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

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

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

Issues, labels, contributor workflow, pull request process for CampusOS. Use when onboarding contributors, documenting issue labels, setting up contribution guidelines, or managing PR workflow.

MongoDB/Mongoose schema design, indexing, relationships, query patterns for CampusOS. Use when designing data models, creating Mongoose schemas, optimizing queries, or setting up database connections.

Security audits, dependency updates, compatibility checks, pnpm package management for CampusOS. Use when updating dependencies, auditing security, managing package versions, or resolving conflicts.

Docker images, container setup, Docker Compose, multi-stage builds for CampusOS. Use when containerizing the app, setting up Docker Compose, building images, or deploying containers.

Get started with CampusOS development. Use when setting up the local environment, making a first contribution, troubleshooting setup issues, or understanding project structure.

API documentation, OpenAPI specs, developer guides for CampusOS. Use when documenting APIs, creating developer guides, generating API specs, or maintaining documentation.

Follow CampusOS branching and PR process. Use when starting new work, creating pull requests, reviewing code, merging to main, or resolving merge conflicts.

Logging, error tracking, debugging, health checks for CampusOS. Use when setting up logging, tracking errors, debugging production issues, or monitoring service health.

Performance metrics, SLAs, dashboards, latency tracking for CampusOS. Use when tracking service metrics, setting SLOs, monitoring latency, or identifying bottlenecks.

Profile and optimize CampusOS performance. Use when investigating slow pages, reducing bundle size, optimizing memory usage, or improving Lighthouse scores.

Semantic versioning, changelog generation, release tags, version bumping for CampusOS. Use when preparing releases, bumping versions, creating release branches, or generating changelogs.

Automated changelog, version summaries, release announcements for CampusOS. Use when creating release announcements, automating release notes, or publishing updates.

OWASP vulnerabilities, authentication hardening, encryption, secrets management for CampusOS. Use when implementing auth, encrypting data, managing environment variables, preventing injection/XSS, or hardening endpoints.

Vulnerability disclosure, responsible reporting, compliance, security contacts for CampusOS. Use when setting up security reporting, creating vulnerability disclosure policy, or managing incident response.

Vitest test framework, mongodb-memory-server, service testing patterns for CampusOS. Use when writing unit tests, setting up test infrastructure, creating test fixtures, or planning test coverage.

Get started with CampusOS development. Use when: setting up local environment, making your first contribution, troubleshooting setup issues, understanding project structure.

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

Express server scaffolding, plugin architecture, middleware patterns. Use when: starting backend development, adding middleware, troubleshooting server startup, designing plugin systems.

GitHub Actions workflows, testing automation, deployment triggers. Use when: setting up CI/CD, automating tests, configuring deployments, managing workflow triggers, caching dependencies.

Linting rules, architecture enforcement, code patterns, tech debt tracking. Use when: enforcing code conventions, managing tech debt, refactoring, scaling code patterns.

Comprehensive codebase review for inconsistencies, security vulnerabilities, code quality, and documentation. Use when: submitting PRs, preparing releases, onboarding new team members, or conducting periodic audits. Covers architecture patterns, dependency security, linting, type checking, and Humanet validation.

Issues, labels, contributor workflow, pull request process. Use when: onboarding contributors, documenting issue labels, setting up contribution guidelines, managing PR workflow.

Database schema design, migrations, relationships, indexing strategies. Use when: designing data models, creating migrations, optimizing queries, setting up database connections, handling relationships.

Security audits, dependency updates, compatibility checks, vulnerability scanning. Use when: updating dependencies, auditing security, managing package versions, resolving conflicts.

Docker images, container setup, Docker Compose, multi-stage builds, registry deployment. Use when: containerizing app, setting up Docker Compose, building images, pushing to registry.

API documentation, Swagger/OpenAPI, tutorials, code examples. Use when: documenting APIs, auto-generating docs, creating developer guides, publishing API specs.

Build React components in Next.js using CampusOS patterns. Use when: implementing new UI modules, refactoring existing components, setting up state management, optimizing component performance.

Follow CampusOS branching and PR process. Use when: starting new work, creating pull requests, reviewing code, merging to main, resolving merge conflicts.

Logging systems, error tracking, debug sessions, dashboards. Use when: setting up logging, tracking errors, debugging production issues, monitoring service health.