Skip to main content
Manus에서 모든 스킬 실행
원클릭으로
GitHub 저장소

OpenWeaponMountComputerFirmware

OpenWeaponMountComputerFirmware에는 eamars에서 수집한 skills 4개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.

수집된 skills
4
Stars
7
업데이트
2026-06-09
Forks
0
직업 범위
직업 카테고리 1개 · 100% 분류됨
저장소 탐색

이 저장소의 skills

development-plan
소프트웨어 개발자

Use for Kazusa development plans: creating, reviewing, approving, executing, verifying, signing off, or handing off implementation, refactor, migration, decommission, prompt/LLM, database, or high-risk change plans.

2026-06-09
lvgl-layout
소프트웨어 개발자

Understand, review, and improve LVGL UI layout in this ESP-IDF firmware. Use this skill whenever working on LVGL views, create_*_view functions, set_rotation_* handlers, tileview/menu layouts, Flex/Grid containers, LV_SIZE_CONTENT/lv_pct sizing, scroll behavior, hidden/floating layout flags, or UI overlap/responsiveness issues. Apply it proactively when the user asks to make the UI layout better, cleaner, more rotation-friendly, or easier to maintain, even if they do not explicitly mention "layout".

2026-06-09
lvgl-widget
소프트웨어 개발자

Select, implement, review, and debug LVGL 9.x widgets in this ESP-IDF firmware. Use this skill whenever writing or reviewing LVGL widget code, choosing between labels/buttons/dropdowns/sliders/arcs/bars/tables/tileviews/menus/textareas/switches/spinboxes, handling LVGL widget events or keys, managing label/static text lifetimes, styling widget parts/states, or checking widget-specific behavior. Apply it proactively for any main/*.c UI work that touches lv_*_create, lv_*_set_*, lv_obj_add_event_cb, LV_PART_*, LV_STATE_*, LV_EVENT_*, or enabled LVGL widgets, even when the user only asks for a small UI change.

2026-06-09
c-style
소프트웨어 개발자

Enforce and review this project's C/C++ coding style for ESP-IDF firmware. Use this skill whenever writing, editing, or reviewing .c, .h, .cpp, .hpp, CMakeLists, ESP-IDF component code, LVGL view code, FreeRTOS task/event code, driver wrappers, or embedded configuration code in this repository. Apply it proactively for C/C++ refactors, bug fixes, feature work, and code-review requests; do not wait for the user to ask for style explicitly.

2026-04-28