Engineering
certification-proflie avatar

certification-proflie

A project-specific template skill for maintaining architectural consistency, coding standards, and deployment workflows in AI-powered full-stack applications.

Introduction

This skill acts as a comprehensive project guideline template designed for engineering teams building complex, AI-integrated applications. It provides a standardized framework to align developers on architectural decisions, file structures, and code patterns, specifically tailored for modern stacks involving Next.js, FastAPI, Supabase, and Claude API. By codifying these standards, the skill helps teams minimize technical debt, streamline onboarding for new contributors, and ensure consistent quality across development, testing, and production deployment lifecycles.

  • Standardized architectural overview: Integrates frontend (Next.js 15, TypeScript), backend (FastAPI, Python), and database (Supabase) configurations to ensure system-wide coherence.

  • Best-practice code patterns: Includes reusable implementations for structured API responses, client-side data fetching hooks, and robust Claude AI integration for structured LLM outputs.

  • Systematic testing requirements: Defines clear protocols for E2E testing using Playwright, unit/integration testing with pytest, and coverage reporting.

  • Deployment and maintenance workflows: Documents Google Cloud Run deployment strategies and configuration management to facilitate reliable production releases.

  • Extensible project template: Serves as a foundation that can be adapted to any software project, allowing teams to inject their own specific constraints and patterns.

  • Ideal for software architects and lead developers who need to enforce consistency in large or multi-service codebases.

  • Use this skill when initiating new project modules, onboarding new team members, or conducting architectural reviews.

  • Inputs typically include project requirements and technical constraints; outputs are established coding standards and system design documentation.

  • Constraints: Users must maintain the documentation according to the current repository state to ensure it remains a reliable source of truth.

  • Ensure all architectural decisions are accompanied by ADRs (Architecture Decision Records) to track the evolution of the system over time.

Repository Stats

Stars
0
Forks
0
Open Issues
1
Language
TypeScript
Default Branch
main
Sync Status
Idle
Last Synced
May 7, 2026, 07:40 PM
View on GitHub