By CinqueIzumi
Shared Claude Code assets for the nl.rhaydus Kotlin/Compose/TOAD apps: code-reviewer and unit-test-writer subagents, a style-check skill, and a docs-first exploration hook.
Use this agent when code changes have been made and need to be reviewed for correctness, style compliance, and architectural fit. This includes after implementing new features, refactoring existing code, fixing bugs, or any time files have been modified and a quality check is needed.\n\nExamples:\n\n- user: "Please add a caching layer to the database service"\n assistant: *implements the caching layer*\n Since significant code changes were made, use the Agent tool to launch the code-reviewer agent to review the changes for correctness, style, and architecture.\n assistant: "Now let me use the code-reviewer agent to review the changes I just made."\n\n- user: "Can you refactor the authentication module to use the new token format?"\n assistant: *refactors the authentication module*\n Since code was refactored, use the Agent tool to launch the code-reviewer agent to verify the refactoring is correct and follows conventions.\n assistant: "Let me use the code-reviewer agent to review the refactored authentication module."\n\n- user: "Review my recent changes"\n assistant: "I'll use the code-reviewer agent to review your recent changes."\n Use the Agent tool to launch the code-reviewer agent to inspect all changed files.
Use this agent when you need unit tests written for new or changed code. This includes after implementing a new function, class, or module, after refactoring existing code, or when the user explicitly asks for tests to be written for specific files or functions.\n\nExamples:\n\n- user: "Please write a function that calculates the factorial of a number"\n assistant: "Here is the factorial function: ..."\n [function implementation]\n Since a significant piece of code was written, use the Agent tool to launch the unit-test-writer agent to write comprehensive unit tests for the new function.\n assistant: "Now let me use the unit-test-writer agent to write unit tests for this function."\n\n- user: "I just refactored the authentication module, can you write tests for it?"\n assistant: "I'll use the unit-test-writer agent to analyze the authentication module and write comprehensive unit tests."\n Since the user explicitly asked for tests on specific code, use the Agent tool to launch the unit-test-writer agent.\n\n- user: "Add input validation to the UserProfile class"\n assistant: "Here's the updated UserProfile class with input validation: ..."\n [code changes]\n Since validation logic was added with many potential edge cases, use the Agent tool to launch the unit-test-writer agent to ensure all edge cases are covered.\n assistant: "Let me now use the unit-test-writer agent to write tests covering all the validation edge cases."
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Shared foundation for the nl.rhaydus apps (Nestbox, Softcover): the TOAD presentation runtime,
Gradle convention plugins, custom ktlint rules, a shared version catalog, the design-system skeleton,
and the reusable Claude Code assets (skills, agents, hooks, conventions docs).
Status: bootstrapping. See
MIGRATION.mdfor the full plan, phase status, and the decisions log. Update that file at the end of every session.
| Path | What | Distribution |
|---|---|---|
gradle/libs.versions.toml | shared version catalog | published catalog artifact |
build-logic/ | convention plugins (rhaydus.*) | includeBuild / published |
ktlint-rules/ | custom lint ruleset | published jar |
toad/ | TOAD runtime (nl.rhaydus.toad) | published KMP lib |
designsystem-core/ | theme/typography skeleton | published KMP lib |
docs/ | canonical conventions | bundled in the Claude plugin |
claude/ | Claude Code plugin + marketplace | plugin install |
Published artifacts go to Maven Central (group nl.rhaydus), so consumers need no credentials
— just mavenCentral(), which both apps already declare. While actively developing the foundation,
source-link it instead:
local.properties: foundation.local=truesettings.gradle.kts reads that flag and includeBuild("../rhaydus-foundation").
Gradle substitutes the published coordinates for local source automatically — no version bumps.false (or remove it) to return to the pinned published version.Consuming needs nothing. Publishing to Maven Central needs a Central Portal user token + a PGP signing
key, supplied via env/Gradle properties (never committed) — see the secret names in
.github/workflows/publish.yml. The nl.rhaydus namespace is verified with a DNS TXT record on
rhaydus.nl (no server required). Releases are normally done by CI on a v* tag.
./gradlew help # configuration check (no modules yet)
./gradlew build # once modules exist
./gradlew publishToMavenLocal # local smoke test of publishing
./gradlew publishAndReleaseToMavenCentral # release (normally done by CI on a v* tag)
npx claudepluginhub cinqueizumi/rhaydus-foundation --plugin rhaydus-kotlinComplete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development
Complete creative writing suite with 10 specialized agents covering the full writing process: research gathering, character development, story architecture, world-building, dialogue coaching, editing/review, outlining, content strategy, believability auditing, and prose style/voice analysis. Includes genre-specific guides, templates, and quality checklists.
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications