project-types

What problem does it solve? When scaffolding a new Java/Spring Boot project, developers often guess which coding standards and skills apply, leading to inconsistent setups or missing mandatory practices. This meta-skill removes that guesswork by mapping each project kind to its required and optional skills before repository creation. ## Core Features & Use Cases - Type Matrix: Defines five canonical project shapes — synchronous REST microservice, event-driven service, scheduler/batch job, library/SDK, and monolith-with-microservice-bones — each with required and optional skills. - Decision Flow: Provides a branching questionnaire (HTTP exposure, event consumption, scheduling, bounded contexts) to classify any new service deterministically. - Orchestration Presets: Pre-fills answers for the create-repo skill per project type, including naming conventions for entry points (controller, consumer, scheduler) and package structure. - Use Case: A team starting a Kafka consumer service invokes this skill first; it classifies the project as Type B, mandates messaging and persistence skills, and skips HTTP-specific skills like api-design. ## Quick Start Ask the AI to classify your new service using the project-types skill and pre-select the required skills before running create-repo.