Explore

Propose or implement behavior-preserving Rust refactors in tfmcp for confirmed coupling or duplication problems.

Turn a bug symptom into a structured, reproducible bug report — summary, environment, exact repro steps, actual vs expected, and evidence (logs, error text, failing route/test) — and then optionally scaffold a failing regression test that pins it. Use this the moment a bug, defect, crash, 500, wrong count, broken page, or "this used to work" is reported and you're about to start fixing it, even if the user just pastes an error or says "X is broken". A structured report makes a far better fix prompt than a raw symptom and becomes the regression test that stops the bug coming back. Trigger on: repro, reproduce, bug report, file a bug, "X is broken", "getting a 500", "why is this failing", regression test for a bug, write up this bug.

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"

Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"

Launch and watch Guaardvark's Swarm Orchestrator: parallel coding agents, each in its own git worktree, working a markdown plan and merging back deterministically. Use when the user wants several agents on one codebase at once, says "swarm this", or asks about a running swarm, worktrees, or merge status.

Connect this agent to a running Guaardvark (self-hosted AI studio) and check what it can do right now. Use first when the user mentions Guaardvark, asks to generate images/video/music/voice locally, run a Film Crew, train a LoRA, launch a swarm, or when a guaardvark MCP tool is missing or a call fails with "not reachable" / "plugin offline".

Code intelligence over repositories Guaardvark has indexed: semantic code search, exact-text search, file listing, PageRank repository map, import dependency graph, reading one class or function, analysis and generated rewrites, plus the System Mapper and self-improvement status. Use when the user asks where something is implemented, how modules depend on each other, or wants an architecture map of an indexed repo.

Security-role assignment, user access, application users, business units, and admin self-elevation in Dataverse environments. Use when the user wants to give someone access, grant a role, become an admin, or add a service principal.

One-step setup and connection diagnostics for a Dataverse environment — installs tools, authenticates, registers MCP, writes `.env`, and verifies active profiles and linked ERP endpoints. Use when starting a new project, switching environments, fixing authentication, troubleshooting MCP, or checking existing Dataverse / Finance and Operations connectivity or linkage.

Environment-level Dataverse administration — bulk delete, retention/archival, organization settings, OrgDB settings, recycle bin, audit, and the 37 allowlisted PPAC toggles. Use when the user wants to clean up data at scale, configure audit, change environment settings, manage retention policies, or list/cancel ERP batch jobs.

Semantic file discovery via `vexor`. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.

Quarterly maintenance pass (every 1-3 months) — dependency/security audit, build health, and repo hygiene for PerformanceMonitor and PerformanceStudio

Use this skill when users want to add, customize, or troubleshoot UI Beats components in React/Next.js projects. It covers component selection, shadcn registry installation from uibeats.com, the UI Beats MCP server, motion and reduced-motion handling, and integration patterns for animated sections.

Generate optimized project context from codebase scan. Trigger: new project, no CLAUDE.md, /ijfw-summarize

Use when the user says: 'ijfw status', 'show me the system state', 'what is ijfw doing', or to see the at-a-glance routing / memory / activity banner.

One-line code review comments. Trigger: review, code review, PR review, /ijfw-review

Diagnose IJFW integration health per platform. Trigger: 'doctor', 'check setup', /doctor

Use when about to claim completion: 'done', 'fix complete', 'tests pass', 'build succeeded', 'shipped', 'no regressions', 'ready to merge', 'ready to ship'. Iron Law gate requiring fresh verification evidence in the same message as the claim; wires into runtime (verification-gate.js + the ijfw_state MCP tool subagent.post-done verb).

Check for and apply IJFW updates safely. Trigger: 'update ijfw', 'upgrade', 'latest version', 'is there a new version', /update

Surface relevant project memory at session start or on demand. Trigger: session start, 'recall', 'remember', 'what do you know', 'context', /recall

Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'.

Donahoe Loop audit gate before execution. Trigger: 'audit plan', 'check plan', 'review plan', 'plan audit', 'plan check', 'before we build', 'before execution', 'validate the plan', 'is this plan solid', 'plan review'. Owns pre-execution audit intent -- fires before any foreign plan-checker.

Internal session metrics tracking. Auto-triggered at session boundaries. Tracks tokens, agent usage, efficiency gains. View with /ijfw-status.

Audit and clean project memory files. Trigger: 'memory audit', 'clean memory', 'memory health', /memory-audit

Session handoff generation and loading. Trigger: session end, context full, /handoff

Root-cause analysis with hypothesis tracking. Trigger: 'debug', 'broken', 'not working', 'fix this bug', /debug

Control the IJFW observation dashboard (start/stop/status). Trigger: 'ijfw dashboard', 'open dashboard', 'show observations', 'dashboard start', 'dashboard stop', 'dashboard status', 'view session activity'.

Generate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact. Trigger: 'cross audit', 'Trident', 'second opinion', 'check with other models', 'check with other AIs', 'cross-check this', 'get another perspective', /cross-audit

Challenge decisions, surface counter-arguments, flag assumptions. Trigger: 'should I', 'is this right', 'critique', 'poke holes', 'second opinion', 'devil's advocate'. Auto-fired by ijfw-intent-router.

IJFW efficiency layer -- smart output, routing, context discipline. Always active. Trigger: any IJFW interaction. Disable: 'ijfw off' or 'normal'.

Compress memory/context files into terse form. Trigger: /compress, compress file

Terse conventional commits. Trigger: commit, git commit, /ijfw-commit

Session-end auto-extraction of lessons, errors, fixes, and user feedback into structured memory. Fires at session end. Requires consent on first run.

Generate Razorpay MCP server tool implementations from API documentation URLs, curl commands, or request/response examples. Produces Go tool code, unit tests, registration, and README updates. Use when the user provides a Razorpay API doc link, curl example, or request/response payload and wants a new MCP tool created.

Expert email management assistant for Apple Mail. Use this when the user mentions inbox management, email organization, email triage, inbox zero, organizing emails, managing mail folders, email productivity, checking emails, or email workflow optimization. Provides intelligent workflows and best practices for efficient email handling.

Use this skill for ANY task on a Synology NAS via the mcp-server-synology MCP — managing files and folders on the NAS, searching NAS shares, reading or creating NAS files, running Download Station tasks (torrents, magnets, downloads), checking NAS health (disks, SMART, volumes, RAID, SHR, UPS, CPU/memory utilization), managing Container Manager containers/projects/images/registries/networks, creating shared folders, configuring NFS exports, and managing NAS users, groups, or share permissions. Triggers on "synology", "NAS", "DSM", "DiskStation", "DS220+/DS920+/etc", "Download Station", "Container Manager", "Docker", "container", "/volume1", and any NAS-share path. Use even when the user just says "my NAS" or names a model number without saying "Synology". Distinct from the lifehacker-cert skill, which only handles SSL certs on one specific NAS — this skill is for general NAS operation.

Free AI-first short-form video publishing to TikTok, Instagram Reels, YouTube Shorts, X, and Facebook from AI agents through Taisly.

Úsalo cuando haya que responder a un cliente molesto o redactar una respuesta de soporte.

Úsalo cuando el usuario pida revisar código Delphi o Pascal en busca de errores.

Úsalo cuando el usuario pida redactar una factura, una cuenta de cobro o una nota de cobro.

Creating and refining Mermaid diagrams with live reload. Use when users want flowcharts, sequence diagrams, class diagrams, ER diagrams, state diagrams, or any other Mermaid visualization. Provides best practices for syntax, styling, and the iterative workflow using mermaid_preview and mermaid_save tools.

Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.

Make images, textures, illustrations and background video for a website or app you are building, with Glif, and wire them into the code. Use when: "add a hero image", "this page needs visuals", "replace these stock photos", "placeholder images", "background texture", "seamless pattern", "paper grain", "section backgrounds", "feature illustrations", "SVG illustration", "empty state art", "404 illustration", "infographic", "blog cover", "OG image", "social share image", "product cutouts for the shop", "looping background video", "scroll animation video", or when a page you're building has empty image slots. NOT for: editing an existing image (use edit-images), images not tied to a site (use make-images), logos or icons (use app-icons-and-logos), store or launch graphics (use app-promo-materials), demo videos (use app-demo-videos), game art (use game-assets).

Make new still images from a brief with Glif and save them to a folder: concept art, a series of variations, mockups, posters, illustrations, wallpapers, reference boards or any picture that isn't tied to a web page, app store or game engine. Use when: "make an image of", "generate a picture", "draw me", "I need some concept art", "make 10 variations", "one in each of these styles", "mockup of", "poster for", "wallpaper", "fake screenshot of", "what would X look like as Y", "mood board images", "images for my deck or doc". NOT for: editing an existing image (use edit-images), images that go into a site you're building (use web-visuals), logos or icons (use app-icons-and-logos), store or ad graphics (use app-promo-materials), game art (use game-assets), video or audio (use audio-and-video).

Help someone start with Glif. Explain how it connects, check the connection and credits for free, and suggest what to make first. Use when the user asks what Glif is, how to set it up, whether it's connected, which account is connected, how many credits they have, or what Glif can do. Never starts generation.

Make art and media for a game you are building with Glif: character reference sheets, consistent characters, pixel-art sprite sheets with animation cycles, seamless and PBR textures, 3D models, item and ability icons, and trailers. Saves files where the engine expects them. Use when: "character sheet", "let's create a character sheet", "same character in every scene", "sprite sheet", "run cycle", "pixel art character", "tileset", "seamless texture for my game", "PBR materials", "3D model for Unity/Godot/three.js", "ability icons", "game trailer", "I need a cool logo for my game". NOT for: the game's logo or app icon (use app-icons-and-logos), music and sound effects (use audio-and-video), store graphics (use app-promo-materials).

Edit an existing image with Glif: remove the background, erase or replace objects, expand the canvas, restore or upscale, retouch, restyle or change one detail. Saves the result next to the original without overwriting it. Use when: "remove the background", "make this a transparent PNG", "cut out the product", "erase X from this photo", "replace the sky", "expand this image to landscape", "make it 16:9 without cropping", "upscale this", "restore this old photo", "retouch this portrait", "restyle this as pixel art", "edit this image", "keep everything else identical". NOT for: new images from scratch (use make-images), animating an image (use audio-and-video), logos (use app-icons-and-logos).

Find the user's saved Glif project, show its media, and add new work to it without starting a separate project. Use when: "show my recent Glif projects", "open my last image", "keep going on that one", "make 5 variations to A/B test", "same but vertical", "make a version for TikTok", "resize it to every format", "same character in a new scene", "fix only the text", "fix scene 3", "next episode", "do another one like yesterday's".

Make or edit audio and video with Glif, from a text brief or from a reference image, video or audio file. Use when: "make music", "add fitting music to my video", "jingle", "voiceover", "narrate this", "text to speech", "sound effect", "UI sounds", "ambient loop", "make a video", "video clip", "UGC video", "talking avatar", "lipsync", "dub this into Spanish", "GIF", "add captions", "trim or combine these clips", "split the vocals", "remove background noise", "animate this photo", "turn this product photo into a video ad", "make this photo dance", "bullet time", "one continuous shot around this", "make a music video for my song", "drive this character with my video", "show this room renovated", "use this video's structure for my product". NOT for: editing a still image (use edit-images), demo videos of an app (use app-demo-videos), new still images (use make-images).

Plan and make launch, store, ad and campaign graphics with Glif: real app screens turned into store listings and launch posts, or a coordinated set of product photos, ads, a short video and a jingle for any product. Use when: "App Store screenshots", "Play Store feature graphic", "launch graphics", "Product Hunt images", "social posts for the launch", "carousel", "promo banner", "static ad", "Meta ads", "ad creatives", "ad concepts", "angles to test", "UGC-style ads", "turn these reviews into ads", "product photos for my shop", "Amazon or Shopify listing images", "lifestyle shots of this product", "social media calendar", "a week of posts", "launch campaign", "poster series", "mood board", "storyboard this ad", "resize this ad for every format", "headline variations", "YouTube thumbnail", "X header", "email header". NOT for: logos and icons (use app-icons-and-logos), images inside the site or OG images (use web-visuals), demo videos (use app-demo-videos), one-off edits (use edit-images).

Design a logo, app icon, favicon set, icon set or brand kit with Glif for an app or site you are building, then export every size and wire it into the code. Use when: "help me design a logo", "make a logo", "design an app icon", "we need a favicon", "PWA icon", "iOS app icon", "Android adaptive icon", "SVG logo", "custom icon set", "illustrated icons for these features", "emoji or sticker pack", "Discord emoji", "mascot", "animate our logo", "logo intro", "make the logo glossy 3D", "brand kit", "visual identity", "brand guidelines", "make it look like our site". NOT for: page images or textures (use web-visuals), editing an existing image (use edit-images), store or launch graphics (use app-promo-materials), game characters (use game-assets).

Use when Codex needs to create, edit, inspect, validate, or demo UE5.8 UMG interfaces through Unreal Motion Graphics MCP/FabUmgMcp, especially target/default workflows, widget tree authoring, HLSL-backed UI materials, Sequencer widget animations, Blueprint event wiring, readback validation, or operation-trace demo scripts.

Use when Codex needs to create, inspect, edit, delete, or validate UE5.8 material assets through Unreal Motion Graphics MCP/FabUmgMcp HLSL material tools, especially one-HLSL Custom-node authoring, UI-default versus non-UI material type selection, union-only writes, semantic outputs, hlsl_delete recovery, or Material ToolMode protocol work.