← all publishers

jordanbyron

@jordanbyron source repo

Report this profile Claim this profile

• 4 skills
• 0 followers
• 10 hours ago last updated

1. ▌
   Babysit · jordanbyron

   Watch a remote pull/merge request for new review comments and CI failures, and keep resolving them until it settles.
   0 installs
2. ▌
   Rspec Test Prof · jordanbyron bundle

   Use when writing, reviewing, or improving RSpec tests in a Rails app. Triggers on writing new specs, adding test coverage, reviewing test code for quality, dealing with slow tests, setting up test infrastructure, or any question about RSpec best practices. Use this skill whenever the user is working with RSpec tests, even if they don't mention TestProf or performance — the patterns here produce better tests regardless.
   0 installs
3. ▌
   Domain Modeling · jordanbyron bundle

   Use when designing models, planning features, structuring controllers, or making architectural decisions in a Rails app. Triggers on questions like "how should I model X", "where does this logic go", "should I make a service object", adding new resources, or restructuring existing domain logic. Use this skill whenever the user is thinking about where behavior lives in their app.
   0 installs
4. ▌
   Philosophy Of Software Design · jordanbyron bundle

   Use this skill any time the user is shaping code structure rather than fixing or explaining it. Trigger on phrases like "I'm about to build...", "how should I structure...", "should I split/combine...", "one class or several...", "designing an API/interface/module/service/pipeline", "writing interface docs before I implement", "refactoring to make it cleaner", "this feels off", or reviewing code for too many methods, awkward boundaries, leaky abstractions, or shallow wrappers. The signal is *structural judgment about code* — choosing what goes where, what an interface exposes, how responsibilities divide across classes/modules/methods. Trigger even when the word "design" is absent and the phrasing is casual or embedded in a coding task ("before I start coding, how should I organize X"). Skip for: pure debugging, stack traces, lint/syntax/typo fixes, language or concept explanations, and non-code design like UI mockups, DB schemas, or infra diagrams.
   0 installs