By rafaeelricco
Run a guided end-to-end test of a running web app after a feature is finished or any time you need to validate real behavior in a browser. Use whenever the user finishes building or changing a feature, or asks to test the app E2E, smoke-test it, click through the UI, verify a flow works end-to-end, check the happy path, or confirm a change works in a real browser — even if they don't say "E2E". The skill first discovers how the app actually works from its codebase and the conversation, then interviews for where the app is running, whether to drive it with Claude Preview or Claude in Chrome, and the login credentials, then walks the app toward the goal and reports pass/fail with screenshots, console errors, and failed network calls.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Domain-driven Neovim and Windows Terminal configuration focused on reproducible workflows across macOS and Windows.
lazy.nvim loads plugins by domain (AI, completion, LSP, UI, Git) for predictable startup and maintenance.PATH (required by the rewritten nvim-treesitter on the main branch)tree-sitter CLI 0.26+ — required at runtime to compile parsers; nvim-treesitter no longer bundles itPATH (Xcode Command Line Tools on macOS: xcode-select --install; build-essential on Linux; MSVC Build Tools on Windows) — used by tree-sitter to build parserstree-sitter CLI# macOS (Homebrew)
brew install tree-sitter-cli
# Linux / generic (requires npm)
npm install -g tree-sitter-cli
# Alternative: cargo
cargo install tree-sitter-cli
Verify with tree-sitter --version — nvim's :checkhealth nvim-treesitter must report it as ✅ before parsers will compile.
git clone [email protected]:rafaeelricco/dotfiles.git
cd dotfiles
# macOS / Linux
ln -s "$(pwd)/nvim/init.lua" "$HOME/.config/nvim/init.lua"
ln -s "$(pwd)/nvim/lua" "$HOME/.config/nvim/lua"
# Optional: keep lazy.nvim lock file in sync if you generate one
# ln -s "$(pwd)/nvim/lazy-lock.json" "$HOME/.config/nvim/lazy-lock.json"
Link the versioned skills directory so Claude Code resolves it via ~/.claude/skills:
# macOS / Linux
mkdir -p "$HOME/.claude"
ln -s "$(pwd)/.claude/skills" "$HOME/.claude/skills"
On Windows, double-click scripts/windows/setup-claude-skills.bat (or right-click → "Run as administrator"). It self-elevates via UAC and creates the symlink. If ~/.claude/skills already exists as a non-empty real directory, the script aborts so you can move its contents into ./.claude/skills/ first.
The repo also publishes each .claude/skills/<skill> as an individual Claude Code plugin. Add the marketplace once:
claude plugin marketplace add rafaeelricco/dotfiles
Then install only the skills you want:
claude plugin install create-pr@ricco-skills
claude plugin install code-pattern@ricco-skills
claude plugin install prompt-master@ricco-skills
claude plugin install gh-issue-drafter@ricco-skills
To install several skills, run one install command per skill. After pulling marketplace updates, refresh the catalog:
claude plugin marketplace update ricco-skills
Marketplace plugin files under plugins/ are generated from .claude/skills/. Regenerate them after editing skills:
python3 scripts/sync-claude-plugin-marketplace.py
After editing a skill:
.claude/skills/<skill>/...python3 scripts/sync-claude-plugin-marketplace.py.claude/skills/, plugins/, and .claude-plugin/claude plugin marketplace update ricco-skills
claude plugin update <skill>@ricco-skills
Claude Code plugins do not load CLAUDE.md as global context. To install the global Claude instructions by command, copy them to ~/.claude/CLAUDE.md with an automatic backup:
curl -fsSL https://raw.githubusercontent.com/rafaeelricco/dotfiles/main/scripts/install-claude-md.py | python3
From a local clone, run:
python3 scripts/install-claude-md.py
Reuse the same .claude/skills/ directory in the Codex CLI. Codex stores user skills under ~/.codex/skills/, but its bundled skills live in ~/.codex/skills/.system/, so we link per skill instead of the whole directory:
# macOS / Linux
mkdir -p "$HOME/.codex/skills"
for dir in .claude/skills/*/; do
name=$(basename "$dir")
ln -sfn "$(pwd)/$dir" "$HOME/.codex/skills/$name"
done
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 claimnpx claudepluginhub rafaeelricco/dotfiles --plugin e2e-testKeep a GitHub pull request merge-ready by triaging merge conflicts, unresolved review feedback, actionable PR comments, and CI failures in a loop. Use when the user asks to babysit this PR, keep this PR merge-ready, triage PR comments and CI, resolve actionable review feedback, watch CI until mergeable, or get a PR ready to merge.
Create and open GitHub pull requests from local repository changes. Use this skill when the user asks to create PR, open PR, abrir PR, criar pull request, ship this branch, ready for review, publish local changes as a pull request, or invokes /create-pr. The skill inspects branch state and diffs, asks before branch, staging, commit, push, base branch, assignee, or ready/draft decisions, requires pr-generate-description before PR creation, pushes with git, and creates the PR with gh.
Draft structured GitHub issues from loose notes, review comments, or partially written issue text. Use when you need to create, rewrite, or standardize a GitHub issue with a separate title and a concise body using Situation, Direction, Acceptance Criteria, Validation, and optional References. Trigger this skill for requests such as create an issue, structure this issue, turn notes into an issue, write acceptance criteria, write validation steps, or make an issue body clearer and objectively verifiable.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Apply this project's TypeScript and React conventions whenever implementing, refactoring, polishing, or reviewing any component, hook, page, form, table, store, service, or data flow — consult it BEFORE writing or editing such code, even when the task looks routine and the user never says "conventions" or "patterns". It owns the local standards for typing, domain modeling, async and UI state, forms and API calls, tables, styling, and component structure, and how to turn them into review findings. Reinforcing signals: Maybe, Result, RemoteData, Future, ts-pattern, discriminated unions, decoders/schemas, useForm, FormInput, DataTable, ColumnDef, cn()/cva(), named prop types, container/presentational split, and read-after-write projection delays.
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.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Create new skills, improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, or benchmark skill performance with variance analysis.
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development