菜单
Recommande stack et architecture via questionnaire (mode from-scratch ou audit/migration). Délègue la rédaction de spec via delegate_task. Lit les préférences stack depuis le vault si disponibles.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Expert guidance for the App Intents framework on Apple platforms. Use when developers mention: (1) Siri or Shortcuts integration, (2) AppIntent, AppEntity, AppEnum, or AppShortcutsProvider, (3) Spotlight actions or indexed entities, (4) exposing app features to Apple Intelligence, (5) parameters, parameter summaries, or intent donation, (6) widget/control configuration intents. Not for widget timeline design itself (see widgetkit-live-activities skill).
Expert guidance for CloudKit sync on Apple platforms. Use when developers mention: (1) iCloud sync or cross-device sync of app data, (2) SwiftData + CloudKit or NSPersistentCloudKitContainer, (3) CKSyncEngine or custom CloudKit record sync, (4) CloudKit sharing / collaboration (CKShare), (5) CloudKit entitlements, containers, or schema deployment, (6) conflict resolution or offline-first with iCloud. Not for third-party sync backends (Firebase, Supabase) and not for app-server REST sync (see docs/api/sync.md).
Expert guidance for StoreKit 2 in-app purchases and subscriptions on Apple platforms. Use when developers mention: (1) in-app purchases, IAP, or subscriptions, (2) Product, Transaction, or currentEntitlements, (3) receipt validation or transaction verification, (4) SubscriptionStoreView / StoreView / ProductView, (5) restore purchases, offer codes, promotional offers, refunds, (6) StoreKit Testing in Xcode or sandbox testing. Not for RevenueCat or third-party billing SDKs.
Apple Human Interface Guidelines for visionOS (Apple Vision Pro). Use when designing or building spatial apps: (1) windows, volumes, and immersive spaces, (2) ornaments, glass material, and spatial layout, (3) eye/hand input, hover effects, and target sizes, (4) comfort, motion, and immersion levels, (5) porting an iOS/iPadOS app to visionOS, (6) RealityKit + SwiftUI scene composition. Companion to the ehmo *-design-guidelines skills for the other Apple platforms.
Expert guidance for WidgetKit widgets and ActivityKit Live Activities on Apple platforms. Use when developers mention: (1) home screen / lock screen / StandBy widgets, (2) Live Activities or Dynamic Island, (3) widget timelines, TimelineProvider, or reload budgets, (4) interactive widgets with App Intents buttons/toggles, (5) Control Center controls (ControlWidget), (6) updating a Live Activity via APNs push. Not for Siri/Shortcuts intents themselves (see app-intents skill).
Audit the health of your Claude Code configuration across all six layers — permissions, hooks, MCP servers, installed skills, agents, settings conflicts. Use when asked to "/health", "check my Claude Code config", "audit my setup", or before debugging unexpected behavior (silent permission denials, MCP tool not appearing, hooks not firing).
| name | engineering-advisor |
| description | Recommande stack et architecture via questionnaire (mode from-scratch ou audit/migration). Délègue la rédaction de spec via delegate_task. Lit les préférences stack depuis le vault si disponibles. |
| version | 1.0.0 |
| platforms | ["linux","macos"] |
| metadata | {"hermes":{"tags":["stack","architecture","advisor","questionnaire","spec"],"related_skills":["devils-advocate","adversarial-review","apple-dev"],"model":"deepseek-v4-full"}} |
Adaptation de tony (50) — ULK → Hermes. Carte :
docs/backlog/2026-06-28-SPEC-HERMES-ENGINEERING-ADVISOR/CARD.md(P2, GitHub #250).
Questionnaire structuré (from-scratch ou audit/migration) → recommandation stack + archi
argumentée → handoff spec. Mémoire des stacks préférées de l'utilisateur dans le vault
(engineering-preferences.md).
delegate_task(spec-draft) produit un document
de spec Markdown — éditer une note Markdown n'est pas du coding, reste DeepSeek. Aucun code
source généré ici.engineering-preferences.md (vault) — explicite, pas optionnel — pour ne pas re-poser les récurrents.from-scratch : ≤7 questions (domaine, scale, équipe, budget/hosting, timeline, intégrations, préférences tech).audit : 5 questions (stack actuelle, douleurs, objectif migration, budget refacto, contraintes).delegate_task(spec-draft) : passer décision + contexte → document de spec structuré.engineering-preferences.md (template vide au 1er run).from-scratch : ≤7 questions, chacune avec exemples de réponses.audit : couvre la douleur ET l'objectif, pas seulement le code.delegate_task spec-draft produit un document utilisable sans édition manuelle.audit sous-utilisé : pousser sur les douleurs ressenties, pas que le stack technique.