Project Configurations
Relevant source files
The following files were used as context for generating this wiki page:
The GeNCorE Command Center is built on a modern web stack utilizing Next.js 15, TypeScript, and Tailwind CSS. The configuration layer manages build processes, development environment settings, styling constraints, and deployment parameters for the Vercel platform.
These configurations ensure a consistent development environment, strict type safety for AI agent interactions, and secure integration with external services like the GitHub REST API and Anthropic SDK.
Sources: README.md:95-101, package.json:20-25, next.config.js:1-6
Build and Environment Configuration
The core application lifecycle is managed through standardized scripts and configuration files that define how the TypeScript code is compiled and served.
TypeScript and Next.js Settings
The project uses tsconfig.json to enforce strict type checking and modern ECMAScript targets (ES2017). A path alias @/* is configured to simplify imports relative to the root directory. The Next.js configuration is kept minimal, enabling React Strict Mode for improved development debugging.
Sources: tsconfig.json:4-29, next.config.js:1-6
Package Management and Dependencies
The package.json file defines the project identity and its runtime requirements. Key dependencies include the Anthropic SDK for Claude interactions and Next.js 15.
| Type | Key Dependencies |
|---|---|
| Runtime | next, react, react-dom, @anthropic-ai/sdk |
| Development | typescript, tailwindcss, postcss, autoprefixer, eslint |
Sources: package.json:1-35
Styling and UI Framework
The project utilizes Tailwind CSS for its "Mobile-first" and "Dark mode" design philosophy. The configuration ensures optimized builds by purging unused styles across the app and component directories.
Tailwind Configuration
Customizations in tailwind.config.js extend the default theme to include a specific font stack optimized for Apple devices (San Francisco) and web standards.
The CSS processing pipeline uses PostCSS to apply Tailwind transformations and Autoprefixer for cross-browser compatibility.
Sources: tailwind.config.js:1-24, postcss.config.js:1-6, app/layout.tsx:1-30
Environment Variables and Deployment
Deployment is targeted at Vercel, as specified in vercel.json. The application relies heavily on environment variables for secure GitHub and AI agent orchestration.
Required Environment Variables
These variables must be configured in the Vercel Dashboard or a local .env.local file.
| Variable | Description | Source |
|---|---|---|
GITHUB_TOKEN | Personal Access Token with repo scope | README.md:46 |
ADMIN_TOKEN | Password for Command Center access | README.md:54 |
NEXT_PUBLIC_REPO_OWNER | Target GitHub organization/user | README.md:55 |
NEXT_PUBLIC_REPO_NAME | Target GitHub repository name | README.md:56 |
Sources: README.md:44-60, vercel.json:1
Security and Middleware Configuration
Security configurations are handled at the edge through Next.js Middleware and custom authentication logic.
Authentication Middleware
The middleware.ts file intercepts requests to protect sensitive routes. It uses a hashed version of the ADMIN_TOKEN for session validation to ensure raw secrets are never stored in client cookies.
Protection Logic
- Session Duration: Cookies are set for 7 days with
httpOnlyandsecureflags (in production). - Unauthorized API Access: Requests to
/api/*return a 401 JSON error instead of a redirect. - SSRF Protection: Configuration ensures PR numbers are validated before being used in GitHub API calls.
Sources: middleware.ts:20-65, README.md:112-120
Conclusion
The project configuration establishes a robust foundation for an AI Command Center. By combining strict TypeScript definitions, a secure middleware layer, and a mobile-optimized Tailwind UI, the system provides a reliable interface for managing GitHub workflows and AI agent assignments across diverse devices.
Sources: README.md:9-14, package.json:5-7