Shared standards, patterns, and MCP context server for the Forge Space ecosystem.
Part of Forge Space β the open full-stack AI workspace. This repo provides the foundation that all other Forge Space projects build on: code quality standards, security framework, CI/CD workflows, and a local MCP context server for IDE integration.
Version 1.2.0
Forge-Space Core provides shared configurations, workflows, and architectural patterns for consistency across the ecosystem. Centralized feature toggles, reusable GitHub Actions workflows (95% reduction in maintenance overhead), and comprehensive security validation.
- π Zero Secrets: Public repository with comprehensive security validation
- ποΈ Architectural Patterns: Proven patterns for scalable applications
- π Automation: Scripts and workflows for consistent project setup
- π Quality Standards: 80% test coverage, linting, and security scanning
- π‘οΈ Security First: Built-in security scanning and validation
- π³ Docker Patterns: Containerization and deployment patterns
- ποΈ Centralized Feature Toggles: Cross-project feature management with CLI control
- π‘ MCP Context Server: Local stdio MCP server exposing all Forge Space project context documents as resources
- π Logger Module: Comprehensive logging with observability and distributed tracing
- π High Performance: Sub-100ms integration times and optimized patterns
- π GitHub Workflows Optimization: Organization-level reusable workflows eliminating duplication
- mcp-gateway: Python/Node.js MCP gateway with comprehensive CI/CD
- forge-space-ui: Next.js web application with multi-environment deployment
- forge-space-mcp: Node.js MCP server with security-focused workflows
This core repository provides the foundation for the entire Forge Space ecosystem:
- π Shared Standards: Consistent coding patterns across all projects
- π‘οΈ Security Framework: Unified security validation and scanning
- π Automation: Centralized workflows and CI/CD pipelines
- π Quality Gates: Standardized testing and quality requirements
Related Projects:
- Forge Space - UI - AI-powered UI generation platform
- MCP Gateway - Central tool aggregation and routing
- Forge Space - UI MCP - Specialized UI development tools
Documentation:
- Ecosystem Overview - Complete ecosystem guide
- Integration Guide - Step-by-step integration instructions
- Architecture Diagrams - Visual architecture reference
Forge-Space Core now provides centralized reusable workflows that eliminate duplication across the Forge Space ecosystem:
- 95% reduction in maintenance overhead
- Single source of truth for all CI/CD logic
- Organization-level sharing via GitHub Actions
- Zero duplicated files across projects
- ci-base.yml - Unified base CI pipeline with configurable inputs
- security-scan.yml - Comprehensive security scanning and validation
- branch-protection.yml - Automated branch protection and validation
- dependency-management.yml - Centralized dependency updates and auditing
- release-publish.yml - Automated release publishing with version management
# In your project's .github/workflows/ci.yml
jobs:
ci:
uses: Forge-Space/core/.github/workflows/reusable/ci-base.yml@main
with:
project-type: 'gateway' # or 'mcp', 'webapp', 'patterns'
node-version: '22'
python-version: '3.12'
enable-docker: true
enable-security: true
enable-coverage: true- Instant Updates: Change once, apply everywhere
- Consistency: Standardized patterns across all projects
- Maintenance: Single point of update for workflow improvements
- Quality: Centralized testing and validation of workflows
- Configure Repository Access: Enable organization access to Forge-Space/core workflows
- Update Workflow References: Replace local copies with organization references
- Remove Duplicated Files: Delete any local
-shared.ymlfiles - Test and Validate: Ensure workflows run correctly with new references
For complete documentation, see our Documentation Hub which includes:
- Project Context - Complete project guide and context
- Implementation Reports - Integration and analysis reports
- Pattern Documentation - All pattern documentation
- Architecture Decisions - System design decisions
- User Guides - Deployment and user journey guides
- MCP Context Server - Setup and IDE integration for the Forge Space context MCP server
- VSCode Extension - Pattern discovery, scaffolding, and compliance validation in VSCode
- Development Standards - Coding and security standards
npm install @uiforge/forge-patterns# Navigate to your project directory
cd /path/to/your-project
# Use the automated integration CLI
npx forge-patterns integrate
# Or use individual integration commands
npx forge-patterns integrate --project=mcp-gateway
npx forge-patterns integrate --project=uiforge-mcp
npx forge-patterns integrate --project=uiforge-webappuiforge-patterns/
βββ .github/
β βββ workflows/ # CI/CD workflow templates
β βββ templates/ # GitHub templates (PR, issues)
βββ patterns/
β βββ code-quality/ # ESLint, Prettier configurations
β βββ config/ # Centralized configuration management
β βββ docker/ # Docker and containerization patterns
β βββ feature-toggles/ # ποΈ Centralized feature toggle system
β βββ git/ # Git hooks and workflows
β βββ mcp-gateway/ # MCP Gateway patterns (security, performance)
β βββ mcp-servers/ # MCP Server patterns (AI providers, streaming)
β βββ security/ # Security patterns (authentication, middleware)
β βββ shared-infrastructure/ # Shared infrastructure patterns (optimization)
βββ docs/ # π Comprehensive documentation
β βββ architecture/ # Architecture decisions and summaries
β βββ architecture-decisions/ # ADRs for system design
β βββ guides/ # User guides and deployment playbooks
β βββ standards/ # Development and security standards
β βββ reports/ # Implementation and analysis reports
βββ test/ # π§ͺ Comprehensive test suites
β βββ feature-toggle-validation.js # Feature toggle system tests
β βββ cross-project-integration.js # Cross-project integration tests
β βββ performance-benchmark.js # Performance benchmarking
βββ scripts/
β βββ forge-features # ποΈ CLI tool for feature management
β βββ integrate.js # Automated integration script
β βββ security/ # Security validation scripts
β βββ bootstrap/ # Project bootstrap scripts
βββ src/ # TypeScript source files
βββ test/ # π§ͺ Comprehensive test suites
βββ package.json # Package configuration
βββ README.md # This fileNEW: Cross-project feature management with unified control
# Enable global features
forge-features enable global.debug-mode
forge-features enable global.beta-features
# Enable project-specific features
forge-features enable mcp-gateway.rate-limiting
forge-features enable forge-space-ui.rate-limiting
forge-features enable forge-space-mcp.ai-chat
forge-features enable forge-space-ui.dark-mode
# Check feature status
forge-features status --global
forge-features status --project=mcp-gatewayFeatures:
- Global and project-specific feature namespaces
- CLI tool for feature management
- Real-time feature updates
- Cross-project consistency
// Base ESLint config for TypeScript projects
module.exports = {
root: true,
extends: ['eslint:recommended', '@typescript-eslint/recommended', 'prettier'],
// ... comprehensive rules
};{
"semi": true,
"trailingComma": "es5",
"singleQuote": true,
"printWidth": 100,
"tabWidth": 2,
"useTabs": false,
"arrowParens": "always",
"endOfLine": "lf"
}# Three-state service model with sleep/wake architecture
services:
[service-name]:
resources:
memory: "512M"
cpu: "0.5"
memory_reservation: "256M"
sleep_policy:
enabled: true
idle_timeout: 300
priority: "normal"
auto_start: false# Build stage
FROM node:22-alpine AS builder
# ... build process
# Production stage
FROM node:22-alpine AS runtime
# ... optimized production imageversion: '3.8'
services:
app:
build: .
ports:
- "3000:3000"
volumes:
- .:/app
command: npm run devmodule.exports = {
collectCoverageFrom: ['src/**/*.ts'],
coverageThreshold: {
global: {
branches: 80,
functions: 80,
lines: 80,
statements: 80
}
}
};codecov:
coverage:
status:
project:
default:
target: 80%
threshold: 1%#!/bin/bash
# Comprehensive pre-commit validation
echo "π Running Forge Space pre-commit validations..."
# Security validation, linting, testing, etc.# Enforces conventional commit format
# feat, fix, docs, style, refactor, test, chore, etc.# SECURITY NOTICE: PUBLIC REPOSITORY TEMPLATE
JWT_SECRET_KEY=REPLACE_WITH_STRONG_SECRET
DATABASE_URL=REPLACE_WITH_DATABASE_URL
API_KEY=REPLACE_WITH_API_KEY# Automated secret detection and validation
./scripts/security/validate-no-secrets.sh
./scripts/security/validate-placeholders.sh# Start development environment
docker-compose up -d
# View logs
docker-compose logs -f app
# Stop environment
docker-compose down# Build production image
docker build -t my-app .
# Run production container
docker run -p 3000:3000 my-app
# Or use production compose
docker-compose -f docker-compose.prod.yml up -d- π High-Efficiency Standards: Serverless-like efficiency with sleep/wake architecture
- Multi-stage builds: Optimized production images
- Development environments: Hot reload and debugging
- Production deployments: Scaling and monitoring
- Security best practices: Non-root users, minimal images
- Resource Optimization: 50-80% memory reduction, 80-95% CPU reduction
- Fast Wake Times: ~100-200ms vs 2-5 second cold starts
- Costless Scalability: Serverless efficiency with container benefits
- agent-rules.md: Code partner philosophy and minimal changes
- documentation-first.md: Documentation-driven development
- error-handling.md: Consistent error handling patterns
- code-quality-analysis.md: Comprehensive code quality standards
- testing-quality.md: Testing standards and quality assurance
- ts-js-rules.md: TypeScript/JavaScript coding standards
- security-secrets.md: Security and secrets management
- dependencies-security.md: Dependency vulnerability management
- snyk_rules.md: Snyk security scanning rules
- ci-cd.md: CI/CD pipeline standards
- enforcement-automation.md: Automated enforcement of standards
- commit-pr-release.md: Commit, PR, and release standards
- version-management.md: Comprehensive version management
- plan-context.md: Project context and state management
- react-patterns.md: React development patterns
- nextjs-app-router.md: Next.js App Router patterns
- accessibility-openness.md: Accessibility guidelines
- pattern.md: Architectural patterns and SOLID principles
- dependency-injection.md: Dependency injection patterns
- db-migrations.md: Database migration standards
- quality-checks.md: Comprehensive quality validation (// turbo)
- run-tests.md: Testing workflow execution
- verify.md: Implementation verification
- add-framework-template.md: Framework template addition
- implement-tool.md: Tool implementation procedures
- deploy-checklist.md: Deployment preparation
- mcp-docs-and-tools.md: MCP documentation usage
- skill-mcp-docs-search.md: Documentation search skills
- start-and-register-gateway.md: Gateway setup
- connect-ide-to-mcp-gateway.md: IDE integration
- change-gateways-prompts-resources.md: Gateway configuration
- skill-backend-express.md: Express.js development
- skill-frontend-react-vite.md: React + Vite development
- skill-e2e-playwright.md: E2E testing
- use-plan-context.md: Plan context loading
- update-plan.md: Plan maintenance
- safety-shell-commands.md: Safe command execution
- code-generation-templates.md: Code generation and templating
- design-output.md: System design and specification
- docker-deployment.md: Docker deployment expertise
- mcp-docs-search.md: Documentation research and lookup
- mcp-tool-development.md: MCP tool development
- high-efficiency-docker-standards-c1f908.md: Complete Docker standards
- docker-standards-implementation-summary-c1f908.md: Implementation overview
- serverless-mcp-sleep-architecture-c1f908.md: Sleep/wake architecture
- scalable-docker-compose-architecture-c1f908.md: Dynamic scaling
- docker-optimization-lightweight-mcp-c1f908.md: Docker optimization
This repository is designed to be completely public with zero secrets:
- β No actual secrets in any files
- β
All sensitive values use
REPLACE_WITH_[TYPE]format - β Automated secret scanning and validation
- β Comprehensive security workflows
# Run comprehensive security scan
./scripts/security/scan-for-secrets.sh
# Validate no secrets
./scripts/security/validate-no-secrets.sh
# Validate placeholder formats
./scripts/security/validate-placeholders.sh- Trufflehog: Secret detection with verified secrets only
- Gitleaks: Custom secret detection rules
- Custom Validation: Placeholder format validation
- Continuous Monitoring: Daily security scans
- Minimum Coverage: 80% across all metrics
- Coverage Types: Branches, Functions, Lines, Statements
- Quality Gates: Fail builds below 80%
- Reporting: XML, HTML, Terminal formats
- Linting: ESLint/Prettier for consistency
- Type Checking: TypeScript strict mode
- Security Auditing: npm audit for vulnerabilities
- Pre-commit: Automated quality validation
# Create new project with full patterns
./scripts/bootstrap/project.sh my-project node
# Bootstrap specific project types
./scripts/bootstrap/gateway.sh # mcp-gateway style
./scripts/bootstrap/webapp.sh # uiforge-webapp style
./scripts/bootstrap/mcp.sh # uiforge-mcp style# Sync patterns to all projects
./scripts/sync/patterns.sh
# Sync configurations
./scripts/sync/configs.sh
# Sync templates
./scripts/sync/templates.sh# Validate pattern consistency
./scripts/validate/patterns.sh
# Validate security configs
./scripts/validate/security.sh
# Validate code quality
./scripts/validate/quality.sh# Security scanning (automated)
- name: Security Scan
uses: trufflesecurity/trufflehog@v3.93.3
- name: Gitleaks Secret Scan
uses: gitleaks/gitleaks-action@v2
# Quality checks
- name: Lint and Format
- name: Type Check
- name: Test with Coverage
- name: Security Audit- β All linting checks pass
- β All tests pass (100% success)
- β Code coverage β₯ 80%
- β Security scans pass
- β Build verification succeeds
- Setup Guide - Complete setup instructions
- Customization Guide - How to adapt patterns
- Maintenance Guide - Ongoing maintenance
- Docker Guide - Containerization patterns
- Architecture Overview - System architecture
- Security Guidelines - Security best practices
- Deployment Guide - Deployment patterns
- Pattern Catalog - All available patterns
- Configuration Reference - All options
- Troubleshooting - Common issues
We welcome contributions to Forge Space Patterns! Please see our Contributing Guide for details.
- Fork the repository
- Create a feature branch
- Make your changes
- Run all validation scripts
- Submit a pull request
- β Follow security guidelines (no secrets)
- β Pass all automated tests
- β Maintain 80% test coverage
- β Follow conventional commit format
- β Update documentation as needed
MIT License - see LICENSE file for details.
- Repository: https://github.com/Forge-Space/core
- Issues: https://github.com/Forge-Space/core/issues
- Discussions: https://github.com/Forge-Space/core/discussions
For questions, issues, or suggestions:
- π§ Create an issue on GitHub
- π¬ Start a discussion
- π Check the documentation
- π Search existing issues
Forge Space Patterns - Consistency, Security, Quality, Automation, Docker π