← all publishers

jrudman25

@jrudman25 source repo

Report this profile Claim this profile

• 8 skills
• 0 followers
• 3 hours ago last updated

1. ▌
   Taste · jrudman25

   Marketing-design specialist for creating or meaningfully changing the visual design of landing pages, portfolios, editorial pages, and other brand-heavy web surfaces, or when the user explicitly asks for stronger creative direction. Use with `frontend-design`; when modifying an existing surface, also use `redesign`. Do not use for dashboards, admin tools, dense product UI, bug fixes, copy or wiring changes that keep the current design, or nonvisual frontend work.
   0 installs
2. ▌
   Grill Me · jrudman25

   Stress-test a plan, decision, or idea through structured questioning. Use only when the user explicitly asks to be grilled, challenged, or interviewed about their reasoning.
   0 installs
3. ▌
   Redesign · jrudman25

   Redesign Workflow
   0 installs
4. ▌
   Find Skills · jrudman25

   Research, audit, compare, and recommend installable agent skills when the user explicitly asks to find a skill, recommend skills, compare skill options, extend agent capabilities, or decide whether a recurring workflow should become a skill. Do not invoke merely because an ordinary task could theoretically be handled by an installable skill.
   0 installs
5. ▌
   Update Docs · jrudman25

   Update relevant project documentation such as `README.md`, `AGENTS.md`, and `TODO.md` from verified repository state while preserving useful existing content. This skill is the canonical owner of `TODO.md` structure.
   0 installs
6. ▌
   Codebase Review · jrudman25

   Perform a thorough codebase review covering code quality, security vulnerabilities, performance, and architecture. Use this skill whenever the user asks to "review the codebase", "check the code", "audit the repo", "look for issues", "do a code review", or any similar request — even if phrased casually like "can you look over this?" For requests about launch, deployment, shipping, or production-readiness verdicts, use `production-ready` instead. Also trigger when the user asks about specific problem areas like "are there any security issues?" or "is the architecture solid?". If the user specifies a focus area, apply only the relevant lenses and note explicitly that the rest of the codebase was out of scope. Update or create TODO.md with unresolved findings, but ask before modifying application code or infrastructure. Output is a priority-ordered action list grouped by severity. Do not use for agent skill discovery, comparison, or auditing; use `find-skills` instead.
   0 installs
7. ▌
   Frontend Design · jrudman25

   Shared foundation for creating a new user-facing surface or making a meaningful change to visual hierarchy, layout, interaction design, accessibility-relevant presentation, or user-facing visual states. Pair with `taste` for marketing, landing, portfolio, or editorial surfaces; pair with `redesign` when materially redesigning an existing interface; use all three for an existing marketing surface. Do not invoke for small styling fixes, copy tweaks, single-property adjustments, or entirely nonvisual work such as data transformations, API clients, state logic, or build configuration.
   0 installs
8. ▌
   Production Ready · jrudman25

   Audit a web application for production readiness across correctness, security, privacy, data integrity, reliability, observability, performance, accessibility, public-site integrity, SEO, and operations. Use when the user asks whether an app is ready to ship, deploy, launch, or run in production. Update or create TODO.md with unresolved findings, but ask before modifying application code or infrastructure.
   0 installs