Skill Creator

Ramblurr

44 published skills · 0 GitHub stars across the catalog. View on GitHub ↗

clojure-test-check

Ramblurr's avatarfrom Ramblurr

Property-based testing with clojure.test.check. Use when writing generative tests, creating custom generators, or debugging shrinking behavior. Triggers on test.check imports, prop/for-all, gen/* usage, or questions about property-based testing in Clojure.

clojure-trove

Ramblurr's avatarfrom Ramblurr

Trove is a minimal logging facade for Clojure/Script supporting both traditional and structured logging. Use when writing libraries that need logging without forcing a backend choice, or when you need rich data-oriented logging with flexible filtering.

executing-plans

Ramblurr's avatarfrom Ramblurr

Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches

extra-reference-material

Ramblurr's avatarfrom Ramblurr

Manage offline reference material in the `extra/` directory. Use when needing external documentation, library source code, screenshots, PDFs, or API specs. ALWAYS check `extra/` before web searches. HALT and ask the human when required material is missing - do NOT fall back to WebFetch/WebSearch.

finishing-a-development-branch

Ramblurr's avatarfrom Ramblurr

Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.

github-actions-versions

Ramblurr's avatarfrom Ramblurr

Use when writing or updating GitHub Actions workflow files (.github/workflows/*.yml) - provides latest version tags for official and popular third-party actions to avoid using outdated versions

landing-the-plane

Ramblurr's avatarfrom Ramblurr

Checklist for finishing work, pushing a branch, and opening a ready-for-review PR with tests and tracker updates. Use when asked to "land the plane"

planning-documents

Ramblurr's avatarfrom Ramblurr

Naming conventions for planning documents in prompts/. Use when creating plans, PRDs, research reports, idea capture or other workflow documents. Triggers on (1) creating new planning documents, (2) naming PRDs or research reports, (3) questions about document organization in prompts/.

receiving-code-review

Ramblurr's avatarfrom Ramblurr

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

research

Ramblurr's avatarfrom Ramblurr

Pre-implementation research for design, architecture, and impact analysis. Use during brainstorming, architectural design, or before implementation to understand dependencies and integration points. Triggers on (1) designing or architecting a feature, (2) brainstorming implementation approaches, (3) analyzing impact of proposed changes, (4) exploring reference materials in extra/, (5) creating research reports before planning.

root-cause-tracing

Ramblurr's avatarfrom Ramblurr

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

skill-creator

Ramblurr's avatarfrom Ramblurr

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

test-driven-development-tdd

Ramblurr's avatarfrom Ramblurr

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

testing-anti-patterns

Ramblurr's avatarfrom Ramblurr

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

using-git-worktrees

Ramblurr's avatarfrom Ramblurr

Use this whenever you need to create an isolated workspace.

writing-clearly-and-concisely

Ramblurr's avatarfrom Ramblurr

Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.

writing-plans

Ramblurr's avatarfrom Ramblurr

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

clojure-guardrails

Ramblurr's avatarfrom Ramblurr

Reference for Guardrails library with Malli in Clojure. Use when working with `>defn`, `>defn-`, `>def`, `>fdef` macros, gspec syntax, or function validation. Triggers on guardrails imports, `com.fulcrologic.guardrails.malli`, function specs with `=>` operator, or questions about runtime validation in Clojure.

tmux

Ramblurr's avatarfrom Ramblurr

Remote control tmux sessions using tmux-buddy (tmuxb) for interactive CLIs (python, gdb, emacs, vim, etc.) by sending keystrokes and scraping pane output.

coding-agents

Ramblurr's avatarfrom Ramblurr

Spawn and control external coding agents (Claude Code, Codex, OpenCode, Pi) for delegating tasks. Use when (1) user asks to run another coding agent, (2) delegating subtasks to a different AI tool, (3) running multiple agents in parallel on separate issues, (4) spawning an agent in an isolated environment or worktree, (5) user mentions "codex", "opencode", "pi agent", or running "another claude".