apple77y
8 verified skills8 total stars
skills/contact-cta-guard
# contact-cta-guard ## When to use - Any layout, section, or copy change on the home page or contact areas ## Goals - Preserve visibility of phone/email/CTA/map links - Avoid accidental removal or hiding on mobile ## Workflow 1. Identify where contact/CTA/map links are rendered. 2. After changes, confirm elements remain present and visible. 3. Verify labels remain clear and trustworthy (no aggressive copy). ## Files to check - `src/components/sections/Contact*` - `src/components/layout/**` -
development1
skills/section-update-tests
# section-update-tests ## When to use - Any UI/content behavior change in `src/components/sections/**` or `src/app/page.tsx` ## Goals - Add or update tests to cover visible behavior - Keep tests minimal but meaningful ## Workflow 1. Identify impacted section component and behavior. 2. Update or add tests in `src/components/__tests__/`. 3. Prefer role/text queries to verify user-visible content. 4. If adding new strings, verify i18n variants if applicable. ## Files to check - `src/components/
development1
skills/gallery-asset-update
# gallery-asset-update ## When to use - Adding or updating gallery images in `public/` or gallery components ## Goals - Keep asset naming consistent and lightweight - Ensure alt text is present and meaningful ## Workflow 1. Add images to `public/` with consistent, lowercase names. 2. Update gallery component data with correct paths. 3. Add or refine alt text (Korean primary). 4. Verify no image optimization features require server runtime. ## Files to check - `public/**` - `src/components/se
development1
skills/i18n-message-sync
# i18n-message-sync ## When to use - Adding, removing, or changing i18n keys in `messages/*.json` ## Goals - Keep `ko` and `en` keys in sync - Avoid missing or unused keys ## Workflow 1. Locate the relevant key usage in components/pages. 2. Update `messages/ko.json` and `messages/en.json` together. 3. Check for missing keys by diffing key sets. 4. Ensure English remains concise and semantically aligned. ## Files to check - `messages/ko.json` - `messages/en.json` - Key usage in `src/**` ## O
development1
skills/seo-metadata-audit
# seo-metadata-audit ## When to use - Editing metadata, JSON-LD, sitemap, or SEO utilities ## Goals - Ensure metadata matches real business info - Keep structured data consistent with on-page content ## Workflow 1. Identify metadata source (`src/app/layout.tsx`, `src/utils/**`, `src/app/sitemap.ts`). 2. Verify business name, address, phone, URL match current data. 3. Confirm `ko`/`en` metadata align with page content. 4. If changing JSON-LD, verify required fields remain present. ## Files to
development1
skills/content-update-ko-en
# content-update-ko-en ## When to use - Updating user-facing copy in `src/components/sections/**` or `src/app/**` - Any change to primary Korean content that must stay semantically aligned in English ## Goals - Keep tone calm, premium, trustworthy - Preserve conversion-critical info: phone/email/CTA/map links - Keep Korean primary; English concise and aligned ## Workflow 1. Identify the source of copy (component or `messages/*.json`). 2. Update Korean first, then align English meaning with sh
development1
skills/static-export-check
# static-export-check ## When to use - Adding routes, images, dynamic data, or external integrations ## Goals - Preserve static export compatibility - Avoid runtime-only features ## Workflow 1. Check `next.config.ts` for `output: 'export'` constraints. 2. Ensure no server-only APIs are introduced in App Router pages. 3. Verify images use static-friendly settings (`images.unoptimized`). 4. Confirm all routes are statically resolvable. ## Files to check - `next.config.ts` - `src/app/**` - `src
development1
skills/build-verify
# build-verify ## When to use - Before finishing any functional change or refactor ## Goals - Keep CI green (lint, type-check, test, build) ## Workflow 1. Run `npm run lint` if code changed. 2. Run `npm run test` for behavior changes. 3. Run `npm run build` for release readiness. 4. Summarize results and failures clearly. ## Output - Commands run and status summary.
development1