agentleFS
Sign inStart free
ch4570ch4570/vulpora/skills/request/SKILL.md

request

Skill1 starsChanged 56 days agoApache-2.0View on GitHub

Scaffold a REST request DTO co-located with its controller, as a validated Kotlin data class. Use when adding a request body for an API endpoint.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer protocol enums from enum over free-form strings.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

request — REST request DTO scaffold

Generate a validated request body for an API endpoint, co-located with its controller.

Authority: AGENTS.md is binding. Review with kotlin-spring-review.

Reference loading (progressive disclosure): Read principles first, then use the KB index. Load only topic files matching the current task; MUST NOT recursively load the entire KB.

Where it goes

  • API module, package com.example.api.<domain> — co-located with the controller (no request/ subfolder). No public keyword.
  • Class name <Action><Entity>Request.

Skeleton (see order/PlaceOrderRequest.kt)

data class <Action><Entity>Request(
    @field:NotBlank
    val <stringField>: String,
    @field:NotNull
    val <enumField>: <ProtocolEnum>,
)

Rules (MUST)

  • data class with val properties.
  • jakarta Bean Validation with the @field: site target (Kotlin): @field:NotBlank, @field:NotNull, etc. The controller validates with @RequestBody @Valid.
  • Identifiers that belong in the URI path (e.g. memberId) stay out of the body.
  • Prefer protocol enums from enum over free-form strings. KDoc per field, in Korean.
  • 생성 코드에 단일 파라미터 람다가 있으면 중첩되지 않은 경우 it을 쓰고, 중첩 스코프를 구분해야 할 때만 내부 파라미터에 이름을 붙인다. 여러 파라미터가 필요한 API는 예외다.

Verify

Compile with the detected build system (gradle/maven/etc.).

Related

[[response]] · [[enum]]

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free