summer-core

Detect Summer Framework presence and extract shared domain types from Java Spring projects.

3|2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/taipt1504/agent-skills --skill summer-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summer-core
Source: https://github.com/taipt1504/agent-skills/tree/main/skills/summer-core
Command: npx skills add https://github.com/taipt1504/agent-skills --skill summer-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects whether a project uses the Summer Framework and prevents incorrect or unsafe loading of Summer-specific sub-skills while providing a canonical source of shared domain types and conventions for downstream tasks.

Core Features & Use Cases

  • Hard Gate Enforcement: Verifies presence of io.f8a.summer:summer-platform in build.gradle or pom.xml and blocks loading of summer sub-skills if not found.
  • Version Detection & Compatibility: Reads gradle.properties and scans build files and source patterns to determine Summer versions and feature availability before suggesting features.
  • Shared Domain Types: Exposes and documents core types such as Member, CallerAware, Password, PhoneNumber, ViewableException, JsonErrorResponse, and CommonExceptions for consistent use across handlers and services.
  • Sub-Skill Routing: Recommends which summer sub-skills to load (rest, data, security, ratelimit, test) based on detected modules and version constraints.
  • Safety Rules: Enforces non-guessing, explicit verification, and version-compatibility checks; asks the user when detection is unclear.

Quick Start

Detect whether the repository uses the Summer Framework, determine its version, list shared domain types, and recommend which summer sub-skills to load.

Frequently Asked Questions about summer-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect the Summer Framework version in a Java Spring project?

Detect the Summer Framework version by scanning build.gradle or pom.xml and reading gradle.properties. This process extracts version constraints and checks feature availability before suggesting specific platform features.

What shared domain types are exposed by the Summer Framework for Java Spring WebFlux?

The Summer Framework exposes shared domain types including Member, CallerAware, Password, PhoneNumber, ViewableException, JsonErrorResponse, and CommonExceptions. These types ensure consistent usage across handlers and services.

How do I prevent loading unsafe sub-skills when using io.f8a.summer:summer-platform?

Prevent unsafe sub-skill loading by enforcing a hard gate that verifies io.f8a.summer:summer-platform in build.gradle or pom.xml. This gate blocks sub-skills from loading unless the platform is explicitly confirmed.

Can I use Summer sub-skills without verifying the summer-platform dependency in my build files?

No, you cannot use Summer sub-skills without verifying the summer-platform dependency. The Skill enforces a hard gate requiring explicit verification in build.gradle or pom.xml to prevent incorrect or unsafe loading.

How does module routing determine which Summer sub-skills to load?

Module routing recommends which Summer sub-skills to load by scanning detected modules and version constraints. It routes sub-skills like rest, data, security, ratelimit, and test based on the confirmed Summer Framework version.

What happens if Summer Framework detection is unclear during build file scanning?

If Summer Framework detection is unclear during build file scanning, the Skill enforces safety rules that prevent guessing. It explicitly asks the user for clarification to ensure accurate version detection and compatibility checks.