BongSuCHOI
- 15 skills
- 0 followers
- 10 hours ago last updated
- ▌ Cx Unstuck · bongsuchoi bundleBreak planning, product, architecture, or implementation-strategy deadlock by identifying the load-bearing failed assumption and its cheapest discriminating experiment before producing bounded alternatives. Use when the same approach has failed repeatedly, constraints conflict, progress stalls, or the user asks for another angle. Use cx-debugging first for unresolved runtime failures; do not trigger a persona fan-out or replace evidence with brainstorming.
- ▌ Cx Slopslap · bongsuchoi bundleAudit and remove statistical AI-slop from web and product UI using a vendored taxonomy, static candidate scanner, five-area contract and optional transform corpus. Use only when the user explicitly requests de-slopping, removal of an AI-looking UI, Slopslap, or removal of statistically common AI UI patterns. Do not auto-apply for general UI improvement, spacing, grid, color, typography, or redesign requests.
- ▌ Cx Debugging · bongsuchoi bundleDiagnose runtime bugs, crashes, hangs, wrong behavior, silent failures, debugger sessions and binary behavior using scoped reproduction and evidence that distinguishes plausible causes. Do not use for routine code review, requirement clarification, planned refactoring, or an acceptance verdict; use cx-acceptance-qa for the verdict and this skill only when a failure needs cause isolation.
- ▌ Cx Interview · bongsuchoi bundleClarify materially ambiguous product, feature, workflow, or brownfield improvement requests into an approved task contract, or synthesize an already-resolved conversation into that contract without restarting discovery. Use when the user asks for an interview, requirements, a specification, help deciding what to build, asks you to grill or stress-test an idea, plan, or design, or when unresolved goals, constraints, non-goals, acceptance criteria, or product decisions would materially change the result. Do not use for a narrow already-specified edit, pure diagnosis, or a decision already settled by project rules.
- ▌ Cx Visual QA · bongsuchoi bundleVerify rendered web, mobile or terminal UI changes with current, sufficient, scope-proportional evidence. Use for screenshot or pixel comparison, reference fidelity, responsive and interaction states, design-system compliance, CJK wrapping, clipping, overflow and final visual PASS, FAIL, or NOT_PROVEN judgments.
- ▌ Cx Programming · bongsuchoi bundleApply non-obvious Python, TypeScript, Go or Rust guidance at typing, validation, async/concurrency, resource, error, FFI or toolchain boundaries. Use when language-specific failure modes matter; do not load for routine syntax or when project conventions already decide the approach.
- ▌ Cx Scope Check · bongsuchoi bundleCompare current changes and decisions with an approved task contract to detect unapproved scope, constraint, non-goal, dependency, API or schema, and acceptance-coverage drift. Use for explicit drift checks, after resume, compaction, or handoff, at major phases of long work, or when changes exceed the expected surface. Do not run on every turn or treat legitimate implementation detail as drift.
- ▌ Cx Acceptance QA · bongsuchoi bundleVerify completed or claimed work against explicit acceptance criteria using scope-proportional mechanical and observed evidence. Use for QA, release or handoff approval, task-contract verification, or whenever a behavior-bearing artifact must be proven. Do not run a second audit after equivalent evidence already proves the same claim; route rendered UI judgment to cx-visual-qa and unresolved failure diagnosis to cx-debugging.
- ▌ Cx Analyze Video · bongsuchoi bundleAnalyze public video URLs and local video files from frames plus timestamped captions or authorized transcription. Use for YouTube, Vimeo, TikTok, X, Twitch, and local .mp4, .mov, .mkv, .webm, .m4v, .avi, .flv, or .wmv when the user asks to summarize, inspect a moment, diagnose a screen recording, compare visual and spoken claims, extract a structure, or answer questions with timestamped evidence. Do not use for ordinary webpage interaction or a final rendered-product UI verdict; route those to cx-browser-automation or cx-visual-qa.
- ▌ Cx Insane Search · bongsuchoi bundleCodex-first fallback for reading blocked or degraded public web content. Use when normal web access returns 402/403, WAF or bot challenges, empty or JavaScript-only HTML, or when public content from X/Twitter, Reddit, YouTube, GitHub, Mastodon, Medium, Substack, Stack Overflow, Threads, Naver, Coupang, LinkedIn, and similar platforms needs an alternate public access path. Uses public endpoints, feeds, yt-dlp, Jina Reader, URL transforms, guarded transport, and explicit browser handoff. Do not use for ordinary web searches or permission-gated content.
- ▌ Cx Ultraresearch · bongsuchoi bundlePerform deep, source-backed research only when the user explicitly requests research, deep research, evidence-based investigation, careful comparison, or citation-heavy multi-source synthesis. Do not use for an ordinary current-fact lookup, a simple web question, or reading one accessible page.
- ▌ Cx Design Director · bongsuchoi bundleGuide broad product UI direction, redesign, design-system extraction and UX structure for web or mobile interfaces. Use when a task changes visual language, layout grammar, component patterns or an end-to-end product flow; do not use for a small style, copy or single-component edit.
- ▌ Cx Browser Automation · bongsuchoi bundleNavigate and interact with real browser pages, fill forms, inspect accessibility snapshots, capture screenshots or traces, and reproduce browser state. Use for browser interaction and evidence capture; final visual judgment belongs to cx-visual-qa.
- ▌ Cx Understand Codebase · bongsuchoi bundleAnalyze unfamiliar codebases and agent harnesses into an evidence-backed architecture knowledge graph with an optional interactive local HTML dashboard. Use for repository onboarding or handoff, studying a new codebase, tracing harness logic and architecture, mapping components and dependencies, refreshing an existing graph, asking graph-backed questions, explaining a file or function, assessing change impact, building a learning tour, extracting business domains, or opening the interactive visualization. Do not use for a narrow source lookup, runtime root-cause diagnosis, or formal acceptance; use ordinary repository search, cx-debugging, or cx-acceptance-qa instead.
- ▌ Cx Coding Agent Sessions · bongsuchoi bundleFind, inspect and summarize local coding-agent sessions across Codex, Claude, OpenCode, Senpi and supported transcript stores. Use for exact session recall, prior-work evidence, child-session discovery and transcript lookup.