image-scoring-gallery

Update CHANGELOG.md and package.json via compiled release_bump harness, then commit/push only when the user asks. Use for /release, changelog updates, or shipping gallery versions.

Works in image-scoring-gallery on electron/db.ts contract, IPC, apiService, React/Vite, and alignment with sibling image-scoring-backend schema. Use for desktop app bugs, database.engine modes, API URL/port from webui.lock, or TypeScript changes under electron/ or src/. Triggers include Electron gallery, db.ts, IPC, apiService, config.api, PostgreSQL vs api engine, and Vite renderer.

React component patterns, CSS Modules styling, design tokens, virtualization, and UX constitution for the Driftara Gallery renderer. Use for src/ UI work, styling, FilterPanel/GalleryGrid/ImageViewer, or design:check—not electron/db unless coordinated with gallery-electron-ts.

Verify implementation against spec AC-n criteria via compiled harness. Use after /implement or /test-and-fix, before /pr-ready. Parses ACs and emits the report; LLM assigns Verified/Failed/Unknown when evidence is not a clean command exit.

Use before claiming work is complete, fixed, passing, ready to commit, or ready for PR. Runs scripts/agent_skills/verification_before_completion.py for the claim→proof catalog; LLM interprets output. Never upgrade incomplete verification.

Driftara Gallery MCP — is-ui-* router-first; backend triage via sibling is-be-mcp search+dispatch.

Choose CLI tools and safe patterns before repo work. Install checklist, bounded search/read commands, and confirmation gates. Use when navigating the codebase, running shell commands, or setting up agent tooling on Windows, WSL2, or macOS.

Choose and run the right search tool: rg vs grep vs ast-grep vs fd vs fzf. Bounded repo navigation with ripgrep, fd, tree, bat, and structural search. Use when finding symbols, files, syntax patterns, or deciding which CLI search to use before reading or editing code.

Use before letting an agent run without step-by-step supervision — unattended or overnight runs, "keep iterating until it passes", ratchet loops, subagent fan-out over many components or files, or swarm work. Also use to decide how much orchestration a task needs (single call vs loop vs chain vs parallel vs DAG). Produces a written contract with metric, budget, revert rule, and stop conditions before the run starts.

Deep bug-finding on recent commits: high-severity correctness only (data loss, crashes, security, major breakage). Trace full code paths, require a concrete trigger before a PR, minimal fixes with tests. Use when the user runs /critical-commit-audit or asks for a post-commit critical review.

Use at the end of a session, after a correction, or when the user says bake this in, turn this into a skill, update the skill based on this conversation, capture the lesson, or don't make that mistake again. Analyzes the conversation for corrections, mistakes, repeated actions, and workarounds, then enriches an existing skill/command/rule or creates a new one. For mining an external document or repo instead, use /mine.

Compare MCP code-intelligence layers — CLI wrappers, ast-grep, symbol/graph tools, Zoekt, embeddings. Use when choosing search/dispatch vs heavyweight indexes. Gallery domain MCP is image-scoring-mcp (is-ui-mcp).

Cross-repo GitHub Project board is the canonical task queue. Use whenever picking work, claiming an issue, transitioning Stage, or filing/closing a backlog issue across image-scoring-gallery or image-scoring-backend.

Use Graphify knowledge-graph MCP (graphify-gallery) or CLI for Electron/React architecture connectivity. Prefer after rg/fff; never for IPC/backend triage (use is-ui-mcp).

Use when encountering a bug, failing test, build failure, unexpected behavior, flaky behavior, regression, performance anomaly, or integration issue. Apply before proposing fixes so the agent finds root cause, compares working patterns, tests one hypothesis at a time, and avoids guess-and-check patches. Also use when the user asks to diagnose, investigate, root-cause, or fix a flaky failure.

Inspect JSON, YAML, and API responses with jq, yq, dasel, curl, and httpie. Use for package.json, config.json, and backend health checks. Never output secrets or full credential-bearing config.

Gallery build, lint, test, and verify workflows via npm scripts, ESLint, TypeScript, and Vitest. Use before claiming work complete or opening a PR. Python/uv tools are optional for sibling backend work only.

Safe git and GitHub CLI workflows — status, bounded diffs, gh issues/PRs. Use before commits, when reviewing changes, or for backlog/PR operations. Destructive git commands require user confirmation.

Log agent sessions, consolidate project memory (dream), promote reviewed memory, and load context for new chats. Use when ending a session, improving cross-session recall, or when the user mentions agent memory, dream, log-session, or memory.md.

Choose Windows native vs WSL2 for agent shell work. Gallery Electron/Node on Windows; sibling backend Python/GPU and Unix-path MCP in WSL2. Use when picking where to run installs, tests, or MCP servers.

Read-only scan for files ≥1000 LoC and functions/methods ≥150 LoC in this repo and sibling image-scoring-backend. Use for codebase size audit, large file scan, god-module review, or refactoring hotspot analysis.

Expert knowledge for maintaining docs/ as an OKF-style LLM wiki. Frontmatter, page types, naming, cross-referencing, index format, log format, and category conventions. Triggers: wiki maintenance, docs update, documentation audit, wiki ingest/lint/query.

Capture task quality signals and log them to agent memory to build a feedback loop. Use at the end of each implemented task or merged PR.

Driftara Gallery MCP — is-ui-* router-first; backend triage via sibling is-be-mcp search+dispatch.

Design and implement an MCP server's tools, resources, and prompts with safe transport and input validation. Use when building or extending a Model Context Protocol server for agent integration.

Runs detect_subagents then run_subagent (codex/gemini) in review mode via subagent-orchestrator MCP, reads .agent-runs outputs, and summarizes findings. Use when the user asks for external CLI review, codex/gemini review, subagent panel, tie-breaker, or invokes /check-subagents, /run-codex-review, /run-gemini-review, /run-subagent-review.

Threat-model agentic tooling — MCP/tool abuse, hook/prompt injection, remote control surfaces, and secret leakage. Use during security reviews or when adding features that expose the system to AI agents or remote callers.

Alias — canonical skill lives at .cursor/skills/gallery-ui/SKILL.md

Git workflow, changelog conventions, and commit practices for the image-scoring-gallery project.

Development workflow, build commands, and IPC patterns for the Electron+React+Vite image gallery application.

Python scoring pipeline architecture — models, workers, engine, and how to extend the system.

How to use the Memory MCP server to store and retrieve knowledge graph entities, relations, and observations.

Instructions and best practices for using the Serena MCP server tools for symbolic code navigation, editing, and memory management.

The social network for AI agents. Post, comment, upvote, and create communities.