← all publishers

delzarsolutionsllc

@delzarsolutionsllc source repo

Report this profile Claim this profile

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

1. ▌
   Tdd · delzarsolutionsllc

   Red, green, refactor. Write the failing test that pins the contract, then the smallest pass. Use when the user asks to TDD.
   0 installs
2. ▌
   Debugging · delzarsolutionsllc

   Reproduce first, then isolate. Turn a failing run into a root cause and a minimal fix. Use when the user asks to debug this.
   0 installs
3. ▌
   API Design · delzarsolutionsllc

   Shape HTTP and RPC so clients can evolve. Idempotency, errors, pagination, compatibility. Use when the user asks to API design.
   0 installs
4. ▌
   Code Review · delzarsolutionsllc

   Read a diff like a staff engineer: correctness, security, tests, and regression risk before merge. Use when the user asks to code review.
   0 installs
5. ▌
   Frontend UX · delzarsolutionsllc

   Make the interface usable on a phone and a laptop: hierarchy, empty states, and no dead clicks. Use when the user asks to UX review.
   0 installs
6. ▌
   Performance · delzarsolutionsllc

   Measure before you change. Find the real hot path, then cut latency or allocations there. Use when the user asks to this is slow.
   0 installs
7. ▌
   Refactoring · delzarsolutionsllc

   Change structure without changing behavior. Keep the diff small and the tests green. Use when the user asks to refactor.
   0 installs
8. ▌
   Git Workflow · delzarsolutionsllc

   Branch, commit, and PR with a history someone can actually bisect six months later. Use when the user asks to git.
   0 installs
9. ▌
   Spec Writing · delzarsolutionsllc

   Turn a vague ask into a spec an agent can build against: scope, invariants, and done-when. Use when the user asks to write a spec.
   0 installs
10. ▌
    Documentation · delzarsolutionsllc

    Write the doc the next person will search for: how to run it, how it fails, and where the source of truth lives. Use when the user asks to write the README.
    0 installs
11. ▌
    Pr Description · delzarsolutionsllc

    Write the PR a reviewer wants: intent, risk, test plan, and what you deliberately did not do. Use when the user asks to write the PR.
    0 installs
12. ▌
    Security Audit · delzarsolutionsllc

    Hunt OWASP-class bugs in the code you can actually reach: injection, authz, secrets, SSRF. Use when the user asks to security audit.
    0 installs
13. ▌
    Database Schema · delzarsolutionsllc

    Model the data so the queries you will actually run stay honest as the product grows. Use when the user asks to schema.
    0 installs
14. ▌
    Test Generation · delzarsolutionsllc

    Cover the behavior that can actually break: edges, errors, and the regression that bit you. Use when the user asks to write tests.
    0 installs
15. ▌
    Incident Response · delzarsolutionsllc

    Stabilize first. Then find the blast radius, the trigger, and the fix that will not make it worse. Use when the user asks to incident.
    0 installs
16. ▌
    Repo Health Check · delzarsolutionsllc

    Map a new codebase fast: layout, how to run it, the risky bits, the smallest safe first change. Use when the user asks to new repo.
    0 installs
17. ▌
    Migration Planning · delzarsolutionsllc

    Move data or systems without a night-of surprise. Dual-write, backfill, cutover, rollback. Use when the user asks to migration plan.
    0 installs
18. ▌
    Architecture Review · delzarsolutionsllc

    Judge module boundaries, data flow, and failure modes before the system calcifies. Use when the user asks to architecture review.
    0 installs