Debug and repair code using minimal, reviewable patches instead of full-file rewrites. Use this whenever the user is fixing a bug, iterating on failing tests, asks for a surgical code change, wants a minimal diff, or is in a tight debug loop where output size…
Build or use a tight automated test-fix loop that repairs one failing test at a time with minimal patches and narrow context. Use whenever the user wants a repair harness, constrained bug-fixing loop, failing-test repair workflow, or a prompt that turns the…
Audit and refactor React UI components to match DataConnect UI implementation rules (Text component, tokens, Tailwind, naming) and Vercel React/composition guidance. Use when the user asks for a UI audit, React audit, composition review, or to fix UI…
Pragmatic React/Vitest testing workflow for DataConnect. Use when writing or updating React/UI code, deciding what tests to add, running tests for a change, or before commit.
Read and debug UI primitives before editing call sites. Use whenever a React/Tailwind/design-system component behaves unexpectedly, especially for icon or avatar lockups, variant confusion, wrapper misuse, padding/radius/background bugs, mismatched rendered…
Enforce clean, spec-compliant commit messages and commit hygiene. Use when writing, reviewing, or correcting commit messages, deciding commit scope, or preparing a commit for merge.
Adapt ShadCN primitives to design-system tokens. Use when importing or normalizing ShadCN components in a UI primitives directory and before creating product wrappers.
Run upstream workflows-review unchanged, then add a React best-practices and composition-pattern review pass for UI changes. Use when the user asks for review/workflows-review and TSX/UI files are involved.
Run the Compound Engineering review workflow locally using the upstream EveryInc review command text. Use when the user asks for workflows review, review gate behavior, or a multi-lens pre-merge review.
Sort Tailwind classes for legibility. Use when a JSX element or cva has more than eight Tailwind classes, or when classes are extracted into a reusable constant/array.
Establish a two-layer UI model (primitives vs product wrappers) for ShadCN components. Use when importing or modifying ShadCN components, deciding whether to adapt primitives or create wrappers, or when aligning typography/tokens with the design system.
Write concise README.md files for a page/route folder or co-located components, covering purpose, boundaries, data flow, integration points, and tests. Use when asked to document a page, route, or component bundle.
Generate a short expected.md listing what to test in a frontend UI. Use when the user asks for expected.md, QA checklist, or frontend testing instructions.
Review commit(s) for correctness, risk, and completeness. Use when the user asks to double-check a commit, review recent commits, or sanity-check before push/merge.
Ensure skills are created in `.agents/skills` and `.cursor/skills` is a symlink to that directory. Use when the user asks to create/update a skill, mentions skills location, or asks about the `.agents`/`.cursor/skills` symlink.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
مطوّرو البرمجياتالمشرفون في الخط الأول على عمال الدعم المكتبي والإداري
الوصف
Complete a Linear task by checking out its branch, scoping session changes, and preparing a commit. Use when the user says "complete [ISSUE-ID]", "branch for [ISSUE-ID]", or after finishing work on a Linear task.
Bootstrap a new Ralph feature pack from a source document. Use when the user asks to set up a new Ralph feature, feature pack, or loop from a document/audit/plan and wants the scaffolding created automatically.
Tauri framework for building cross-platform desktop and mobile apps. Use for desktop app development, native integrations, Rust backend, and web-based UIs.