Total Skills
7
Skills published by rotilho with real stars/downloads and source-aware metadata.
Total Skills
7
Total Stars
0
Total Downloads
0
Comparison chart based on real stars and downloads signals from source data.
spring-application-code-style
0
kotlin-cucumber-tests
0
kotlin-code-style
0
deep-research
0
code-practice
0
concise
0
create-skill
0
Apply Spring Boot application-layer conventions for package structure, controllers, services, repositories, transactions, configuration properties, bean wiring, observability, and integration testing. Use when the user wants Spring application structure or Spring application architecture and wiring guidance, including coroutine or Flow usage inside Spring-managed code, especially for WebFlux or coroutine-first services, not shared libraries or framework internals.
Plan, review, or improve Kotlin Cucumber / BDD tests: decide when Cucumber fits, structure feature files, step definitions, hooks, fixtures, and Kotlin helpers, and keep domain language readable without coupling steps to implementation details. Use when the request explicitly centers on Kotlin Cucumber, Kotlin BDD, feature files, step definitions, hooks, or executable-specification tests and reviews.
Apply Kotlin-specific code style and design guidance for file organization, type design, constructors, extensions, nullability, serialization, coroutines, Flow, and Kotlin unit/integration test style outside Cucumber or BDD. Use when the user wants idiomatic Kotlin conventions or Kotlin-language-specific code review guidance, excluding Spring application architecture, Spring-managed wiring concerns, and Cucumber/BDD-specific test design.
Run thorough, evidence-backed research or audit and refresh existing research artifacts with a gap-first workflow: inventory existing knowledge, identify only the missing high-impact gaps, verify important claims with primary sources, and synthesize a decision-useful answer with traceable evidence. Use for research-heavy comparisons, validation, or evidence-backed audits, not routine local code or prompt review.
Improve or apply language-agnostic, framework-neutral code practices for clean code, maintainability, refactoring, ownership, boundaries, state, error handling, testing, and reusable engineering defaults. Use when the user wants broad code quality guidance rather than Kotlin-, Spring-, or framework-specific conventions.
Communication-mode skill for concise replies, brief updates, fewer-token rewrites, and tighter prompts. Keep normal user-facing replies readable and professional, while `caveman` mode is only for internal reasoning, agent coordination, or explicitly requested maximum-brevity output.
Create or improve an agent skill. Use when the user wants a new `SKILL.md`, a rewrite of an existing skill, better trigger coverage or trigger/overlap evaluation, tighter instructions, or a repeated workflow turned into a reusable skill.