paradauxio/paradaux
Personal engineering workflows for intake, verification, debugging, and pull requests.
Create a GitHub pull request with Why, How, Diagram, and Screenshots sections, uploading diagram images and real application screenshots through the gh CLI.
Diagnose failed login, session, or authorization behavior in applications using Keycloak, including mismatches in app configuration or Infisical-managed settings.
Resolve failing CI checks or actionable review feedback on a GitHub pull request, then verify the affected checks and report remaining blockers.
Use the project's .context/ directory for local scratch scripts, notes, intermediate files, and other temporary task artifacts whenever work needs scratch storage.
Begin engineering work from a plain-text request, ticket title, or Tasklie or GitHub issue reference by resolving context, scope, and verification before proceeding.
Investigate and fix unexplained bugs, failing or flaky tests, build failures, performance regressions, and cross-service errors using reproducible evidence and discriminating experiments. Use for diagnosis or repair, preserving the user's requested scope.
Verify a changed web application or reproduce a UI bug by exercising the affected user journey in a browser and checking observable state.