- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add first-fluke/oh-my-agent --skill oma-frontend -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add first-fluke/oh-my-agent --skill oma-frontend -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add first-fluke/oh-my-agent --skill oma-frontend -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add first-fluke/oh-my-agent --skill oma-frontend -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/first-fluke/oh-my-agent/tree/HEAD/.agents/skills/oma-frontendDe l'éditeur
Build, modify, and verify React/Next.js or Angular TypeScript user interfaces that follow project architecture, design-system constraints, accessibility expectations, and existing frontend conventions.
shadcn/ui — or Angular + signals + RxJS in Angular projects (resources/angular-rules.md)resources/execution-protocol.md, resources/checklist.md, and the stack references listed under Stack Reference, each loaded on its triggeroma-design review through ../oma-design/resources/product-interface-review.md. This review is advisory unless the task explicitly requires design approval.frontend.route-selection per ../_shared/runtime/route-selection.md.find_file, search_for_pattern, get_symbols_overview, and find_symbol. Native search is limited to the provider exclusions and non-code paths permitted by the project's search policy.resources/specialized-visual-implementation.md. For affected motion, touch, component feedback, or interaction performance, use ../_shared/ui-interaction-quality.md. Ordinary UI work does not preload these paths.Reads and edits frontend routes, components, styles, hooks, and tests, and possibly i18n keys; reads design tokens, i18n files, and resource references. Adds a dependency or shadcn component only when project conventions justify it. Lint, typecheck, test, and browser commands run only when the user or the active workflow requires them; builds run only on explicit user request. Backend APIs and registry tools are called only when the task requires them.
Apply framework, library, architecture, and data-model defaults only when the target project has no established choice. Scoped edits do not authorize a stack migration or unrelated infrastructure.
../../rules/frontend.md is the source for the React/Next.js core rules (component reuse, design fidelity, rendering strategy, accessibility, request proxy convention, prop drilling, auth boundary, animation library, framework version), the FSD-lite architecture, and naming. The guardrails below add what it does not state.
components/ui/* as read-only; customize through wrappers or cva composition.../../rules/frontend.md §Naming Conventions — domain + role readable from the basename alone (order-summary-card.tsx, use-order-polling.ts, cart.atoms.ts). Grab-bag names (utils.ts, helpers.ts, misc.ts) and version suffixes (*-v2, *-final) are banned.resources/angular-rules.md: standalone components + OnPush + signals-first, inject() DI, lazy routes, new control flow. Any non-trivial RxJS pipeline MUST ship with a marble test (TestScheduler from rxjs/testing) — a stream without a marble test fails review. React/Next.js-specific rules (shadcn workflow, proxy.ts, Libraries table below) do not apply in Angular projects.React/Next.js projects only — Angular projects use the Angular-native equivalents in resources/angular-rules.md (signals, typed Reactive Forms, HttpClient/httpResource, RxJS with mandatory marble tests).
components.json → style: "base-*"). Radix (radix-*) is a
reasoned fallback for existing Radix codebases only; no big-bang migration. Details in
resources/tech-stack.md §shadcn/ui Primitive Engine.npx shadcn@latest search <@registry> -q "<query>"npx shadcn@latest view <item> (registry source) or npx shadcn@latest docs <component> (docs and examples)npx shadcn@latest add <item>; preview with --dry-run or --diff before overwritingWhen a shadcn MCP server is connected, its registry search, example, and add-command tools cover the same three steps; discover the actual tool names before calling them.
generateMetadata, sitemap)useQuery hooksresources/tech-stack.md §Mutations)Usage: Prefer strict shadcn primitives (Card, Sheet, Typography, Table) over div or generic classes.
Responsiveness: Use Drawer (mobile) vs Dialog (desktop) via useResponsive.
Customization: Treat components/ui/* as read-only. Create wrappers (e.g., components/common/ProductButton.tsx) or use cva composition. Never edit components/ui/button.tsx directly.
packages/design-tokens or equivalent); never hardcode colorspackages/i18n or equivalent); never hardcode UI textes-toolkit first; if implementing custom logic, use the project or task coverage target and risk-relevant testsProject stack conventions live in dedicated files. Load a file when its trigger applies.
To extend: add resources/<name>.md and append a row above.
Stack generation spec: resources/stack-generation.md (loaded by /stack-set when it generates this skill's stack/)
../oma-design/resources/product-interface-review.md: recommended design review after substantial product-interface implementation.
Specialized visual implementation: resources/specialized-visual-implementation.md (requested CanvasUI GPU effect, Scroll World scene, or selected GSAP implementation)
Interaction quality: ../_shared/ui-interaction-quality.md (motion, feedback, touch, interruption, or performance changes)
Local code tools: ../_shared/core/code-intelligence.md (code search/navigation)
Project frontend rules: ../../rules/frontend.md (implementing or reviewing React/Next.js code: core rules, FSD-lite architecture, naming)
Execution steps (follow for the selected task): resources/execution-protocol.md
Checklist (applicable items before handoff): resources/checklist.md
Error recovery: resources/error-playbook.md
Context loading: ../_shared/core/context-loading.md
Clarification: ../_shared/core/clarification-protocol.md
Context budget: ../_shared/core/context-budget.md
Lessons learned: ../_shared/core/lessons-learned.md (matching prior failure or requested retrospective)
Observability handoff: ../oma-observability/SKILL.md §Integrations — Core Web Vitals targets and browser-to-backend trace correlation
Implement or modify web UI in React, Next.js, or Angular. Use for components, pages, styles, forms, and frontend state or data flows.
---name: oma-frontenddescription: Implement or modify web UI in React, Next.js, or Angular. Use for components, pages, styles, forms, and…---# .agents/skills/oma-frontend/SKILL.mdFAQ
Téléchargez .agents/skills/oma-frontend/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/first-fluke/oh-my-agent.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.