Total 58,115 skills
Showing 12 of 58115 skills
A skill for reading, researching, and editing pages on Cosense (formerly Scrapbox). Used when users make requests like "Look up XX on Cosense", "Read this Cosense page", "Do XX on Scrapbox", "View the page on scrapbox.io", "Add a comment to this page", etc. Retrieves pages using the cosense CLI and answers users' questions while citing the source of information.
Activated when users are about to make major decisions based on second-hand information (reports, rumors, others' summaries), or when the team shows a tendency to "make decisions without on-the-ground research". Typical trigger signals: "I've read several industry reports", "Just send someone to do the research", "Based on my experience, it should be like this". Non-activation scenarios: Decisions are already based on sufficient first-hand information, low-risk minor decisions don't require in-depth research, or reliable data sources are already under continuous monitoring. Difference from the "Seek Truth from Facts Information Processing Skill": This skill focuses on "how to collect high-quality first-hand information", while the latter focuses on "how to process and refine information after obtaining it".
Activated when users need to extract decision-making signals from a large amount of unorganized information (user feedback, competitor data, market reports, internal metrics). Typical trigger signals: "Too much data, don't know which to trust" "Users are saying all kinds of things" "Received a lot of feedback but don't know what the conclusion is". Scenarios where it is not called: Information is already structured and clear, requiring only simple judgment; or there is no information at all and decisions need to be made based on intuition. Difference from the "Investigation Research Method": This skill focuses on information processing (how to process after obtaining raw materials), while the latter focuses on information collection (how to obtain good raw materials).
Use when you need to design, review, or improve REST APIs with Spring Boot — including HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation and sunset headers, content negotiation (JSON and vendor media types), ISO-8601 instants in DTOs, pagination/sorting/filtering, Bean Validation at the boundary, idempotency, ETag concurrency, HTTP caching, error handling, security, contract-first OpenAPI (OpenAPI Generator), controller advice, and problem details for errors. This should trigger for requests such as Review Java code for Spring Boot REST API; Apply best practices for Spring Boot REST API in Java code; Design Spring Boot REST controllers and DTOs; Add Problem Details error responses in Spring Boot REST; Improve pagination validation or idempotency in Spring APIs. Part of Plinth Toolkit
Use when you need to review, improve, or build Spring Boot 4.0.x applications — including proper usage of @SpringBootApplication, component annotations (@Controller, @Service, @Repository), bean definition and scoping, configuration classes and @ConfigurationProperties (with @Validated), component scanning, conditional configuration and profiles, constructor injection, @Primary and @Qualifier for multiple beans of the same type, bean minimization, graceful shutdown, virtual threads, Jakarta EE namespace consistency, and scheduled tasks. This should trigger for requests such as Review Java code for Spring Boot application; Apply best practices for Spring Boot application in Java code; Improve Spring Boot configuration properties and beans; Review Spring Boot component scanning and profiles; Tune Spring Boot graceful shutdown or virtual threads. Part of Plinth Toolkit
Help users define the strategic context for their product by identifying the right competitive alternatives, unique value drivers, and target segments to win a market category.
Use when you need to design, review, or improve validation in Spring Boot applications — including Bean Validation on request DTOs, @Valid/@Validated at API boundaries, constraint groups, custom constraints, @ConfigurationProperties validation, nested DTO validation, and consistent validation error handling. This should trigger for requests such as Add validation support in Spring Boot; Review Spring Boot validation rules; Improve request validation in Spring Boot REST APIs; Add custom Bean Validation constraints in Spring Boot; Validate configuration properties in Spring Boot. Part of Plinth Toolkit
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should trigger for requests such as Review pom.xml to improve it; Apply Maven best practices to pom.xml; Improve Maven POM configuration; Review Maven dependency management and plugin configuration; Modernize Maven build conventions for a Java project. Part of Plinth Toolkit
Review a plan or in-progress change from its intended final state, separating real compatibility and migration obligations from historical residue. Explicit invocation only; use after planning discussions, requirement changes, prototypes, or rollout completion when the user wants a coherent end-state proposal before implementation.
Deep-dive into any codebase and produce structured knowledge artifacts that turn a coding agent into a codebase specialist. This skill should be used when the user asks to "study this repo", "understand this codebase", "document this project", "onboard me onto this code", "create codebase knowledge", "map this architecture", or when asked to produce knowledge artifacts for any agent working on an unfamiliar repository.
Write tests from a feature spec, treating the spec and its flow contract as the source of truth, stubbing pending tests where implementation is missing and halting when code and spec disagree. Use when the user says "write tests from this spec", "fill the coverage gaps", "prove this wizard works", or after spec-assess-coverage identifies what is untested.
Sweep every spec in the estate for maintenance debt — partial behaviours with no ticket, ageing future behaviours, roll-up statuses that disagree with their behaviours, long-standing open questions, and modules with no specs at all. Use when the user asks "what state are our specs in", "review the spec estate", "which open questions are blocking work", or on a periodic cadence. Reports only.