bromanko
@bromanko
Public Skills
elm-security-review
by bromanko
This skill should be used when the user asks for "security review", "vulnerability scan", "audit Elm security", "security audit", "find vulnerabilities", "check for security issues", or wants a deep security analysis of Elm code including port safety, JSON decoder validation, and XSS prevention.
typescript-security-review
by bromanko
This skill should be used when the user asks for "security review", "vulnerability scan", "audit TypeScript security", "security audit", "find vulnerabilities", "check for security issues", or wants a deep security analysis of TypeScript code including input validation, auth boundaries, and dependency risks.
fsharp-security-review
by bromanko
This skill should be used when the user asks for "security review", "vulnerability scan", "audit F# security", "security audit", "find vulnerabilities", "check for security issues", or wants a deep security analysis of F# code including input validation, .NET interop safety, and dependency concerns.
elm-review
by bromanko
This skill should be used when the user asks to "review Elm", "full Elm review", "review all Elm", "comprehensive Elm review", or wants a complete review covering code quality, security, performance, and testing for Elm code.
exec-plan
by bromanko
Write or implement execution plans (ExecPlans) — thorough, self-contained design documents that guide a coding agent through complex features or significant refactors. Use this skill when the user asks to "write a plan", "create an exec plan", "make an ExecPlan", "plan this feature", "design this refactor", "write a design doc for implementation", or when they ask to "implement a plan", "execute this plan", "follow the plan", "continue the plan", "pick up where the plan left off". Also trigger when the user mentions "ExecPlan", "execution plan", or references a PLAN.md or similar planning document. This skill covers both authoring plans and executing them.
fsharp-code-review
by bromanko
This skill should be used when the user asks to "review F# code", "fsharp code quality", "F# idioms check", "review my F#", "check code quality", or wants feedback on F# code patterns, idioms, Result handling, or module organization.
fp-ts
by bromanko
This skill should be used when the user asks to "write idiomatic fp-ts", "refactor to fp-ts", "use Option/Either/Task/TaskEither", "compose with pipe/flow", "handle errors with fp-ts", "convert to functional style", "use fp-ts patterns", or mentions fp-ts types, monads, or functional composition in TypeScript.
fsharp-performance-review
by bromanko
This skill should be used when the user asks to "review performance", "optimize F#", ".NET performance", "performance audit", "find bottlenecks", "improve efficiency", or wants analysis of F# code performance focusing on .NET runtime patterns, async architecture, and data structure choices.
gleam-code-review
by bromanko
This skill should be used when the user asks to "review gleam code", "code quality review", "gleam idioms check", "review my gleam", "check code quality", or wants feedback on Gleam code patterns, idioms, Result handling, or module organization.
gleam-performance-review
by bromanko
This skill should be used when the user asks to "review performance", "optimize gleam", "BEAM performance", "performance audit", "find bottlenecks", "improve efficiency", or wants analysis of Gleam code performance focusing on BEAM runtime patterns, process architecture, and data structure choices.
ears-requirements
by bromanko
Generate EARS (Easy Approach to Requirements Syntax) specifications from plan files, design documents, user stories, or existing codebases. Use this skill whenever the user wants to write software requirements, create specifications, extract requirements from code, convert informal requirements to structured format, prepare requirements for verification/testing, or mentions "EARS", "requirements syntax", "shall statements", "system requirements", or "specifications". Also trigger when the user asks to make requirements testable, reduce ambiguity in specs, or prepare verification criteria from a plan or codebase.
typescript-test-review
by bromanko
This skill should be used when the user asks for "test review", "test coverage", "improve TypeScript tests", "review tests", "test quality", "testing audit", or wants analysis of TypeScript test suites for coverage gaps, edge cases, and testing best practices.
elm-test-review
by bromanko
This skill should be used when the user asks for "test review", "test coverage", "improve Elm tests", "review tests", "test quality", "testing audit", or wants analysis of Elm test suites for coverage gaps, edge cases, and testing best practices.
fsharp-test-review
by bromanko
This skill should be used when the user asks for "test review", "test coverage", "improve F# tests", "review tests", "test quality", "testing audit", or wants analysis of F# test suites for coverage gaps, edge cases, and testing best practices.
typescript-code-review
by bromanko
This skill should be used when the user asks to "review TypeScript code", "typescript code quality", "TypeScript idioms check", "review my TypeScript", "check code quality", or wants feedback on TypeScript patterns, typing strategy, and module organization.
elm-code-review
by bromanko
This skill should be used when the user asks to "review Elm code", "Elm code quality", "Elm idioms check", "review my Elm", "check code quality", or wants feedback on Elm code patterns, idioms, Msg/Model design, or module organization.
gleam-test-review
by bromanko
This skill should be used when the user asks for "test review", "test coverage", "improve gleam tests", "review tests", "test quality", "testing audit", or wants analysis of Gleam test suites for coverage gaps, edge cases, and testing best practices.
elm-performance-review
by bromanko
This skill should be used when the user asks to "review performance", "optimize Elm", "Elm performance", "performance audit", "find bottlenecks", "improve efficiency", or wants analysis of Elm code performance focusing on virtual DOM efficiency, rendering patterns, and data structure choices.
exec-plan-review
by bromanko
Review execution plans (ExecPlans) for completeness, clarity, and implementability. Use this skill when the user asks to "review a plan", "review this exec plan", "critique this plan", "is this plan good enough", "check this plan", "audit this plan", "review my PLAN.md", or wants feedback on whether an execution plan is ready for a developer or coding agent to implement. Also trigger when the user mentions "plan review", "plan quality", or asks if a plan is "implementable" or "self-contained enough".
typescript-performance-review
by bromanko
This skill should be used when the user asks to "review performance", "optimize TypeScript", "TypeScript performance", "performance audit", "find bottlenecks", "improve efficiency", or wants analysis of TypeScript code performance focusing on runtime hotspots, rendering efficiency, and data handling.
fsharp-review
by bromanko
This skill should be used when the user asks to "review F#", "full F# review", "review all F#", "comprehensive F# review", "review fsharp", or wants a complete review covering code quality, security, performance, and testing for F# code.
word-explorer
by bromanko
This skill should be used when the user provides a word and requests an exploration of its meaning, etymology, usage, and literary examples. The skill produces comprehensive, engaging word profiles that combine dictionary definitions, pronunciations, literary quotations, and practical usage guidance.
typescript-review
by bromanko
This skill should be used when the user asks to "review TypeScript", "full TypeScript review", "review all TypeScript", "comprehensive TypeScript review", or wants a complete review covering code quality, security, performance, and testing for TypeScript code.
gleam-review
by bromanko
This skill should be used when the user asks to "review Gleam", "full Gleam review", "review all Gleam", "comprehensive Gleam review", or wants a complete review covering code quality, security, performance, and testing for Gleam code.
jj-commit
by bromanko
Analyze jj status and create well-structured, logical commits with descriptive messages. Use when the user wants to commit changes in a jujutsu repository, create atomic commits, or organize working copy changes into meaningful commit groups.