codebase-reference

Document the Cebu Airsoft Hub stack, conventions, and patterns.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jacocanete/cebu-airsoft-hub --skill codebase-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-reference
Source: https://github.com/jacocanete/cebu-airsoft-hub/tree/main/.opencode/skills/codebase-reference
Command: npx skills add https://github.com/jacocanete/cebu-airsoft-hub --skill codebase-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single, living reference that captures the Cebu Airsoft Hub project's tech stack, file and routing conventions, data-fetching patterns, backend expectations, and design system so reviewers, maintainers, and new contributors have immediate, consistent context.

Core Features & Use Cases

  • Living documentation of the stack (TanStack Start, React, Prisma, Express, Socket.io), environment, and deployment notes.
  • Coding and review conventions including routing/file patterns, hook structure, naming rules, and file-size guidelines to ensure consistent PR reviews.
  • Data-fetching and real-time patterns describing React Query hooks, Socket.io usage, api wrapper behavior, and backend route order (validation, auth, prisma, response).
  • Design system and tokens covering brand colors, typography, shared prose classes, and component usage rules to keep UI consistent.
  • Use Cases: accelerate onboarding, guide code reviews, produce context-aware live suggestions during refactors, and inform automated analysis or agent recommendations.

Quick Start

Ask the skill to summarize the project's routing, data-fetching, and naming conventions into a concise checklist for a code review.

Frequently Asked Questions about codebase-reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document React and Prisma codebase conventions for consistent code reviews?

To document codebase conventions for reviews, maintain a living reference capturing your tech stack, routing patterns, and data-fetching rules. This provides reviewers and maintainers with immediate, consistent context for project-specific guidance.

What is the best way to structure React Query and Socket.io patterns in a project reference?

The best way to structure real-time and data-fetching patterns is to describe React Query hook usage, Socket.io integration, and API wrapper behavior. This ensures backend route order and context-aware assistance remain consistent across the project.

How do I create a code review checklist for routing and file conventions in a React codebase?

Create a code review checklist by summarizing project routing, file patterns, and naming rules into concise guidelines. This enforces consistent file-size limits and structural conventions during pull request reviews.

Does this codebase reference include design system tokens and UI component usage rules?

Yes, the codebase reference includes design system tokens and component usage rules. It covers brand colors, typography, and shared prose classes to keep the UI consistent across developer contributions and refactors.

Can I use this reference to accelerate onboarding for new contributors to a Prisma and Express stack?

Yes, you can use the reference to accelerate onboarding for new contributors. It provides stack details, environment notes, and backend expectations, giving new developers immediate context for the Prisma and Express architecture.