القائمة
Apply the Battle Ops tactical brand to UI work, including theme tokens, logo usage, PrimeNG styling, and microcopy.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, deploying, and managing distributed apps. USE FOR: aspire start, aspire stop, start aspire app, aspire describe, list aspire integrations, debug aspire issues, view aspire logs, add aspire resource, aspire dashboard, update aspire apphost, aspire publish, aspire deploy, aspire secrets, aspire config. DO NOT USE FOR: non-Aspire .NET apps (use dotnet CLI), container-only deployments (use docker/podman). INVOKES: Aspire CLI commands (aspire start, aspire describe, aspire otel logs, aspire docs search, aspire add, aspire publish, aspire deploy), bash. FOR SINGLE OPERATIONS: Use Aspire CLI commands directly for quick resource status or doc lookups.
Synchronize OpenSpec specs with bound GitHub issues, and enforce frequent commits while applying changes.
استنادا إلى تصنيف SOC المهني
| name | battle-ops-style |
| description | Apply the Battle Ops tactical brand to UI work, including theme tokens, logo usage, PrimeNG styling, and microcopy. |
| license | MIT |
| compatibility | Best used for Angular and PrimeNG UI changes in this repository. |
| metadata | {"author":"nikneem","version":"1.0","generatedBy":"manual"} |
Apply the Battle Ops tactical identity consistently across repository UI work.
Use this skill whenever you create or modify branded UI in this repository. It converts the approved Battle Ops brand into operational guidance for implementation work so future UI changes stay visually and verbally consistent.
src\App\public\branding\src\App\src\#05070A#0A1A2A#00E5FF#66F2FF#2C3A47#FFB300#B33A3AUse dark surfaces by default. Bright accents should feel like sonar or tactical instrumentation, not playful neon clutter.
0.5px32px20px14px12pxSupported variants:
Rules:
Supported Battle Ops-compatible settings:
Do not introduce arbitrary user theming or freeform recoloring. Preferences must stay within the Battle Ops system.
When reduced motion is enabled:
PrimeNG components should inherit Battle Ops tokens rather than looking like stock defaults.
Prefer token-driven styling and shared overrides over one-off component hacks.
Tone must be tactical, cold, precise.
Prefer phrasing such as:
SECTOR SCAN INITIATEDCONTACT DETECTEDTORPEDO IMPACT CONFIRMEDHULL INTEGRITY COMPROMISEDUNAUTHORIZED MOVEButtons and labels should feel command-oriented:
ENGAGEDEPLOY SHIPSLOCK TRAJECTORYAWAITING COORDINATESsrc\App\public\branding\