Engineering
spec-kit-template-copilot-sh-v0.0.62 avatar

spec-kit-template-copilot-sh-v0.0.62

Architectural expert for the SpecKit template, managing Spec-Driven Development, design patterns, and microservices lifecycle automation.

Introduction

This skill acts as a specialized architectural advisor for projects using the SpecKit Template (v0.0.62). It provides deep, context-aware guidance on maintaining the integrity of microservices-based e-commerce platforms built with Next.js, tRPC, and PostgreSQL. The skill is designed for software engineers and architects who need to navigate the structured Spec-Driven Development (SDD) workflow, ensuring that every feature evolution—from initial specification to implementation—adheres to defined project constitutions and quality gates. It supports decision-making regarding Repository patterns, Service-layer logic, and centralized error handling, while strictly enforcing architectural constraints like Zod-based input validation and secure API gateway conventions.

  • Facilitates the complete SDD lifecycle using CLI commands (/speckit.specify, /speckit.plan, /speckit.tasks, /speckit.implement).

  • Provides expert oversight on design patterns including Repository, Service layer, and dependency injection.

  • Offers technical consultation on Next.js 14, React Server Components, tRPC, Prisma database schemas, and Redis caching layers.

  • Validates architectural compliance against project-specific documentation, including architecture.md and api-design.md.

  • Guides developers through complex refactoring tasks, cross-component debugging, and systemic structural changes.

  • Always consult /docs/architecture.md and /prisma/schema.prisma when providing design recommendations.

  • Ensure all new features follow the established directory structure in features/ and adhere to the project constitution in .specify/memory/constitution.md.

  • Prioritize the use of automated bash scripts located in .specify/scripts/bash/ for workflow integrity.

  • Input validation must rely on Zod schemas; maintain strict separation between UI components and business logic in the Service layer.

  • Use the analyze command to verify consistency across feature branches (NNN-feature-name format) and ensure alignment with the quality gates defined in tasks.md.

Repository Stats

Stars
0
Forks
0
Open Issues
0
Language
Shell
Default Branch
main
Sync Status
Idle
Last Synced
May 4, 2026, 01:14 AM
View on GitHub