Loading...
Loading...
Found 1,487 Skills
C/C++/CAPL best practices for automotive embedded systems. This skill should be used when writing, reviewing, or refactoring embedded C/C++ code or CAPL scripts targeting automotive ECUs, following MISRA, AUTOSAR, ISO 26262, and ISO 21434 guidelines. Triggers on tasks involving embedded firmware, CAN/CAN FD/LIN/Ethernet communication, TCP/UDP/DoIP/SOME-IP protocols, RTOS programming, safety-critical code, cybersecurity, diagnostics (UDS), CAPL test automation, or calibration toolchain integration.
Establish design review gates with criteria, checklists, and approval workflows.
Evaluates interfaces, components, screens, and flows against universal UX/UI principles (heuristics, UX laws, Gestalt, cognitive psychology, accessibility) and delivers concrete, prioritized improvements. Use whenever the user shares UI code, screenshots, components, or mockups and wants feedback — even if they don't use the words "critique" or "review". Also trigger when the user asks "what's wrong with this UI", "how can I improve this", "review my component", "does this look right", "give me feedback on this design", or shares any interface and asks for thoughts. Trigger for partial slices too (a single button, form, or card) — not only full screens.
Manage WeChat information and send messages. This function can only be activated with the MCP Server `WeChatMCP`. Please check the server status before using any tools in this MCP server
Completes verified credential programs and fetches MoCat progression status on Moca chain. Use after credential verification succeeds via the moca-credential-verifier skill.
Perform non-destructive cross-artifact consistency and quality analysis on three core documents: spec.md, plan.md, and tasks.md. Identify inconsistent, duplicate, ambiguous, and under-specified items after task generation. Trigger words include: "speckit-analyze", "speckit-analyze", "document consistency analysis", "specification analysis", "quality check", "artifact analysis", "spec analysis", "plan analysis", "task analysis"
Checks manual test scripts for harness adoption, golden files, fail-fast, config sourcing, idempotency. Use when auditing manual test quality.
Verify a spec-driven change is complete and correctly implemented. Checks task completion, implementation evidence, and spec alignment.
Verifica a Stack do Portainer. Além disso analisa parâmetros, rotas Traefik, volumes, recursos e conformidade do stack Portainer de Acordo com as Recomendações da Promovaweb.
Audit and consolidate documentation for healthcare engineering systems. Supports two modes — analyze (coverage audit — writes only .health-docs/analysis.md) and document (consolidate existing docs + fill gaps). Detects applicable regulatory regimes (HIPAA, ONC, FDA SaMD) from codebase signals, composes existing skills as subagents for deep-dimension analysis, and produces a structured handoff artifact consumed by document mode.
Review a Memory Bank with fresh-context specialists and produce a prioritized fix list.
Audits a specific component, file, or CSS against the project's extracted design soul in .marrow.md and returns a list of violations with severity and fix instructions. Use this skill when the user wants to check if something matches the design soul, review a component for soul violations, or audit existing code before shipping. Triggers on: /marrow-check, or prompts like "check this against marrow", "does this match the design soul", "audit this component", "is this on-brand", "check this file", "review this for soul violations". Requires .marrow.md to exist. If not found, instructs user to run /marrow first.