← all publishers

bumgeunsong

@bumgeunsong source repo

Report this profile Claim this profile

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

1. ▌
   Commit · bumgeunsong

   Use when creating git commits in this project
   0
   installs
2. ▌
   Run Web · bumgeunsong

   Launch recipe for the daily-writing-friends web app (apps/web — Vite + React + React Router, dev server on http://localhost:5173). Use to build and run the app locally so /run and /verify can drive the real UI. Captures the mandatory nvm node-22 PATH prefix (the default Homebrew node is broken), the dev-server command and port, backend selection (cloud vs local Supabase), and the static gate commands (type-check, tests).
   0
   installs
3. ▌
   Testing · bumgeunsong bundle

   Use when writing, adding, or modifying tests (*.test.ts, *.test.tsx, *.integration.test.tsx), adding coverage, implementing business logic, or doing TDD — unit tests for pure functions AND integration tests for components/hooks (React Query cache, MSW-mocked Supabase, React Router data-router loaders). Routes to strategy, naming, unit, integration, spec, and mutation-verification references. Does NOT cover cross-page journeys (use Playwright E2E in apps/web/tests/).
   0
   installs
4. ▌
   API Layer · bumgeunsong

   Use when creating or modifying API functions in */external/ directories or data-fetching hooks. Enforces Supabase patterns, mapping conventions, and N+1 prevention.
   0
   installs
5. ▌
   Code Style · bumgeunsong

   Use when writing or modifying any code. Enforces naming conventions, function design, and code clarity principles.
   0
   installs
6. ▌
   React Hook · bumgeunsong

   Use when passing callbacks to custom hooks, fixing react-hooks/exhaustive-deps warnings, or debugging unexpected re-renders in React components.
   0
   installs
7. ▌
   Pr Stacking · bumgeunsong bundle

   PR stacking workflow for breaking large features into smaller, dependent PRs. Use when planning multi-step features, creating dependent branches, or rebasing stacked changes.
   0
   installs
8. ▌
   Refactoring · bumgeunsong

   Use when user explicitly asks to refactor code, or when test coverage is requested for untested code with side effects. Enforces Functional Core Imperative Shell pattern extraction before any changes.
   0
   installs
9. ▌
   Type System · bumgeunsong

   Use when analyzing types, reviewing type safety, or strengthening the type system. Scans for 7 categories of type weakness and produces concrete before/after fixes.
   0
   installs
10. ▌
    Verify Browser · bumgeunsong

    Use after UI/frontend changes — layout, responsive behavior, navigation/routing, or any user-facing flow — to prove it actually works by driving a real headless browser (Playwright) against the running dev server. Asserts behavior (clicks, URL changes, visible text), measures layout (alignment via bounding boxes, overflow via scrollWidth minus clientWidth), captures console/page errors, and saves screenshots. Reach for this whenever "it type-checks and the unit tests pass" does not prove the feature renders and behaves correctly in a browser. Complements verify-runtime (which checks data-flow via dev logs).
    0
    installs
11. ▌
    Verify Runtime · bumgeunsong

    Use when modifying data-flow code (API calls, dual-write, mutations, database reads/writes) to verify runtime behavior via structured dev logs, before claiming the change works.
    0
    installs
12. ▌
    React Component · bumgeunsong

    Use when creating or modifying React components (.tsx files). Enforces component structure, import order, and hooks patterns.
    0
    installs
13. ▌
    Composable Layout · bumgeunsong

    Use when writing or modifying page-level layout markup in apps/web — max-width containers, flex rows, vertical spacing — or composing multiple sections on a page. Enforces shared/ui layout primitives (ReadingColumn, Stack, Row) and compound-component slots over scattered Tailwind classes.
    0
    installs
14. ▌
    Sentry Web Vitals · bumgeunsong bundle

    Fetch and compare per-route p75 Web Vitals (LCP/FCP/CLS) from Sentry Discover for the daily-writing-friends production project, with an F2-weighted score and pre/post-deploy diff. Use when the user wants to verify whether performance improved or regressed after a deploy, compare pre/post-merge windows for a PR, identify the worst-performing routes for the next perf push, or sanity-check a Web Vitals claim. Triggers - "web vital 확인해줘", "p75 비교", "회귀 있나", "perf 점수", "이 PR 머지 후 LCP 어떻게 됐어", "sentry에서 가져와".
    0
    installs
15. ▌
    Fetching Pr Comments · bumgeunsong

    Use when needing to check PR review comments on current branch, before addressing reviewer feedback, or when asked to fetch/review PR comments
    0
    installs
16. ▌
    Improving Web Vitals · bumgeunsong

    Use when the user wants to improve daily-writing-friends production Web Vital scores (LCP/FCP/CLS) by running additional iterations of the local perf harness to drive the overall F2 score higher. Triggers - "web vital 개선", "LCP 줄여", "F2 점수 올려", "harness 한 번 더 돌려", "perf 개선 작업", "perf iteration", "drive score up".
    0
    installs
17. ▌
    Daily Writing Friends Design · bumgeunsong

    Design system for Daily Writing Friends app. MUST use when doing ANY UI work including components, pages, buttons, forms, styling, Tailwind CSS, dark mode, theming, layouts, cards, inputs, or visual changes. Ensures consistent design tokens, button hierarchy, and accessibility.
    0
    installs