القائمة
Write concise Conventional Commit messages from code changes. Use when drafting commit messages for git commits, pull request squash messages, or release-ready history.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Animation patterns for Mars Greenhouse Command Center including CSS keyframes, transitions, Framer Motion (React), and greenhouse-specific animations. Dark theme optimized. Use when adding animations, transitions, hover effects, loading spinners, skeleton loaders, page transitions, plant growth effects, sensor transitions, status indicators, or any motion/animation work.
Mock-first API pattern with centralized client for Mars Greenhouse Command Center. Shows namespaced API object, mock-to-real switching, data fetching hooks, loading/error states, and simulation polling. No auth needed (single-operator system).
Data visualization patterns using Recharts and pure CSS charts. Use when building charts, graphs, dashboards, stat cards, progress bars, or any data visualization. Also use when formatting numbers, dates, percentages, or mission-specific values for display.
Mars Greenhouse Command Center design system. Dark-only theme with warm Mars palette, cockpit-inspired UI. Reference for colors, typography, spacing, components, and layout patterns.
Form handling patterns for React apps including controlled/uncontrolled inputs, validation, common input components, file uploads, drag-and-drop, multi-step forms, and submission patterns. Use when building forms, handling user input, implementing validation, creating file upload UIs, or working with form state.
Tailwind CSS utility class reference covering layout (flexbox, grid), spacing, typography, colors, sizing, borders, shadows, positioning, responsive design, states, animations, and common component patterns. Use when writing Tailwind CSS classes, building responsive layouts, styling components with utility classes, or looking up Tailwind class names.
| name | commit-message |
| description | Write concise Conventional Commit messages from code changes. Use when drafting commit messages for git commits, pull request squash messages, or release-ready history. |
Use this format:
<type>: <subject>
Rules:
feat, fix, docs, style, refactor, test, chore, ci.<subject> with a lowercase letter.<subject> short, imperative, and specific.Type guide:
feat: add user-facing functionalityfix: correct a bug or regressiondocs: update docs onlystyle: formatting only, no behavior changerefactor: internal code improvement without behavior changetest: add or update testschore: tooling, deps, config, or maintenanceExamples:
feat: add keyboard shortcut help modalfix: handle null branch in repo pickerdocs: document local oauth setuprefactor: split markdown sanitizer into pure helpersBefore finalizing, verify:
: is lowercase.