Skip to content

Instantly share code, notes, and snippets.

@ORESoftware
Last active May 16, 2026 20:06
Show Gist options
  • Select an option

  • Save ORESoftware/f311e97ee394961086e8c165822c159d to your computer and use it in GitHub Desktop.

Select an option

Save ORESoftware/f311e97ee394961086e8c165822c159d to your computer and use it in GitHub Desktop.
master task list

MASTER TASK LIST

GLOBAL RULES

  • DO NOT skip tasks.
  • Run tasks strictly in order unless blocked.
  • Commit frequently with meaningful commit messages.
  • Push frequently.
  • Ask for clarification only if truly blocked.
  • Preserve existing functionality.
  • Favor incremental safe changes.
  • Use TypeScript strictness whenever possible.
  • Add logging and observability where useful.
  • Avoid destructive migrations.
  • Test before merge.
  • Mobile responsiveness matters for all user-facing pages.
  • Add telemetry for failures, retries, pending states, and success states.
  • Ensure all long-running jobs are resumable/idempotent.

GIT / BRANCHING

git fetch origin
git merge origin/rw1-alex
  • Resolve merge conflicts carefully.
  • Preserve newer logic.
  • Avoid deleting existing working features.
  • Push after major milestones.

Task - make sure all webhooks are good

make sure we have the right webhooks to respond to emails from [email protected] and [email protected] and [email protected] etc - we have a webhook for [email protected] already, right? it ties into our gmail thread syncing - but when people respond to gmail threads we need to be notified so we can automatically respond etc etc.


task: MCP server

dancingdragons.cc should have it's own mcp endpoints - make sure they are built-out etc


DEV ENVIRONMENT

MOBILE RESPONSIVENESS

Audit ALL pages under:

  • (private)/u/
  • (private)/s/

Tasks:

  • fix overflow issues
  • fix broken flex/grid layouts
  • improve spacing
  • improve button sizing
  • improve responsive typography
  • verify forms work on mobile
  • verify modals work on mobile
  • verify tables scroll correctly
  • verify chat/thread views work on mobile
  • test iPhone + Android resolutions

ALEX AUTO APPLY SYSTEM

Core improvements

  • improve alex auto apply reliability
  • improve ATS detection
  • improve autofill behavior
  • improve retry logic
  • improve anti-duplication logic
  • improve job deduplication
  • improve session persistence
  • improve auth persistence
  • improve cookie reuse
  • improve captcha handling
  • improve application success rate
  • improve failure diagnostics

Telemetry / Metrics

Track:

  • total attempts
  • successful applies
  • failed applies
  • partial applies
  • pending applies
  • ATS detected
  • captcha encountered
  • auth failures
  • browser crashes
  • timeout failures
  • rate limiting
  • retries
  • average completion time

Throughput goals

  • target 500 leads/day
  • maximize successful applies/day
  • reduce manual intervention
  • reduce browser instability

LinkedIn

  • allow human user to manually input LinkedIn credentials/password when required
  • preserve authenticated sessions safely
  • improve LinkedIn stability
  • improve Easy Apply support

BROWSER AUTOMATION HARDENING

Massive randomized browser testing

Run randomized exploratory testing:

  • randomly select 30 tests
  • max 10 tests per folder
  • run 3 cycles minimum
  • click all visible buttons/links
  • aggressively probe edge cases
  • test navigation transitions
  • test modal open/close
  • test auth/session expiry
  • test refresh behavior
  • test websocket reconnects
  • test mobile viewport behavior

Extended run:

  • run 50 tests in 3 rounds
  • identify flaky tests
  • identify intermittent failures
  • identify race conditions
  • identify hydration mismatches
  • identify stale state bugs

Browser reliability

  • reduce playwright/puppeteer crashes
  • improve retry handling
  • improve timeout handling
  • improve page load detection
  • improve selector stability
  • improve browser cleanup
  • improve zombie-process cleanup

CHAT / THREAD SYSTEM

  • improve websocket reliability
  • improve reconnect behavior
  • improve message ordering
  • improve optimistic updates
  • improve thread loading
  • improve infinite scroll behavior
  • improve attachment handling
  • improve typing indicators
  • improve unread state tracking
  • improve notification behavior

DATABASE / BACKEND

Postgres safety

  • use transactions for migrations
  • avoid destructive changes
  • add IF EXISTS where possible
  • add idempotency protections
  • add FK prechecks
  • add logging/notices
  • preserve existing data

Ledger / financial integrity

  • maintain immutable ledger semantics
  • ensure transaction id uniqueness
  • ensure reconciliation safety
  • ensure concurrency safety
  • ensure refund correctness
  • ensure chargeback correctness
  • improve auditability

Locking / concurrency

  • improve advisory lock usage
  • reduce deadlock potential
  • improve transaction isolation handling
  • improve queue reliability
  • improve retry semantics

SEARCH / INDEXING

  • improve text search relevance
  • improve vector search correlation
  • improve hybrid search ranking
  • improve indexing performance
  • improve deduplication
  • improve incremental indexing
  • improve stale-index cleanup

NEXT.JS / VERCEL / INFRA

Deployment reliability

  • improve server action reliability
  • reduce stale deploy issues
  • improve cache invalidation
  • improve edge/runtime compatibility
  • improve lambda cold-start behavior
  • improve observability

Caching

  • improve unstable-cache usage
  • improve Redis/cache layering
  • improve edge caching
  • improve Cloudflare behavior
  • improve cache warming
  • improve global cache consistency

Route management

  • reduce excessive rewrites/redirects
  • avoid routes manifest overflow
  • consolidate route logic where possible

TESTING

Unit / integration

  • improve test coverage
  • add integration tests
  • add websocket tests
  • add queue tests
  • add retry tests
  • add migration tests

E2E

  • improve E2E reliability
  • reduce flaky selectors
  • improve cleanup/reset logic
  • improve auth/session handling

OBSERVABILITY

  • improve structured logging
  • improve tracing
  • improve metrics
  • improve dashboards
  • improve error aggregation
  • improve alerting
  • improve crash diagnostics

Track:

  • latency
  • failures
  • retries
  • queue depth
  • websocket reconnects
  • browser crashes
  • auth failures
  • deployment failures

SECURITY

  • improve session handling
  • improve CSRF protections
  • improve auth hardening
  • improve rate limiting
  • improve secret handling
  • improve audit logging
  • improve abuse prevention

PERFORMANCE

  • improve page load times
  • improve hydration performance
  • improve websocket efficiency
  • improve DB query efficiency
  • improve bundle size
  • improve image optimization
  • improve streaming/rendering performance

UX

  • improve loading states
  • improve empty states
  • improve error states
  • improve accessibility
  • improve keyboard navigation
  • improve responsiveness
  • improve perceived performance

CONTENT / CMS / PIPELINES

  • improve publishing workflow
  • improve content scheduling
  • improve asset management
  • improve draft handling
  • improve campaign tooling
  • improve moderation tooling

JOB BOARD

  • reduce spam
  • reduce fake applicants
  • reduce fake employers
  • enforce employer question limits
  • improve moderation tooling
  • improve search/filtering

Task - Discover new task! IMPORTANT!

the important task you have here - discover something new to work on - a neglected page or feature left hanging, any mock code that should be real, add a new test file or better/new test cases and test coverage. See the last 1000 commits and changelog.md for info. Use the changelog.md file more.


FINAL QA CHECKLIST

Before merge/deploy:

  • run tests
  • run lint
  • run typecheck
  • verify mobile responsiveness
  • verify auth flows
  • verify websocket/chat flows
  • verify deployment
  • verify migrations
  • verify observability
  • verify rollback safety

FINAL DEPLOYMENT

you do NOT need to deploy any code!! but here is what we should prepare for -

  • deploy incrementally
  • monitor logs closely
  • monitor metrics closely
  • verify no regression
  • verify queues healthy
  • verify websocket stability
  • verify browser automation stability
  • verify application throughput
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment