Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.claude/agents/figma-to-component.md:
- Around line 1-70: The CI failure is due to Prettier formatting errors in the
Markdown file named figma-to-component (frontmatter and content). Reformat the
file with your project's Prettier configuration (run prettier --write on
.claude/agents/figma-to-component.md or use your editor's format command),
ensuring the YAML frontmatter, code blocks, and inline code are correctly
indented and wrapped; then stage and commit the reformatted file so the Prettier
check passes.

In @.github/workflows/ci.yml:
- Around line 32-50: Add a final "verdict" step that runs unconditionally (if:
always()) after the PR comment step and inspects the outcomes of the earlier
steps by their IDs (typescript, eslint, prettier, build); if any of
steps.typescript.outcome, steps.eslint.outcome, steps.prettier.outcome, or
steps.build.outcome is not "success", exit non‑zero to fail the workflow (give
the step an id like final-verdict and a clear error message). This preserves the
per-step continue-on-error behavior for comment/logging but enforces a blocking
CI failure if any check actually failed.

In `@src/components/ui/alert-dialog.tsx`:
- Around line 55-57: The conditional currently checks only for trigger !==
undefined, which still allows trigger === null to render <AlertDialogTrigger
asChild>{trigger}</AlertDialogTrigger> and cause a runtime error; update the
check to exclude null as well (e.g., use trigger != null or trigger !==
undefined && trigger !== null or Boolean(trigger)) so that AlertDialogTrigger is
only rendered when trigger is a valid non-null value, referencing the trigger
prop and AlertDialogTrigger/asChild usage.
- Around line 13-38: The component currently branches on AlertStatus across
AlertStatus, defaultTexts, and AlertDialogProps; refactor to use cva variants
and VariantProps by replacing the AlertStatus union and scattered defaultTexts
with a cva() call that defines variants (e.g., variant: { default, danger }) and
defaultVariants, update the props interface to extend VariantProps<typeof
yourCva> and React.ComponentProps<typeof AlertDialogPrimitive.Root>, and use the
generated variant classNames/props inside AlertDialogContext and the component
to derive title/description (move defaultTexts into variant defaults or a
mapping keyed by variant) so all status behavior is centralized in the cva
variants configuration.
- Around line 5-11: Replace the direct SVG imports InfoIcon and DeleteIcon with
lucide-react icon components: remove "import InfoIcon from
'@/assets/icons/info.svg'" and "import DeleteIcon from
'@/assets/icons/delete_forever.svg'" and instead import the proper lucide-react
icons (e.g., "import { Info, Trash2 } from 'lucide-react'"). Then update the JSX
usages that render <InfoIcon .../> and <DeleteIcon .../> (the instances
referenced in this file) to use <Info .../> and <Trash2 .../> (preserving
className, size, strokeWidth or other props passed through cn or Button props)
so styling and accessibility remain unchanged.

In `@src/components/ui/Button.tsx`:
- Around line 16-17: In src/components/ui/Button.tsx update the danger variant
string (the 'danger' key in the exported variants) to replace the arbitrary
class bg-[var(--state-error)] with the design-token utility class bg-state-error
so it matches other variants (e.g. bg-button-primary, bg-button-neutral) and
avoids arbitrary values; keep the rest of the class list (text-text-strong
hover/active/disabled classes) unchanged to preserve behavior.

---

Nitpick comments:
In @.claude/agents/figma-to-component.md:
- Around line 7-9: Add explicit frontend stack constraints to the
Figma-to-component agent guide: insert a short, clear statement near Step 3 that
all generated frontend code must target "React 19 + Next.js 16 (App Router) +
TypeScript" and use "Tailwind CSS v4 + class-variance-authority (cva)" for
styling, and also update the coding-guidelines section referenced by the glob
pattern "**/*.{ts,tsx}" so it explicitly requires React 19, Next.js 16 (App
Router), TypeScript, Tailwind v4 and cva; locate the Step 3 heading and the
coding-guidelines block in .claude/agents/figma-to-component.md (and the related
paragraphs around lines 33-63) and add that exact stack constraint text to
ensure consistency across generated components.

In @.github/workflows/ci.yml:
- Line 21: 현재 CI 워크플로의 pnpm 설정에서 "version: latest"로 되어 있어 재현성이 떨어집니다;
.github/workflows/ci.yml에서 "version: latest"를 특정 버전 문자열(예: amplify.yml에 사용된 동일한
pnpm 버전)으로 고정하도록 변경하고, 해당 키("version" under pnpm setup) 값을 amplify.yml의 버전과
일치시키세요.

In `@amplify.yml`:
- Line 7: Replace the unstable "corepack prepare pnpm@latest --activate"
invocation with a pinned pnpm version or rely on package.json's packageManager
field: either change the command to "corepack prepare pnpm@9.x.x --activate"
(use the exact desired semver, e.g., 9.15.0) or remove the prepare call and
ensure package.json contains "packageManager": "pnpm@9.15.0" so that "corepack
enable" will activate the correct pnpm; update the line containing corepack
prepare pnpm@latest --activate accordingly.

In `@CLAUDE.md`:
- Around line 13-18: Add a language identifier to the fenced code block that
currently contains the "src/ … lib/cn.ts" tree (the block starting with ``` and
the "src/" line) to satisfy markdownlint MD040 and enable syntax highlighting;
update the opening fence to include a language token such as ```text (or
```bash) so the block becomes ```text followed by the existing lines and the
closing ```.
- Around line 51-53: The fenced code block that currently reads ``` feat / fix /
style / refactor / ci / chore ``` should include a language identifier to
satisfy markdownlint MD040; update the block delimiter to include an explicit
language (for example change the opening fence to ```text) so the block becomes
```text … ```; locate the fenced block containing "feat / fix / style / refactor
/ ci / chore" in CLAUDE.md and add the language tag.