메뉴
Polish one findedd.cn UI component such as BurgerCard, IngredientCard, PixelButton, FlavorTag, navigation, BurgerBuildStage, or a kitchen control. Use for tightly scoped component improvements where business logic and data models must remain unchanged.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Add, validate, or review findedd.cn burger recipes, ingredient records, ingredient IDs, filtering, kitchen selection logic, and world burger content. Use whenever work touches burger composition, ingredient data consistency, recipe generation, cultural flavor logic, or data-driven burger pages.
Design or review findedd.cn pages, components, colors, spacing, burger cards, ingredient cards, kitchen interactions, and pixel-food UI. Use whenever a request changes or evaluates the site's visual hierarchy, layout, copy presentation, interaction styling, or brand consistency.
Orchestrate findedd.cn engineering, visual, content, data, review, and tooling tasks through a scoped audit-plan-implement-verify workflow. Use for any task in the findedd-blog repository, especially requests involving pages, components, burger or ingredient data, visual QA, dependencies, deployment preparation, or PR review.
Audit, install, configure, or recommend tooling for findedd.cn while enforcing free, local, open-source, and maintainable choices. Use for dependencies, MCP servers, Storybook, BackstopJS, Lighthouse CI, component libraries, analytics, visual testing, or any external service proposal.
Verify findedd.cn interfaces after UI changes at mobile, tablet, and desktop sizes using available browser automation or inspection tools. Use after any layout, component, navigation, filter, kitchen, burger-stage, or visual interaction change, and for visual audits that must not alter business logic.
| name | pixel-ui-polisher |
| description | Polish one findedd.cn UI component such as BurgerCard, IngredientCard, PixelButton, FlavorTag, navigation, BurgerBuildStage, or a kitchen control. Use for tightly scoped component improvements where business logic and data models must remain unchanged. |
Focus on one component or one tightly related component group. Do not rewrite unrelated pages, alter data models, or introduce a dependency for styling.
npm run lint plus npm run build.