Development
Plugin
plinth
Languages: Español · 中文 Help this project grow: Become a sponsor
Plugin Signal83/100Strong
maintained100
capable100
documented50
adopted56
Install
$ npx -y skills add jabrena/plinth --agent claude-code
Run the curl in your terminal, the rest in Claude Code.
In this plugin
- skills
- 001-commands-inventory
- 002-agents-inventory
- 003-skills-inventory
- 004-commands-installation
- 005-agents-installation
- 012-agile-epic
- 013-agile-feature
- 014-agile-user-story
- 021-problem-framing
- 022-root-cause-analysis
- 023-assumption-analysis
- 024-context-mapping
- 025-quality-attribute-discovery
- 030-architecture-adr-general
- 031-architecture-adr-functional-requirements
- 032-architecture-adr-non-functional-requirements
- 033-architecture-diagrams
- 041-planning-plan-mode
- 042-planning-openspec
- 043-planning-github-issues
- 044-planning-jira
- 045-planning-azure-devops
- 051-design-two-steps-methods
- 052-design-hamburger-method
- 053-design-simple-rules
- 054-design-tdd
- 055-design-parallel-change
- 056-design-avoid-breaking-changes
- 057-design-feature-toggles
- 058-design-bdd
- 059-design-atdd
- 110-java-maven-best-practices
- 111-java-maven-dependencies
- 112-java-maven-plugins
- 113-java-maven-documentation
- 114-java-maven-search
- 121-java-object-oriented-design
- 122-java-type-design
- 123-java-design-patterns
- 124-java-secure-coding
- 125-java-concurrency
- 126-java-exception-handling
- 128-java-generics
- 130-java-testing-strategies
- 131-java-testing-unit-testing
- 132-java-testing-integration-testing
- 133-java-testing-acceptance-tests
- 141-java-refactoring-with-modern-features
- 142-java-functional-programming
- 143-java-functional-exception-handling
- 144-java-data-oriented-programming
- 145-java-refactoring-high-performance
- 151-java-performance-jmeter
- 152-java-performance-gatling
- 161-java-profiling-detect
- 162-java-profiling-analyze
- 163-java-profiling-refactor
- 164-java-profiling-verify
- 170-java-documentation
- 181-java-observability-logging
- 182-java-observability-metrics-micrometer
- 183-java-observability-tracing-opentelemetry
- 200-agents-md
- 300-frameworks-spring-boot-create-project
- 301-frameworks-spring-boot-core
- 302-frameworks-spring-boot-rest
- 303-frameworks-spring-boot-validation
- 304-frameworks-spring-boot-security
- 305-frameworks-spring-boot-modulith
- 311-frameworks-spring-jdbc
- 312-frameworks-spring-data-jdbc
- 313-frameworks-spring-db-migrations-flyway
- 314-frameworks-spring-kafka
- 315-frameworks-spring-mongodb
- 316-frameworks-spring-mongodb-migrations-mongock
- 321-frameworks-spring-boot-testing-unit-tests
- 322-frameworks-spring-boot-testing-integration-tests
- 323-frameworks-spring-boot-testing-acceptance-tests
- 400-frameworks-quarkus-create-project
- 401-frameworks-quarkus-core
- 402-frameworks-quarkus-rest
- 403-frameworks-quarkus-validation
- 404-frameworks-quarkus-security
- 411-frameworks-quarkus-jdbc
- 412-frameworks-quarkus-panache
- 413-frameworks-quarkus-db-migrations-flyway
- 414-frameworks-quarkus-kafka
- 415-frameworks-quarkus-mongodb
- 416-frameworks-quarkus-mongodb-migrations-mongock
- 421-frameworks-quarkus-testing-unit-tests
- 422-frameworks-quarkus-testing-integration-tests
- 423-frameworks-quarkus-testing-acceptance-tests
- 500-frameworks-micronaut-create-project
- 501-frameworks-micronaut-core
- 502-frameworks-micronaut-rest
- 503-frameworks-micronaut-validation
- 504-frameworks-micronaut-security
- 511-frameworks-micronaut-jdbc
- 512-frameworks-micronaut-data
- 513-frameworks-micronaut-db-migrations-flyway
- 514-frameworks-micronaut-kafka
- 515-frameworks-micronaut-mongodb
- 516-frameworks-micronaut-mongodb-migrations-mongock
- 521-frameworks-micronaut-testing-unit-tests
- 522-frameworks-micronaut-testing-integration-tests
- 523-frameworks-micronaut-testing-acceptance-tests
- 701-technologies-openapi
- 702-technologies-wiremock
- 703-technologies-fuzzing-testing
- 704-technologies-sql
- 705-technologies-nosql-mongodb
- 706-technologies-containers-docker
- 707-technologies-hexagonal-architecture
- 801-regulations-eu-ai-act
- 802-regulations-dora
- 803-regulations-gdpr
- 804-regulations-eu-nis2
- 805-regulations-eu-cyber-resilience-act
- 806-regulations-eu-data-act
- 807-regulations-eu-digital-services-act
- 808-regulations-eu-digital-markets-act
- 810-regulations-eu-mifid-ii
- 811-regulations-eu-market-abuse-regulation
- 812-regulations-eu-product-liability-directive
- 813-regulations-iso-42001
- commands
- agents
What's inside
Skills
125/001-commands-inventoryUse when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the project root. This should trigger for requests such as Create embedded commands inventory checklist;/002-agents-inventoryUse when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate/003-skills-inventoryUse when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate/004-commands-installationUse when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should/005-agents-installationUse when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or .codex/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install/012-agile-epicGuides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document
Show all 125 skillsShow fewer
/013-agile-featureGuides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger/014-agile-user-storyGuides the creation of agile user stories. Use when the user wants to create a user story. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story; Split feature requirements into user stories. Part of Plinth Toolkit/021-problem-framingUse when a problem or issue needs explicit framing before deeper analysis begins — establishing the Problem statement, Current state, Desired state, Stakeholders, and Success criteria. This should trigger when an issue's Problem Framing point of view needs evaluation, or when a/022-root-cause-analysisUse when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when/023-assumption-analysisUse when a framed and root-caused problem needs its assumptions made explicit before design or planning begins — explicit Assumptions, Unknowns, and a Validation plan. This should trigger when an issue's Assumption Analysis point of view needs evaluation, or when a maintainer/024-context-mappingUse when a problem under exploration needs its surrounding system context identified before design begins — Existing systems, Integrations, Ownership, and External dependencies. This should trigger when an issue's Context Mapping point of view needs evaluation, or when a/025-quality-attribute-discoveryUse when a problem under exploration needs its quality attributes (non-functional requirements) identified and prioritized before architecture and design begin. This should trigger when an issue's Quality Attribute Discovery point of view needs evaluation, or when a maintainer/030-architecture-adr-generalUse when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for/031-architecture-adr-functional-requirementsFacilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for/032-architecture-adr-non-functional-requirementsFacilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture,/033-architecture-diagramsUse when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams, ER (Entity Relationship) diagrams, and bounded-context diagrams — through a modular, step-based/041-planning-plan-modeUse when creating or refining a structured Java implementation plan from trusted issue summaries, approved designs, ADRs, OpenSpec changes, existing plans, or a valid combination. The plan records its source artifacts and derivation direction and can remain the execution/042-planning-openspecUse when creating or updating OpenSpec artifacts from an issue, plan, approved design, ADRs, existing OpenSpec, or a valid combination. The workflow assesses reviewable scope, records source authority and derivation, handles conflicts, and prevents silent synchronization./043-planning-github-issuesUse when you need GitHub CLI (`gh`) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use repository-owned/044-planning-jiraUse when you need Jira CLI (`jira`) installation/authentication guidance and a maintainer-authored Jira issue inventory workflow. The agent does not ingest raw Jira issue or JQL output directly; it asks the Jira project maintainer/operator to author sanitized issue summaries/045-planning-azure-devopsUse when you need Azure DevOps CLI guidance to verify installation, configure organization and project context, discover work item IDs by optional WIQL filters, and execute safe work-item create/update operations. Uses an interactive install gate - if `az` or the Azure DevOps/051-design-two-steps-methodsUse when a complex or risky code change should be split into Kent Beck's two-step method by first making the change easy through behavior-preserving preparatory refactoring, then making the intended behavior change once the design supports it. This should trigger for requests/052-design-hamburger-methodUse when a large feature, story, plan, or spec idea needs to be split into small vertical slices with the Hamburger Method. This should trigger for requests such as Split this oversized story; Find the smallest useful slice; Break this feature into vertical slices; Apply the/053-design-simple-rulesUse when Java design, refactoring, or implementation tradeoffs should be evaluated with Kent Beck's simple design rules, including passes the tests, reveals intention, has no duplication, and has the fewest elements. This should trigger for requests such as Apply simple design/054-design-tddUse when Java implementation work should be guided by Test-Driven Development, including maintaining a test list, choosing the next behavior, writing a failing test first, implementing only enough production code to pass, and refactoring while keeping tests green. This should/055-design-parallel-changeUse when a database schema or data-meaning change needs Parallel Change, including expand, migrate, and contract sequencing for column renames, type or data reinterpretation, large-table backfills, relationship-table changes, enum/status transitions, timezone/default changes,/056-design-avoid-breaking-changesUse when you need to review a plan, OpenSpec change, specification, or implementation proposal for breaking-change risk across commands, skills, generated outputs, XML sources, README/docs, tests, CI, APIs, schemas, configuration, data, migration, and release guidance. This/057-design-feature-togglesUse when designing, implementing, reviewing, testing, or cleaning up feature toggles, feature flags, kill switches, runtime configuration gates, canary controls, staged rollouts, experiments, or temporary compatibility switches in Java enterprise systems. This should trigger for/058-design-bddUse when a Java change needs independent Behavior-Driven Development guidance from trusted behavior facts through concrete examples and observable scenarios, with focused clarification when behavior is pending or ambiguous. This should trigger for requests such as Apply BDD;/059-design-atddUse when reviewing whether an OpenSpec change's execution goal, acceptance criteria, and implementation or verification tasks are aligned. This should trigger for requests such as Review this OpenSpec change with ATDD; Check acceptance criteria against tasks; Find acceptance/110-java-maven-best-practicesUse 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/111-java-maven-dependenciesUse when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency/112-java-maven-pluginsUse when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information/113-java-maven-documentationUse when you need to create a DEVELOPER.md file for a Maven project — combining a fixed base template with dynamic sections derived from allowlisted Maven POM structure, including a Plugin Goals Reference, Maven Profiles table, and Submodules table for multi-module projects./114-java-maven-searchRoutes Maven version questions to the right workflow by choosing project-local update report interpretation for a user’s own pom.xml, or Maven artifact discovery from maintainer-approved structured evidence. Use when interpreting dependency, plugin, or property update reports;/121-java-object-oriented-designUse when reviewing, improving, or refactoring Java object-oriented design, including applying SOLID, DRY, or YAGNI; improving classes and interfaces; correcting encapsulation, inheritance, or polymorphism; resolving God Class, Feature Envy, or Data Clumps; and improving object/122-java-type-designUse when you need to review, improve, or refactor Java code for type design quality — including establishing clear type hierarchies, applying consistent naming conventions, eliminating primitive obsession with domain-specific value objects, leveraging generic type parameters,/123-java-design-patternsUse when you need to select, review, or implement Java design and integration patterns — including classic Java design patterns, REST API patterns, Kafka and event-driven patterns, database and persistence patterns, and cross-cutting integration patterns. This should trigger for/124-java-secure-codingUse when you need to apply Java secure coding best practices — including validating untrusted inputs, defending against injection attacks with parameterized queries, minimizing attack surface via least privilege, applying strong cryptographic algorithms, handling exceptions/125-java-concurrencyUse when you need to apply Java concurrency best practices — including thread safety fundamentals, ExecutorService thread pool management, concurrent design patterns like Producer-Consumer, asynchronous programming with CompletableFuture, immutability and safe publication,/126-java-exception-handlingUse when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast/128-java-genericsUse when you need to review, improve, or refactor Java code for generics quality — including avoiding raw types, applying the PECS (Producer Extends Consumer Super) principle for wildcards, using bounded type parameters, designing effective generic methods, leveraging the/130-java-testing-strategiesUse when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply/131-java-testing-unit-testingUse when you need to review, improve, or write Java unit tests — including migrating from JUnit 4 to JUnit 5, adopting AssertJ for fluent assertions, structuring tests with Given-When-Then, ensuring test independence, applying parameterized tests, mocking dependencies with/132-java-testing-integration-testingUse when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client infrastructure from import signals, injecting service coordinates dynamically via System.setProperty(),/133-java-testing-acceptance-testsUse when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — confirming @acceptance scenarios before coding, happy path with RestAssured, DB/Kafka test fixtures, WireMock for/141-java-refactoring-with-modern-featuresUse when you need to refactor Java code to adopt modern Java features (Java 8+) — including migrating anonymous classes to lambdas, replacing Iterator loops with Stream API, adopting Optional for null safety, switching from legacy Date/Calendar to java.time, using collection/142-java-functional-programmingUse when you need to apply functional programming principles in Java — including writing immutable objects and Records, pure functions, functional interfaces, lambda expressions, Stream API pipelines, Optional for null safety, function composition, higher-order functions,/143-java-functional-exception-handlingUse when you need to apply functional exception handling best practices in Java — including replacing exception overuse with Optional and VAVR Either types, designing error type hierarchies using sealed classes and enums, implementing monadic error composition pipelines,/144-java-data-oriented-programmingUse when you need to apply data-oriented programming best practices in Java — including separating code (behavior) from data structures using records, designing immutable data with pure transformation functions, keeping data flat and denormalized with ID-based references,/145-java-refactoring-high-performanceUse when you need to refactor Java code for high performance — including memory/allocation reduction, CPU hot-path optimization, and syntax/API/control-flow improvements. This should trigger for requests such as Review Java code for high performance; Optimize Java hot path;/151-java-performance-jmeterUse when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with loops, threads, and ramp-up, or running performance tests from the project root with custom or default/152-java-performance-gatlingUse when you need to set up Gatling performance testing for a Java Maven project — including adding Gatling dependencies and the Gatling Maven plugin, creating Java simulations, running gatling:test, configuring a simulation class, and reviewing generated reports. This should/161-java-profiling-detectUse when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven profiling (CPU, memory, threading, GC, I/O), interactive profiling scripts, JFR integration with Java 25/162-java-profiling-analyzeUse when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and/163-java-profiling-refactorUse when you need to refactor Java code based on trusted profiling analysis findings — including reviewing repository-owned or maintainer-sanitized docs/profiling-problem-analysis and docs/profiling-solutions files, identifying specific performance bottlenecks, and implementing/164-java-profiling-verifyUse when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report generation, quantitative before/after metrics comparison, side-by-side flamegraph analysis, regression/170-java-documentationUse when you need to generate or improve Java project documentation — including README.md files, package-info.java files, and Javadoc enhancements — through a modular, step-based interactive process that adapts to your specific documentation needs. This should trigger for/181-java-observability-loggingUse when you need to implement or improve Java logging and observability — including selecting SLF4J with Logback/Log4j2, applying proper log levels (ERROR, WARN, INFO, DEBUG, TRACE), parameterized logging, correlation context, secure logging without sensitive data exposure,/182-java-observability-metrics-micrometerUse when you need to implement or improve Java metrics observability with Micrometer — including meter design, naming/tag conventions, cardinality control, timers/counters/gauges/distribution summaries, percentiles/histograms, Actuator/Prometheus integration, and metrics/183-java-observability-tracing-opentelemetryUse when you need to implement or improve distributed tracing with OpenTelemetry in Java — including trace/span modeling, context propagation, semantic conventions, span attributes/events/status, sampling strategy, baggage usage, privacy safeguards, and backend integration with/200-agents-mdUse when you need to generate an AGENTS.md file for a Java repository — covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries — through a modular, step-based interactive process that adapts to your specific project needs./300-frameworks-spring-boot-create-projectUse when you need to create a new Maven-based Spring Boot 4.0.x project using SDKMAN-managed Java and Spring Boot CLI tooling. This should trigger for requests such as Create a Spring Boot Maven project; Bootstrap Spring Boot project with SDKMAN; Generate a new Spring Boot/301-frameworks-spring-boot-coreUse 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/302-frameworks-spring-boot-restUse 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,/303-frameworks-spring-boot-validationUse 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/304-frameworks-spring-boot-securityUse when you need to design, review, or improve security in Spring Boot applications — including SecurityFilterChain, OAuth2/JWT resource server patterns, form login basics, method security (@PreAuthorize), CSRF and CORS for APIs, session fixation, security headers, exception/305-frameworks-spring-boot-modulithUse when you need to design, review, or improve modular monoliths with Spring Modulith in Spring Boot applications - including application module package structure, ApplicationModules verification, named interfaces, allowed dependencies, domain events, @ApplicationModuleTest,/311-frameworks-spring-jdbcUse when you need to write or review programmatic JDBC with Spring — including JdbcClient (Spring Framework 7+) as the default API, JdbcTemplate only where batch/streaming APIs require JdbcOperations, NamedParameterJdbcTemplate for legacy named-param code, parameterized SQL,/312-frameworks-spring-data-jdbcUse when you need to use Spring Data JDBC with Java records — including entity design with records, repository pattern, immutable updates, aggregate relationships, custom queries, transaction management, and avoiding N+1 problems. This should trigger for requests such as Review/313-frameworks-spring-db-migrations-flywayUse when you need to add or review Flyway database migrations in a Spring Boot application — Maven dependencies, db/migration scripts, spring.flyway.* configuration, baseline and validation, and alignment with JDBC or Spring Data JDBC. This should trigger for requests such as/314-frameworks-spring-kafkaUse when you need to design or implement Kafka messaging in Spring Boot — including topic design, producer/consumer implementation, JSON serialization with Boot factory customizers, Testcontainers `@ServiceConnection` integration tests, retries and dead-letter topics,/315-frameworks-spring-mongodbUse when you need to design or implement MongoDB data access in Spring Boot — including document modeling, Spring Data Mongo repositories/templates, indexing, optimistic concurrency, and error handling. This should trigger for requests such as Add MongoDB in Spring Boot; Review/316-frameworks-spring-mongodb-migrations-mongockUse when you need to add or review Mongock MongoDB data migrations in a Spring Boot application — including Maven coordinates, Spring Data MongoDB drivers, migration scan packages, @ChangeUnit classes, lock/transaction settings, and optional policy-approved MongoDB integration/321-frameworks-spring-boot-testing-unit-testsUse when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests/322-frameworks-spring-boot-testing-integration-testsUse when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger/323-frameworks-spring-boot-testing-acceptance-testsUse when you need to implement acceptance tests from maintainer-authored or maintainer-sanitized Gherkin scenario facts for Spring Boot applications — including selecting scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest,/400-frameworks-quarkus-create-projectUse when you need to create a new Maven-based Quarkus 3.x project using SDKMAN-managed Java and Quarkus CLI tooling. This should trigger for requests such as Create a Quarkus Maven project; Bootstrap Quarkus project with SDKMAN; Generate a new Quarkus service; Create Quarkus 3/401-frameworks-quarkus-coreUse when building or reviewing core Quarkus applications with CDI beans and scopes, SmallRye Config and profiles, lifecycle, interceptors and events, virtual threads, and test-friendly design. This should trigger for requests such as Review Java code for Quarkus application/402-frameworks-quarkus-restUse when you need to design, review, or improve REST APIs with Quarkus REST (Jakarta REST) — including resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers, optional runtime OpenAPI exposure (SmallRye), contract-first generation/403-frameworks-quarkus-validationUse when you need to design, review, or improve validation in Quarkus applications — including Bean Validation on JAX-RS resources, @Valid on parameters and CDI beans, constraint groups, @ConfigMapping validation, custom constraints, nested DTO validation, and/404-frameworks-quarkus-securityUse when you need to design, review, or improve security in Quarkus applications — including Quarkus Security with JWT/OIDC, basic auth, @RolesAllowed / @Authenticated / @PermitAll, SecurityIdentity, permission checks, path-based authorization in configuration, exception mapping/411-frameworks-quarkus-jdbcUse when you need programmatic JDBC in Quarkus — Agroal DataSource, parameterized SQL, transactions, batching, and Dev Services. This should trigger for requests such as Review JDBC or SQL data access in a Quarkus project; Improve transactions and parameter binding for Quarkus/412-frameworks-quarkus-panacheUse when you need data access with Quarkus Hibernate ORM Panache — including PanacheEntity / PanacheEntityBase, PanacheRepository, named queries, JPQL, native SQL, DTO projections (project(Class)), pagination (Page.of()), N+1 avoidance (JOIN FETCH), optimistic locking (@Version/413-frameworks-quarkus-db-migrations-flywayUse when you need to add or review Flyway database migrations in a Quarkus application — quarkus-flyway extension, db/migration scripts, quarkus.flyway.* configuration, migrate-at-start, and alignment with JDBC or Panache. This should trigger for requests such as Add or review/414-frameworks-quarkus-kafkaUse when you need Kafka messaging in Quarkus with SmallRye Reactive Messaging — including channel/topic design, build-time Jackson serialization, typed @Channel/@Incoming, ack/failure strategies, retries/DLQ, idempotency, Dev Services, and Testcontainers integration tests. This/415-frameworks-quarkus-mongodbUse when you need MongoDB persistence in Quarkus — including Panache Mongo entities/repositories, document design, indexes, transactions where applicable, and error handling. This should trigger for requests such as Add MongoDB in Quarkus; Review Quarkus Mongo Panache design;/416-frameworks-quarkus-mongodb-migrations-mongockUse when you need to add or review Mongock MongoDB data migrations in a Quarkus application — including the Quarkiverse Mongock extension, Quarkus MongoDB client configuration, migrate-at-start, @ChangeUnit classes, lock/transaction settings, and Quarkus test verification. This/421-frameworks-quarkus-testing-unit-testsUse when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI mock replacement, @InjectSpy for partial CDI bean mocking, REST Assured for resource-focused tests,/422-frameworks-quarkus-testing-integration-testsUse when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box/423-frameworks-quarkus-testing-acceptance-testsUse when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured/500-frameworks-micronaut-create-projectUse when you need to create a new Maven-based Micronaut 4.x project using SDKMAN-managed Java and Micronaut CLI tooling. This should trigger for requests such as Create a Micronaut Maven project; Bootstrap Micronaut project with SDKMAN; Generate a new Micronaut service; Create/501-frameworks-micronaut-coreUse when building or reviewing Micronaut applications — Micronaut.run bootstrap, @Singleton/@Prototype, @Factory beans, @ConfigurationProperties, environments, @Requires, @Controller vs services, @Scheduled, graceful shutdown, @ExecuteOn for blocking work, and Jakarta-consistent/502-frameworks-micronaut-restUse when you need to design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI (OpenAPI Generator),/503-frameworks-micronaut-validationUse when you need to design, review, or improve validation in Micronaut applications — including Bean Validation on @Controller methods, @Body @Valid, query/path parameter validation, @ConfigurationProperties validation, custom constraints, nested DTO validation, and/504-frameworks-micronaut-securityUse when you need to design, review, or improve security in Micronaut applications — including micronaut-security authentication, @Secured and intercept-url-map rules, JWT/session strategies, SecurityService checks, CORS, CSRF awareness for browser apps, rejection handlers, and/511-frameworks-micronaut-jdbcUse when you need programmatic JDBC in Micronaut — pooled DataSource, parameterized SQL, io.micronaut.transaction.annotation.Transactional, batching, and domain exception translation. This should trigger for requests such as Review JDBC or SQL data access in a Micronaut project;/512-frameworks-micronaut-dataUse when you need data access with Micronaut Data — @MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, and @MicronautTest with TestPropertyProvider and Testcontainers. For raw java.sql access without/513-frameworks-micronaut-db-migrations-flywayUse when you need to add or review Flyway database migrations in a Micronaut application — micronaut-flyway, db/migration scripts, flyway.datasources.* configuration, and alignment with JDBC or Micronaut Data. This should trigger for requests such as Add or review Flyway/514-frameworks-micronaut-kafkaUse when you need Kafka messaging in Micronaut — including @KafkaClient and @KafkaListener design, @Serdeable serialization, topic/partition strategy, TestPropertyProvider integration tests, retries and dead-letter processing, and error handling. This should trigger for requests/515-frameworks-micronaut-mongodbUse when you need MongoDB persistence in Micronaut — including @MongoRepository design, document modeling, indexes, query patterns, and error handling. This should trigger for requests such as Add MongoDB in Micronaut; Review Micronaut Data Mongo design; Improve error handling/516-frameworks-micronaut-mongodb-migrations-mongockUse when you need to add or review Mongock MongoDB data migrations in a Micronaut application — including Mongock runner/driver selection, Micronaut bean wiring, migration scan packages, @ChangeUnit classes, lock/transaction settings, and Testcontainers verification. This should/521-frameworks-micronaut-testing-unit-testsUse when you need to write unit tests for Micronaut applications — Mockito-first with @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client(/) assertions, @Property overrides, @ParameterizedTest, and *Test vs *IT naming. For framework-agnostic/522-frameworks-micronaut-testing-integration-testsUse when you need to write or improve integration tests for Micronaut — @MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode where appropriate, and Maven Surefire/Failsafe splits for *Test, *Tests, *IT, and *AT. This should trigger for/523-frameworks-micronaut-testing-acceptance-testsUse when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Micronaut applications — @acceptance scenarios, @MicronautTest, HttpClient, BaseAcceptanceTest with TestPropertyProvider for Testcontainers and WireMock, *AT suffix, Failsafe./701-technologies-openapiUse when you need framework-agnostic OpenAPI 3.x guidance — spec structure, metadata and versioning, paths and operations, reusable schemas, security schemes, examples, documentation quality, contract validation (e.g. Spectral), breaking-change awareness, and handoffs to codegen/702-technologies-wiremockUse when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures, isolation and reset between tests, verification of calls, dynamic ports and base URLs, and avoiding/703-technologies-fuzzing-testingUse when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI integration, reproducible failures, and local execution guidance. This should trigger for requests/704-technologies-sqlUse when you need framework-agnostic SQL guidance — schema naming, relational table design, query readability, indexes, transactions, database security, migrations, testing, and monitoring — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests/705-technologies-nosql-mongodbUse when you need framework-agnostic MongoDB and non-relational database query guidance — document schema design, collection modeling, JSON Schema validation, indexes, aggregation pipelines, query performance, consistency trade-offs, transactions, and operational safety —/706-technologies-containers-dockerUse when you need framework-agnostic Docker and container image guidance for Java projects - Dockerfile design, multi-stage Maven builds, jlink custom runtimes, micro runtime distributions such as Alpaquita, JVM container ergonomics, non-root execution, image metadata,/707-technologies-hexagonal-architectureUse when you need framework-agnostic Hexagonal architecture guidance for Java projects - ports and adapters boundaries, application core independence, driving and driven adapters, dependency direction, infrastructure leakage detection, optional architecture tests, and/801-regulations-eu-ai-actUse when reviewing, designing, or modifying Java enterprise systems that use AI, LLMs, AI agents, RAG, tool calling, workflow automation, or model-based decision support and need EU AI Act regulatory awareness. This should trigger for requests such as Review a Java AI system for/802-regulations-doraUse when reviewing, designing, or modifying Java enterprise systems that may support financial entities, critical ICT services, third-party ICT provider integrations, or operational resilience obligations under DORA. This should trigger for requests such as Review a Java/803-regulations-gdprUse when reviewing, designing, or modifying Java enterprise systems that process personal data and need GDPR-aware engineering controls. This should trigger for requests such as Review a Java service for GDPR privacy controls; Design data-subject rights workflows; Add retention,/804-regulations-eu-nis2Use when reviewing, designing, or modifying Java enterprise systems from a maintainer-authored or maintainer-sanitized NIS2 engineering evidence inventory. Supports essential or important entities, critical-sector services, managed service providers, supply-chain dependencies,/805-regulations-eu-cyber-resilience-actUse when reviewing, designing, or modifying Java enterprise products, services, libraries, agents, plugins, connected components, or platform modules that may qualify as products with digital elements and need EU Cyber Resilience Act secure-by-design, vulnerability handling,/806-regulations-eu-data-actUse when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products, cloud providers, APIs, event streams, AI data pipelines, data spaces, or SaaS platforms and need EU Data/807-regulations-eu-digital-services-actUse when reviewing, designing, or modifying Java enterprise systems that may support intermediary services, hosting services, online platforms, marketplaces, content moderation, recommender systems, advertising delivery, complaint workflows, transparency reporting, or/808-regulations-eu-digital-markets-actUse when reviewing, designing, or modifying Java enterprise systems that may support EU Digital Markets Act gatekeeper-platform concerns, core platform services, interoperability, business-user data access, consent-dependent data combination, ranking, self-preferencing,/810-regulations-eu-mifid-iiUse when reviewing Java enterprise evidence for MiFID II investment services, investment activities, client classification, suitability, appropriateness, order-handling evidence, best-execution evidence, algorithmic-trading governance evidence, market-access governance evidence,/811-regulations-eu-market-abuse-regulationUse when reviewing, designing, or modifying Java enterprise systems that may support EU Market Abuse Regulation concerns, market surveillance, suspicious order and transaction reports, insider dealing controls, unlawful disclosure controls, market manipulation detection, inside/812-regulations-eu-product-liability-directiveUse when reviewing, designing, or modifying Java enterprise software products, AI-enabled products, RAG assistants, AI agents, generated instructions, related services, automated updates, vulnerability handling, corrective updates, warnings, instructions, or product-safety/813-regulations-iso-42001Use when reviewing, designing, or modifying Java enterprise systems that use GenAI, LLMs, AI-assisted coding, RAG, AI agents, generated code, generated dependencies, prompt workflows, external model providers, or AI-enabled business logic and need ISO/IEC 42001 AI management
Agents
9plinth-architectJava architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.plinth-business-analystBusiness analyst. Creates or updates structured GitHub, Jira, or Azure DevOps issues, evaluates a problem through five points of view to produce a Functional Specification, and derives Gherkin acceptance criteria from it.plinth-java-coderImplementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.plinth-java-micronaut-coderImplementation specialist for Micronaut projects. Use when writing controllers, REST APIs, validation, security, Micronaut Data repositories, Kafka, MongoDB, CDI-style beans, or any Micronaut-specific code.plinth-java-performanceJava performance coordinator. Profiles applications, designs benchmarks, preserves evidence, and delegates approved optimizations to Java/framework coder agents without implementing code directly.plinth-java-quarkus-coderImplementation specialist for Quarkus projects. Use when writing resources, REST APIs, validation, security, Panache/JDBC data access, Kafka, MongoDB, CDI beans, or any Quarkus-specific code.
Show all 9 agentsShow fewer
plinth-java-spring-boot-coderImplementation specialist for Spring Boot projects. Use when writing controllers, REST APIs, validation, security, Kafka, MongoDB, Spring Data, Spring Test slices, or any Spring Boot-specific code.plinth-no-javaDefault implementation specialist for non-Java projects. Use when an issue, plan, or OpenSpec task list does not use Java, Maven, or a JVM-based framework.plinth-tech-leadTech lead for Java Enterprise Development. Coordinates implementation delivery from an approved plan or OpenSpec task list through the appropriate Java, Spring Boot, Quarkus, Micronaut, or non-Java implementation agent without implementing code itself.
Commands
13/benchmarkDesign and coordinate a reproducible Java performance test./close-specArchive a completed OpenSpec change by name./create-acceptance-criteriaDerive and post confirmed Gherkin acceptance criteria for an issue./create-adrCreate a repository ADR for an approved architectural decision./create-diagramCreate an architecture or design diagram from selected source artifacts./create-feature-branchCreate and switch to a conventionally named feature branch.
Show all 13 commandsShow fewer
/create-specCreate or update OpenSpec artifacts from approved source material./create-worktreeCreate an isolated Git worktree on a new conventionally named branch./explore-designRefine the technical design of an issue or OpenSpec change before implementation./explore-problemAnalyze an issue through five lenses and post a Functional Specification./implement-specDeliver an approved plan or OpenSpec change through controlled implementation./profileCoordinate a reproducible Java profiling and optimization lifecycle./update-issueUpdate an issue description with structured, evidence-backed content.
Badges
2
README
1Plinth for Java
Help this project grow: Become a sponsor
Goal
An opinionated AI-native workflow for evolving modern Java Enterprise SDLC practices through reusable Skills, Agents, Commands & MCP servers.
What is a Plinth?
A
plinthrepresents the solid foundation or platform used to support statues or artworks in art and sculpture. It served as a structural and symbolic foundation for columns, statues, and entire temple podiums. Romans inherited the idea from Greek architecture but expanded its use to emphasize monumentality, hierarchy, and imperial power.
Project at a glance
- 13 Commands
- 9 Agents
- 125 Skills
Latest Updates
Explore the latest published content on https://jabrena.github.io/plinth/ and follow its evolution through new skills, improvements, and fixes in the CHANGELOG.
Start in 60 seconds
Install every skill for your preferred agent:
npx skills add jabrena/plinth --skill '*' --agent cursor -y
npx skills add jabrena/plinth --skill '*' --agent claude-code -y
npx skills add jabrena/plinth --skill '*' --agent codex -y
npx skills add jabrena/plinth --skill '*' --agent github-copilot -y
Install every command for your prefered agent:
install @004-commands-installation cursor
install @004-commands-installation claude-code
install @004-commands-installation codex
install @004-commands-installation github-copilot
Install every agent for your prefered agent:
install @005-agents-installation cursor
install @005-agents-installation claude-code
install @005-agents-installation codex
install @005-agents-installation github-copilot
See it in action
You can use the project in 2 ways:
- Use the AI-Native development workflow
- Refactor your code with Skills
Using AI-Native development workflow
Identify an issue in your Kanban dashboard from Atlasian Jira, Github Issues or Azure DevOps and apply the following workflow:
Issue
|
v
/update-issue --> /explore-problem --> /create-acceptance-criteria
|
v
/create-spec --> /explore-design
|
v
/implement-spec --> /close-spec
Analysis & Design
Turn an idea into an actionable change with user stories, GitHub Issues or Jira, ADRs, diagrams, AI plan mode, and OpenSpec.
Functional Specification:
Technical Specification:
Build
Implement and improve Java applications with Maven, design, coding, testing, security, documentation, Spring Boot, Quarkus, Micronaut, OpenAPI, and WireMock guidance.
Operate
Measure and improve production behavior through observability, profiling, benchmarking, and performance testing.
Compliance (Alpha)
Review Java systems, AI models, and how GenAI tools are used across applications and delivery pipelines for regulation-aware engineering controls, evidence, and qualified owner handoffs spanning AI, data, security, product, platform, market, and governance. These skills support engineering awareness and do not provide legal advice.
| Regulation | Skill |
|---|---|
| EU AI Act | 801-regulations-eu-ai-act |
| DORA | 802-regulations-dora |
| GDPR | 803-regulations-gdpr |
| NIS2 | 804-regulations-eu-nis2 |
| Cyber Resilience Act | 805-regulations-eu-cyber-resilience-act |
| Data Act | 806-regulations-eu-data-act |
| Digital Services Act | 807-regulations-eu-digital-services-act |
| Digital Markets Act | 808-regulations-eu-digital-markets-act |
| MiFID II | 810-regulations-eu-mifid-ii |
| Market Abuse Regulation | 811-regulations-eu-market-abuse-regulation |
| Product Liability Directive | 812-regulations-eu-product-liability-directive |
Note: This set of skills could be a good complement for the future OWASP EU Compliance MCP.
Refactor your code with Skill
Ask your agent:
Use @110-java-maven-best-practices to review this Maven project located in examples/@maven/maven-demo
Explain the findings, apply the approved improvements, and validate the build.
The skill guides the agent through a structured Maven review while keeping you in control of proposed changes.
5-Minute Onboarding
Learn to use this project following the quick guide Getting Started in 5 minutes.
Explore the complete Commands, Agents, Skills, and MCP Servers inventories.
Project Components
The project generates a set of deliverables at the end of any iteration.
| Inventory | Installation | Getting Started |
|---|---|---|
| 1. Commands | @004-commands-installation Install Commands in project | Commands |
| 2. Agents | @005-agents-installation Install Agents in Cursor/Claude | Agents |
| 3. Skills | npx skills add jabrena/plinth --skill '*' --agent cursor -y | Skills |
Compatibility
This project is compatible with any tool that supports Commands, Agents, Skills, MCP Servers and AGENTS.md.
Skill Validations
Every push runs the following validation checks in the Skill Scanners as part of the CI Pipeline to keep documentation and generated skills correct, consistent, and secure:
| Name | Purpose |
|---|---|
| 1. MarkdownValidator | Protects the documentation layer by catching Markdown parsing drift and remote link failures before skill-specific checks run. |
| 2. skill-check | Confirms every generated skill follows the expected packaging contract, complementing scanners that focus on behavior or security risk. |
| 3. cisco-ai-skill-scanner by Cisco | Adds behavior-oriented security coverage by looking for risky skill flows that structural validation cannot see. |
| 4. SkillSpector by NVIDIA | Provides an independent static quality and security review, useful for comparing findings against the other scanners. |
| 5. Snyk Agent Scan by SNYK | Focuses on agent-skill supply-chain and prompt-risk signals, adding another security perspective alongside Cisco and SkillSpector. |
Limitations
Lack of determinism
From the outset, be aware that results from interactions with these Skills and agents are not deterministic because of how the models behave, but you can mitigate that with clear goals and validation checkpoints.
Not all models behave in the same way
Some interactive skills require Premium models for interactive use; otherwise they follow a fixed sequence of steps.
Limits of interactions with models
Models can generate code, but they cannot execute it against your local data. To bridge that gap, some Skills include scripts you run locally.
Software engineers must remain in the loop
This project supports software engineering work; it does not replace engineering judgment. A software engineer must review, guide, and validate AI-generated decisions, code, and outcomes before they are used.
Access to corporate data
Use caution when a problem involves corporate databases or other sensitive organizational data. Before granting an AI-assisted workflow access, assess authorization, privacy, data leakage, retention, and unintended modification risks. Apply least-privilege access, human review, validation, and monitoring. See OWASP GenAI Data Security Risks & Mitigations 2026, and the new set of skills about EU regulation.
Contribute
See CONTRIBUTING.md for ways to support and improve the project.
Architecture Decision Records (ADR)
- Review the ADR index for the complete list.
Java JEPs from Java 8 onward
Java uses JEPs (JDK Enhancement Proposals) to describe new language and platform features. This repository tracks which JEPs could improve the Skills and guidance here.
Further resources
Talks, articles, reference links, skill portals, and related projects live in Project references.
Developed by humans with support from Cursor and Codex, with ❤️ from Madrid
File tree
1470jabrena/plinthView on GitHub
.claude/
.claude-plugin/
marketplace.json
agents
commands
.codex/
config.toml
.cursor/
agents/
plinth-architect.md
plinth-business-analyst.md
plinth-java-coder.md
plinth-java-micronaut-coder.md
plinth-java-performance.md
plinth-java-quarkus-coder.md
plinth-java-spring-boot-coder.md
plinth-no-java.md
plinth-tech-lead.md
commands/
benchmark.md
close-spec.md
create-acceptance-criteria.md
create-adr.md
create-diagram.md
create-feature-branch.md
create-spec.md
create-worktree.md
explore-design.md
explore-problem.md
implement-spec.md
profile.md
update-issue.md
mcp.json
skills
.editorconfig
.gitattributes
.github/
agents
CODEOWNERS
commands
dependabot.yml
FUNDING.yml
PULL_REQUEST_TEMPLATE.md
workflows/
examples-build.yaml
maven.yaml
sf/
create-spec-with-codex.yaml
update-issue-with-codex.yaml
skill-scanners.yml
.gitignore
.mcp.json
.mvn/
jvm.config
wrapper/
maven-wrapper.jar
maven-wrapper.properties
.pre-commit-config.yaml
.sdkmanrc
.serena/
.gitignore
project.yml
AGENTS.md
benchmarks/
problem1/
acceptance-tests-prompts.md
metrics-v1.example.json
metrics-v1.schema.json
README.md
scenario1/
demo/
.gitkeep
gherkin/
scenario1.feature
README.md
results/
.gitkeep
20260718T180736Z-cursor-composer.json
20260718T182709Z-cursor-composer-2.5-fast.json
20260718T201032Z-cursor-composer.json
20260718T202221Z-cursor-composer.json
20260718T203320Z-codex-gpt-5.json
20260718T210313Z-codex-gpt-5.json
20260718T211359Z-codex-gpt-5.json
20260718T212300Z-cursor-claude-sonnet-4-5.json
20260718T214700Z-claude-code-claude-sonnet-5.json
20260718T215507Z-claude-code-claude-sonnet-5.json
20260721-141828-copilot-claude-sonnet-4.5.json
20260721-225100-copilot-claude-sonnet-4.5.json
20260721T205321Z-claude-code-claude-sonnet-5.json
20260722T174436Z-github-copilot-claude-opus-4.json
20260809T185527Z-cursor-grok-4.5.json
example.result.json
README.md
specs/
functional-requirements/
README.md
scenario2/
demo/
.gitkeep
gherkin/
scenario2.feature
README.md
results/
.gitkeep
20260718T182956Z-cursor-composer-2.5-fast.json
20260718T201505Z-cursor-composer.json
20260718T202421Z-cursor-composer.json
20260718T204424Z-codex-gpt-5.json
20260718T213027Z-cursor-sonnet-4-6.json
20260718T214223Z-claude-code-sonnet-5.json
20260718T215456Z-claude-code-sonnet-5.json
20260721-145056-copilot-claude-sonnet-4.5.json
20260809T185517Z-cursor-grok-4.5.json
example.result.json
README.md
specs/
functional-requirements/
problem1/
ADR-001-God-Analysis-API-Functional-Requirements.md
ADR-002-God-Analysis-API-Non-Functional-Requirements.md
ADR-003-God-Analysis-API-Technology-Stack.md
my-json-server-oas.yaml
README.md
US-001_god_analysis_api.feature
US-001_God_Analysis_API.md
US-001-god-analysis-api.openapi.yaml
scenario3/
.agents/
skills/
openspec-propose/
SKILL.md
demo/
.gitkeep
gherkin/
scenario3.feature
README.md
results/
.gitkeep
20260718T203620Z-cursor-composer-2.5-fast.json
20260718T205106Z-codex-gpt-5.json
20260718T211603Z-codex-gpt-5.json
20260718T215700Z-claude-code-sonnet-5.json
20260718T232651Z-cursor-claude-sonnet-4-6.json
20260721-145543-copilot-claude-sonnet-4.5.json
20260722T142821Z-github-copilot-claude-sonnet-4.5.json
20260722T153524Z-github-copilot-claude-opus-4-5.json
20260809T185257Z-cursor-cursor-grok-4.5.json
example.result.json
README.md
specs/
functional-requirements/
problem1/
ADR-001-God-Analysis-API-Functional-Requirements.md
ADR-002-God-Analysis-API-Non-Functional-Requirements.md
ADR-003-God-Analysis-API-Technology-Stack.md
my-json-server-oas.yaml
README.md
US-001_god_analysis_api.feature
US-001_God_Analysis_API.md
US-001-god-analysis-api.openapi.yaml
scenario3.md
technical-requirements/
openspec/
changes/
add-god-analysis-api/
.openspec.yaml
design.md
proposal.md
specs/
god-analysis-api/
spec.md
tasks.md
config.yaml
README.md
scenario4/
demo/
.gitkeep
gherkin/
scenario4.feature
README.md
results/
.gitkeep
20260718T192207Z-cursor-composer-2.5-fast.json
20260718T193351Z-cursor-gpt-5-5.json
20260718T195308Z-cursor-gpt-5.5.json
20260718T200637Z-cursor-composer.json
20260718T204946Z-cursor-composer.json
20260718T210520Z-cursor-composer-2.5-fast.json
20260718T211651Z-codex-gpt-5.json
20260718T215710Z-claude-code-claude-sonnet-5.json
20260719T095543Z-codex-gpt-5.json
20260719T101831Z-claude-code-claude-sonnet-5.json
20260719T102739Z-codex-gpt-5.json
20260719T103500Z-cursor-claude-sonnet-4-6.json
20260719T110500Z-cursor-composer.json
20260719T111807Z-codex-gpt-5.json
20260719T112608Z-claude-code-claude-sonnet-5.json
20260719T113531Z-cursor-grok-4.5.json
20260719T114550Z-cursor-composer-2.5-fast.json
20260719T144644Z-cursor-composer-2.5-fast.json
20260719T145732Z-codex-gpt5.json
20260719T152526Z-cursor-claude-sonnet-4-6.json
20260719T161211Z-claude-code-claude-sonnet-5.json
20260719T162838Z-codex-gpt-5.json
20260721-145724-copilot-claude-sonnet-4.5.json
20260721T230500Z-github-copilot-claude-opus-4.json
20260809T190045Z-cursor-grok-4.5.json
example.result.json
README.md
specs/
functional-requirements/
problem1/
ADR-001-God-Analysis-API-Functional-Requirements.md
ADR-002-God-Analysis-API-Non-Functional-Requirements.md
ADR-003-God-Analysis-API-Technology-Stack.md
my-json-server-oas.yaml
README.md
US-001_god_analysis_api.feature
US-001_God_Analysis_API.md
US-001-god-analysis-api.openapi.yaml
technical-requirements/
openspec/
changes/
add-god-analysis-api/
.openspec.yaml
design.md
proposal.md
specs/
god-analysis-api/
spec.md
tasks.md
config.yaml
README.md
scenario5/
demo/
.gitkeep
gherkin/
scenario5.feature
results/
.gitkeep
20260809T110956Z-codex-gpt-5.6.json
20260809T113253Z-codex-gpt-5.4.json
20260809T114340Z-codex-gpt-5.5.json
20260809T120318Z-claude-code-claude-sonnet-5.json
20260809T122232Z-claude-code-claude-opus-5.json
20260809T124008Z-cursor-grok-4.5.json
20260809T125321Z-cursor-composer-2.5.json
20260809T190050Z-cursor-grok-4.5.json
example.result.json
notes.md
README.md
specs/
functional-requirements/
problem1/
ADR-001-God-Analysis-API-Functional-Requirements.md
ADR-002-God-Analysis-API-Non-Functional-Requirements.md
ADR-003-God-Analysis-API-Technology-Stack.md
my-json-server-oas.yaml
README.md
US-001_god_analysis_api.feature
US-001_God_Analysis_API.md
US-001-god-analysis-api.openapi.yaml
technical-requirements/
openspec/
changes/
add-god-analysis-api/
.openspec.yaml
design.md
proposal.md
specs/
god-analysis-api/
spec.md
tasks.md
config.yaml
README.md
problem2/
acceptance-tests-prompts.md
metrics-v2.example.json
metrics-v2.schema.json
README.md
scenario1/
demo/
.gitkeep
gherkin/
scenario1.feature
README.md
results/
.gitkeep
20260809T152722Z-codex-gpt5-6.json
20260809T165756Z-codex-gpt5-6.json
20260809T172123Z-cursor-grok-4-5.json
20260809T173221Z-cursor-composer-2-5-fast.json
20260809T180238Z-claude-code-claude-sonnet-5.json
20260809T183816Z-claude-code-claude-sonnet-5.json
20260809T184743Z-cursor-grok-4-5.json
example.result.json
README.md
specs/
functional-requirements/
greek_gods.feature
greekController-oas.yaml
my-json-server-oas.yaml
README.md
schema.sql
structurizr-1-Component-001.png
uml-sequence-diagram.plantuml
uml-sequence-diagram.png
scenario2/
demo/
.gitkeep
gherkin/
scenario2.feature
README.md
results/
.gitkeep
20260809T153855Z-codex-gpt5-6.json
20260809T170358Z-codex-gpt-5-6.json
20260809T172311Z-cursor-grok-4-5.json
20260809T173213Z-cursor-composer.json
20260809T175044Z-claude-code-claude-sonnet-5.json
20260809T183619Z-claude-code-claude-sonnet-5.json
20260809T184936Z-cursor-grok-4-5.json
example.result.json
README.md
specs/
functional-requirements/
agile/
PLAN-US-001_Implementation.plan.md
US-001_api_greek_gods_data_retrieval.feature
US-001_API_Greek_Gods_Data_Retrieval.md
design/
ADR-001_REST_API_Functional_Requirements.md
ADR-002-Acceptance-Testing-Strategy.md
ADR-003-Greek-Gods-API-Technology-Stack.md
greek_gods_api_sequence_diagram.png
greek_gods_api_sequence_diagram.puml
greekController-oas.yaml
my-json-server-oas.yaml
schema.sql
scenario3/
.agents/
skills/
openspec-propose/
SKILL.md
demo/
.gitkeep
gherkin/
scenario3.feature
README.md
results/
.gitkeep
20260809T154757Z-codex-gpt5-6.json
20260809T164739Z-codex-gpt5-6.json
20260809T170024Z-codex-gpt5-6.json
20260809T171832Z-cursor-grok-4.5.json
20260809T173305Z-cursor-composer-2.5.json
20260809T175515Z-claude-code-sonnet-5.json
20260809T184853Z-cursor-grok-4.5.json
example.result.json
README.md
specs/
functional-requirements/
agile/
PLAN-US-001_Implementation.plan.md
US-001_api_greek_gods_data_retrieval.feature
US-001_API_Greek_Gods_Data_Retrieval.md
design/
ADR-001_REST_API_Functional_Requirements.md
ADR-002-Acceptance-Testing-Strategy.md
ADR-003-Greek-Gods-API-Technology-Stack.md
greek_gods_api_sequence_diagram.png
greek_gods_api_sequence_diagram.puml
greekController-oas.yaml
my-json-server-oas.yaml
schema.sql
technical-requirements/
openspec/
changes/
add-greek-gods-api/
.openspec.yaml
design.md
proposal.md
specs/
greek-gods-api/
spec.md
tasks.md
config.yaml
README.md
scenario4/
demo/
.gitkeep
gherkin/
scenario4.feature
README.md
results/
.gitkeep
20260809T161029Z-codex-gpt5.json
20260809T171249Z-codex-gpt5.json
20260809T171831Z-cursor-grok45.json
... 1600 moreShowing a partial view of a very large repo.
FAQ
plinth is a Claude Code plugin with 125 hand-picked skills for development work, indexed on Flowy. Install it with the command on its page. It includes 001-commands-inventory, 002-agents-inventory, 003-skills-inventory. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
- What is plinth?
- Languages: Español · 中文 Help this project grow: Become a sponsor
- How do I install plinth?
- Run these in Claude Code: npx -y skills add jabrena/plinth --agent claude-code. Then prompt normally.
- Does plinth auto-invoke its skills?
- Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
- Is plinth free?
- Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.