Structural code intelligence for AI coding agents. Use this skill when the user wants to understand how a codebase is organized (modules, call graphs, file dependencies), find where to start reading, trace the impact of a change, find code by meaning, or understand what a symbol does in its full context. Do NOT use…
Use when the user wants to prepare project-specific context engineering documents, AI coding agent instruction files, project starter Markdown files, vibe coding guardrails, PRD/TDD/architecture/security/testing docs, AGENTS.md/CLAUDE.md/Cursor/Windsurf/Continue/Copilot context files, or a complete AI-coding-ready…
Review database migrations and schema changes for safety — reversibility, lock duration, online-vs-offline behavior, batch-size on backfills, tenant isolation, RLS policies (Supabase), idempotence, audit-log impact. Use this skill on any PR that touches migrations/, supabase/migrations/, .sql, schema files…
Drive a reviewed spec to evidence-backed, integrated closure — grill the spec at intake until it is fully understood, decompose it into owned work items, build each against targeted criteria, gate every merge per item, maintain a criterion-to-evidence ledger, and close only when an integrated done gate passes. Use…
Operate the Atelier software factory (the ADW engine stamped into this repo's adws/). Use when the user says /atelier, wants to create / run / update an ADW or workflow, manage the agent roster in sssf.config.yaml, keep the engine current, or observe running agent workflows. Keywords - atelier, software factory, ADW…
Author, review, and improve Botpipe workflows. Use when Codex is asked to create packaged or workspace-local Botpipe workflows, convert codebases into workflows, design provider-heavy producer/verifier steps, write Botpipe prompts/contracts, inspect Botpipe traces, or apply Codex CLI/gpt-5.5 workflow patterns.
Use when a coding task needs an objective-first long-running loop with fresh-context work and review phases, explicit acceptance criteria, resumable state, and real blocked handling.
Sync and backup Antigravity IDE sessions, transcripts, SQLite database metadata, and brain artifacts locally into a structured workspace directory (.gemini-local/) with a rich interactive viewer.html page. Use this skill whenever the user mentions backups, workspace syncing, fswatch real-time mirroring, viewing…
Handles git branches, commits, and pull requests for VichuFlow following Conventional Commits v1.0.0. Use this skill whenever the user asks to commit, create a commit, stage changes, create a PR, open a pull request, push changes, or create a branch — e.g. "/commit", "commit this", "make a PR", "push my changes"…
Compress project context into HANDOFF.md with workflow state, analysis checkpoint, next gate, verification, current hypothesis, freshness anchors, optional gotcha references, and a resume packet for the next agent session.
Marketing workflow for Lorekeeper — README copy, manifesto, positioning, and multi-agent A/B testing of copy variations. Load this when working on any user-facing content: README, docs/manifesto.md, positioning, comparison tables, or launch copy.
Systematic debugging — a four-phase root-cause methodology, boundary instrumentation for multi-component systems, the 3-fix escalation rule, and a verification gate to run before claiming anything is fixed. Use on any test failure, production bug, build failure, performance regression, or integration glitch, and…
A workflow for analyzing an existing codebase and producing a documented picture of how it currently works. It extracts facts about APIs, data models, dependencies, configuration, tests, and project structure, then creates planning inputs.
Use during /research (or any recipe) to send 1-3 research queries in parallel — vault or web targets — and aggregate compressed findings. Routes each query to vault-researcher or web-researcher based on target. Hosts the cross-verify consent gate so any inline-research caller (/research, /design, /decompose) inherits…
Apply the relevant Dwi lenses together when several observed workflow problems co-occur. Select only the lenses the task needs, preserve a silent fast path for clear reversible work, and keep authority and evidence explicit. Prefer a focused module when one issue dominates.
Route software-engineering tasks to the smallest useful workflow. Trigger for ambiguous, multi-module, risky, performance-sensitive, AI/ML, or infrastructure work; skip for trivial edits.
Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows…
Use when working with team tasks in the Vikunja tracker via the "tracker" MCP tools (nexttask/claim/advance/...) — queue discipline, stage gates, when to callhuman vs returntask.
Use when designing, writing, or running Nido-backed VM tests, disposable production-like QA environments, template-accelerated test labs, or isolated multi-agent AI sandboxes. Provides workflows for Nido CLI spawn/provision/upload/test/delete automation, port forwarding, templates, cleanup hygiene, and VM isolation…
Use when the answer needs verified evidence across multiple sources - deep research, literature review, paper review, GitHub/project due diligence, claim verification, fact-checking, current or version-sensitive information, counterevidence search, cited reports, or checking local files against the web. Do not use for…
Use when the user wants to capture or defer something for later without acting on it now — add it to the backlog, park it, shelve it, queue it, track it, "we'll do this later", "not now but don't forget", a tech-debt entry, or moving an audit finding to the backlog. Fires on "add to the backlog", "add to the backlog…
A reference guide for writing and editing skills, which are instruction packages that tell a coding agent how to handle particular tasks. It focuses on making those instructions predictable and easy to follow.
★not rated 2 13d agoA55 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: