Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
lombok-patterns
Lombok annotations and best practices for Java 21+ projects. Use when reducing boilerplate, configuring builders, or choosing between Lombok and Records.
emvnuel/SKILL.md 1
-
testing-patterns
REST integration testing patterns with JUnit 5, Mockito, RestAssured. Use when writing integration tests that mock external dependencies, use Testcontainers/H2 for databases, and test endpoints with raw JSON bodies.
emvnuel/SKILL.md 1
-
ddd-da-massa
Practical DDD patterns for Jakarta EE web applications with cognitive load distribution. Use when designing controllers, entities, services, or evaluating cohesion and load balance.
emvnuel/SKILL.md 1
-
cdd-design-pillars
Measures and limits cognitive load in Jakarta EE/MicroProfile code. Use when reviewing code complexity, designing services/entities, or identifying when to extract abstractions.
emvnuel/SKILL.md 1
-
gof-design-patterns
Detects opportunities to apply GoF Design Patterns in Jakarta EE/MicroProfile. Use when reviewing code for structural improvements or implementing creational, structural, or behavioral patterns.
emvnuel/SKILL.md 1
-
rest-api-design
REST API design patterns and MicroProfile OpenAPI documentation. Use when designing endpoints, choosing HTTP methods, status codes, or documenting APIs with OpenAPI annotations.
emvnuel/SKILL.md 1
-
clean-code-principles
Detects violations of Clean Code principles and suggests refactorings. Use when reviewing code quality, improving readability, or refactoring methods, classes, and modules.
emvnuel/SKILL.md 1
-
quarkus-panache-smells
Detects and refactors ORM code smells in Quarkus Panache applications using the Repository pattern. Use when reviewing PanacheRepository code, diagnosing N+1 queries, data overfetching, or pagination issues.
emvnuel/SKILL.md 1
-
vibedev-flow-designer
Use when translating a program/app idea into a VibeDev MCP Job (deliverables, definition of done, invariants, and a small step plan) and preparing it to transition to READY without implementing features yet
coldshalamov/VibeDev
-
vd-create
Create or refine a VibeDev Studio UnifiedWorkflow graph via tool calls. Use when the user says `$vd-create`, asks the model to “build the workflow graph”, “set up Research/Planning/Execution/Review steps”, or wants the model to collaboratively design prompts/conditions/breakpoints and write them into `unified_workflows` so the UI canvas shows the plan before running `$vd-next`.
coldshalamov/VibeDev
-
vd-next
Advance a VibeDev workflow from chat. Use when the user types `$vd-next` / says “vd next” and wants the agent to fetch the next compiled step prompt from the VibeDev MCP HTTP server (`vibedev-mcp serve`) and handle breakpoint/new-thread/diagnose states.
coldshalamov/VibeDev
-
debug-mode
Run an iterative, hypothesis-driven “debug mode” loop to diagnose and fix a bug using targeted instrumentation and log capture. Use when the user wants an interactive debug loop, when you need to quickly narrow a failure via added debug statements, or when you need a lightweight way to centralize logs from a repro run (via `agent-skills debug` server + SSE UI).
strantalis/agent-skills
-
crypto-expert
Crypto best-practices guidance and review across languages and domains. Use whenever cryptography, encryption, hashing, signatures, key/nonce/IV handling, randomness, password storage, TLS/PKI, secure channels, token formats, or "roll your own crypto" is mentioned, including high-level questions or code/design reviews. Trigger broadly to prevent subtle security mistakes.
strantalis/agent-skills
-
gh-cli
Standardize all GitHub interactions via the GitHub CLI (`gh`) instead of ad-hoc URLs, UI clicks, or direct REST API calls. Use when you need to read or change GitHub state (repos, issues, pull requests, reviews, check status, Actions workflows/runs, releases, labels, milestones, discussions, gists) and want deterministic output (prefer `--json` + `--jq`). Also use when the user provides a GitHub URL, including deep links like `https://github.com/OWNER/REPO/pull/123`, `.../issues/123`, `.../pull/123/files`, or comment permalinks like `#issuecomment-...`, and you need to fetch the underlying PR/issue/thread and reply. Fall back to `gh api` only when there is no first-class `gh NOUN VERB` command.
strantalis/agent-skills
-
context7-cli
Use the local Context7 CLI in this repo to search libraries and fetch Context7 context for skills or documentation tasks. Trigger when you need to run `c7 search`/`c7 context`, resolve library IDs, or retrieve text/json outputs from Context7 via the CLI.
strantalis/agent-skills
-
feature-file
Manage features.yml for tracking requirements and progress; use proactively ONLY when features.yml already exists, or invoke manually to create one; complements TodoWrite for persistent project state.
Chemiseblanc/ai
-
waterfall-development
Enforces strict waterfall development workflow with phase gates. Use when (1) features.yml exists in project root, (2) user asks to implement/develop/build a feature, (3) user explicitly requests waterfall workflow. Creates features.yml if missing when invoked.
Chemiseblanc/ai
-
git-commit
Guide for breaking changes into logical, atomic commits using interactive staging. Use when committing changes that span multiple concerns, when needing to stage parts of files (hunks), when asked to create well-organized commit history, or when changes should be split into multiple commits.
Chemiseblanc/ai
-
software-architecture
Document software architecture using ARCHITECTURE.md and docs/*.md files with Mermaid diagrams. Use proactively when ARCHITECTURE.md exists in project root, or invoke to create initial architecture documentation. Covers system design, data flows, component relationships, and code organization with references to key entry points and abstractions.
Chemiseblanc/ai
-
commit-message
Format git commit messages combining Conventional Commits summary lines with Linux kernel-style bodies. Use when writing, reviewing, or formatting commit messages.
Chemiseblanc/ai
-
structured-logging
Guide for writing effective log messages using wide events / canonical log lines. Use when writing logging code, adding instrumentation, improving observability, or reviewing log statements. Teaches high-cardinality, high-dimensionality structured logging that enables debugging.
Chemiseblanc/ai
-
tlaplus-modeling
Model and reason about concurrent or distributed systems with TLA+ and PlusCal. Use when: designing multithreaded or distributed behavior before code exists, deriving invariants from an informal design, writing TLA+ specs, creating PlusCal algorithms, model checking with TLC, organizing multi-module specifications, debugging verification failures, or reducing state space. Covers informal concurrency design, MCP tool usage, PlusCal preferred syntax (call/await over goto), TLA+ module organization, and state-space optimization.
Chemiseblanc/ai
-
formal-verification
OPT-IN workflow for involved formal-verification planning. Use only when: the user explicitly asks for formal verification, this skill is referenced by workspace instructions, or the task explicitly calls for structuring a full formal-verification effort across models, refinement steps, and implementation-level proof obligations.
Chemiseblanc/ai
-
alloy-modeling
Model and analyze relational systems with Alloy. Use when: designing object graphs, authorization rules, topology constraints, schemas, ownership relations, or other structure-heavy systems; writing Alloy signatures, relations, facts, predicates, assertions, and scope-bounded checks; debugging counterexample instances; or deciding what should be abstracted into a bounded relational model.
Chemiseblanc/ai