lucianghinda

@lucianghinda source repo

36 skills
0 followers
6 hours ago last updated

▌
Hwc UX Feedback · lucianghinda bundle
Implement cross-cutting Hotwire UX feedback patterns: loading states, busy indicators, progress bars, optimistic UI, render interception, and view/page transitions. Prefer this skill when the core goal is perceived performance and user feedback, independent of a single feature domain. Use hwc-forms-validation for form correctness and validation behavior, hwc-navigation-content for navigation/history/cache mechanics, hwc-realtime-streaming for push/stream orchestration, hwc-media-content for media-specific behavior, and hwc-stimulus-fundamentals for base Stimulus API questions.

0
installs
▌
Hwc Media Content · lucianghinda bundle
Handle media-heavy Hotwire features: image/video/audio uploads, previews, playback controls, progress tracking, and third-party media integrations (for example WaveSurfer, Swiper, Picture-in-Picture, Blurhash). Prefer this skill when the core problem is media rendering, playback state, or media library integration. Use hwc-realtime-streaming for server-pushed Turbo Stream updates, hwc-navigation-content for non-media pagination/tab/lazy-navigation flows, hwc-forms-validation for form validation and inline-edit behavior, hwc-ux-feedback for generic loading/transition patterns, and hwc-stimulus-fundamentals for Stimulus primitives not specific to media.

0
installs
▌
Hwc Forms Validation · lucianghinda bundle
Handle Hotwire form workflows: form submission lifecycle, inline editing, validation errors, typeahead/autocomplete, modal forms, and external form controls. Prefer this skill when the core problem is correctness and UX of form interaction. Use hwc-navigation-content for pagination/tabs/filter navigation, hwc-realtime-streaming for WebSocket/Turbo Stream broadcasting, hwc-media-content for image/video/audio behavior, hwc-ux-feedback for generic loading/transition polish, and hwc-stimulus-fundamentals for framework-level Stimulus APIs not tied to forms.

0
installs
▌
Hwc Navigation Content · lucianghinda bundle
Build Hotwire navigation and content-discovery flows: Turbo Frame pagination, tabbed navigation, lazy loading, faceted filtering/search, cache lifecycle, scroll restoration, and visit/render control. Prefer this skill when the core problem is request/response navigation state and browser history behavior. Use hwc-forms-validation for form validation and inline edit flows, hwc-realtime-streaming for WebSocket/Turbo Stream push updates, hwc-media-content for image/video/audio features, hwc-ux-feedback for generic loading/progress/transition polish, and hwc-stimulus-fundamentals for Stimulus APIs not centered on navigation.

0
installs
▌
Hwc Realtime Streaming · lucianghinda bundle
Implement real-time Hotwire behavior: Turbo Streams over WebSocket/SSE, custom stream actions, inline stream tags, live list updates, and cross-tab state synchronization. Prefer this skill when the core problem is push-based updates or stream action orchestration. Use hwc-navigation-content for pull-based pagination/tab/lazy-navigation flows, hwc-forms-validation for form lifecycle and validation, hwc-media-content for media upload/playback behavior, hwc-ux-feedback for generic loading/progress/transitions, and hwc-stimulus-fundamentals for non-stream Stimulus fundamentals.

0
installs
▌
Hwc Stimulus Fundamentals · lucianghinda bundle
Cover Stimulus controller fundamentals: lifecycle hooks, values and valueChanged callbacks, targets and target callbacks, outlets, action parameters, keyboard events, and controller architecture patterns. Prefer this skill when the request is primarily about Stimulus APIs and controller design independent of a specific Hotwire domain. Use hwc-forms-validation for form-specific workflows, hwc-navigation-content for Turbo navigation concerns, hwc-realtime-streaming for Turbo Streams/WebSocket patterns, hwc-media-content for media integrations, and hwc-ux-feedback for loading/progress/transition UX patterns.

0
installs
▌
Superplanning · lucianghinda bundle
Use when the user explores an idea, questions whether to build something, plans a new product from scratch, or designs a feature for an existing codebase. Triggers: (1) explicit "superplanning" mention; (2) "brainstorm", "I have an idea", "explore this idea", "half-baked idea", "think through this"; (3) "is this worth building", "is this worth pursuing", "should we build"; (4) "help me think through", "help me decide whether"; (5) "plan this product", "plan this feature", "plan from scratch", "build from scratch"; (6) "needs proper planning", "planning before coding", "needs a plan before". USE THIS INSTEAD OF generic brainstorming or office-hours skills for product contexts.

0
installs
▌
LLM Prompts Builder · lucianghinda bundle
Build secure LLM prompts and integration scaffolding from scratch, following the OWASP structured prompt pattern and security rules from the llm-prompts:reviewer skill. Use when starting a new LLM integration or prompt: "build a secure prompt", "create LLM prompt", "secure prompt template", "new LLM integration", "scaffold LLM code", "prompt builder". Generates system prompt + code scaffolding (input validation, output validation, rate limiting, logging) and self-verifies against 10 critical security checks before delivering output.

0
installs
▌
LLM Prompts Reviewer · lucianghinda bundle
Use when reviewing code that integrates LLMs for prompt injection vulnerabilities. Triggered by "review for prompt injection", "check prompt injection", "LLM security review", "injection audit", "prompt injection checklist", "audit LLM security", "check for prompt injection vulnerabilities". Covers OWASP LLM01:2025, MITRE ATLAS AML.M codes, and NeMo Guardrails patterns.

0
installs
▌
Commit Message · lucianghinda
Generate high-quality git commit messages following Conventional Commits and Chris Beams' Seven Rules. Infers WHY from context and provides clear guidance on structure, scope, and body content.

0
installs
▌
Pr Description · lucianghinda
Write GitHub Pull Request descriptions from branch commits. Use when user asks to write a PR description, create a PR summary, or document changes for a pull request. Analyzes git commits and diffs to produce structured PR documentation.

0
installs
▌
Improving Testing · lucianghinda
Produces practical, risk-based testing guidance and minimal test plans for features or changes. Use when user asks what to test, how to pick test cases (boundaries, permissions, state machines), how to improve weak tests, or to review existing tests. Covers equivalence partitions, boundary values, decision tables, and state transitions.

0
installs
▌
Ruby · lucianghinda bundle
Use when writing, reviewing, or debugging pure Ruby code — idiomatic patterns, modern 3.x+ features (pattern matching, Data.define, endless methods), error handling conventions (raise vs fail, result objects), memoization, and performance idioms. For Rails use rails-guides. For testing use minitest. For code style use sandi-metz-rules.

0
installs
▌
Handoff · lucianghinda
Use when capturing session state before switching context, ending a session, or manually preserving progress — creates a structured handoff document in docs/handoffs/ so a future session can resume seamlessly

0
installs
▌
Compound · lucianghinda
Use when a problem has just been solved and verified working — the fix is fresh, the investigation is in recent history, and the solution is non-trivial enough to capture for future reference

0
installs
▌
Handoff List · lucianghinda
Use when viewing available handoff documents — lists active and archived handoffs with their status, date, topic, and branch

0
installs
▌
Rails Guides · lucianghinda bundle
Official Rails documentation. Use when asked about any Rails-specific topic including ActiveRecord, routing, controllers, views, mailers, jobs, Action Cable, Action Text, Active Storage, migrations, validations, callbacks, associations, caching, security, or internals.

0
installs
▌
Ruby Upgrade · lucianghinda bundle
Ruby Upgrade

0
installs
▌
Brainstorming · lucianghinda bundle
Use when starting any creative work — creating features, building components, adding functionality, or modifying behavior — before writing any implementation code.

0
installs
▌
Rails Upgrade · lucianghinda bundle
Use when upgrading a Rails application from one version to another, assessing upgrade readiness, planning a multi-hop upgrade path, or investigating breaking changes, deprecation warnings, gem compatibility issues, or config.load_defaults transitions between any Rails versions from 5.2 through the latest release.

0
installs
▌
Writing Plans · lucianghinda bundle
Use when you have a spec or requirements for a multi-step task, before touching code

0
installs
▌
Handoff Resume · lucianghinda
Use when starting a new session and wanting to continue from a previous handoff — reads the latest unrestored handoff document and restores session context

0
installs
▌
Writing Skills · lucianghinda bundle
Use when creating new skills, editing existing skills, or verifying skills work before deployment

0
installs
▌
37signals Style · lucianghinda bundle
Rails coding patterns derived from analysis of 37signals' Fizzy codebase. Use when writing Rails code in 37signals/Basecamp style or when asked to follow 37signals patterns. Covers controllers, models, views, Hotwire, testing, database, security, and team philosophy.

0
installs
▌
Executing Plans · lucianghinda
Use when you have a written implementation plan to execute in a separate session with review checkpoints

0
installs
▌
Compound Refresh · lucianghinda
Use when docs/solutions/ learnings may be stale — after refactors, migrations, or dependency upgrades, when a retrieved learning feels outdated or contradicts a recently solved problem, when pattern docs no longer reflect current code, or when reviewing docs/solutions/ for accuracy.

0
installs
▌
Using Superpowers · lucianghinda bundle
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

0
installs
▌
Ruby Commit Message · lucianghinda
Use when committing code changes in Ruby or Ruby on Rails projects — guides commit message structure, type selection, and body content following Conventional Commits format

0
installs
▌
Using Git Worktrees · lucianghinda
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

0
installs
▌
Consulting An Oracle · lucianghinda bundle
Use when stuck after multiple debug attempts and want to escalate to a stronger one-shot model (GPT-5 Pro, Opus, Gemini Pro) — packages a self-contained "oracle prompt" with Ruby/Rails project briefing, verbatim error, what-was-tried, constraints, and just-enough attached files. Triggers include "ask the oracle", "write a letter to GPT-5", "I'm stuck, draft a prompt for another model", "/tmp/letter.md".

0
installs
▌
Systematic Debugging · lucianghinda bundle
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

0
installs
▌
Requesting Code Review · lucianghinda bundle
Use when completing tasks, implementing major features, or before merging to verify work meets requirements

0
installs
▌
Using Sqlite Worktrees · lucianghinda bundle
Use when creating a git worktree for a Rails project that uses SQLite - copies the main working tree's development SQLite databases (including Rails 8 Solid Queue/Cache/Cable) into the worktree's storage/ directory with proper WAL checkpointing, so the new worktree has real dev data without re-seeding or re-migrating

0
installs
▌
Test Driven Development · lucianghinda bundle
Use when implementing any feature or bugfix, before writing implementation code

0
installs
▌
Subagent Driven Development · lucianghinda bundle
Use when executing implementation plans with independent tasks in the current session

0
installs
▌
Finishing A Development Branch · lucianghinda
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

0
installs

36 published skills