novahiz
UserAgent governance toolkit for AI coding agents. Classifies prompts, requires the right skills before file edits, and blocks unsafe changes. Runs fully local with no model calls. Ships as CLI, installer, and MCP tools.
Categories
Indexed Skills (91)
novahiz-analyse
novahiz-analyse, step 4 of the Novahiz pipeline: understand the affected code before modifying it. Five ordered phases (reconnaissance, architecture, quality, operations, synthesis), backed by the code map when one is available. Every claim cites a real file path, and what could not be determined gets stated as such. Use before touching unfamiliar code, before a refactor or a migration, or to locate a bug. Triggers on: "understand this code", "where is", "who calls", codebase map, impact analysis, root cause, entry point.
novahiz-assess-decide
novahiz-assess-decide is step 5 of the assessment roadmap: the go / no-go decision. Scored decision with rationale, terminal step of the assessment pipeline. Use after intake, research, define, and shape are complete. Triggers on: "should we build this", "go no-go", "decision", "kill this idea", "approve".
novahiz-assess-intake
novahiz-assess-intake is step 1 of the assessment roadmap: capture the idea before judging it. Read-only structured capture of a feature request, product concept, or vague idea. Use when the user presents a new idea, feature request, or product concept that needs to be captured cleanly before research or specification. Triggers on: "new idea", "capture this feature", "assess", "intake", "product concept".
novahiz-assess-research
novahiz-assess-research is step 2 of the assessment roadmap: investigate feasibility and market. Research report covering technical feasibility, competitive landscape, and whether the idea should be built. Use after intake, before defining a specification. Triggers on: "research this idea", "feasibility", "market research", "competitive landscape", "should we build this".
novahiz-audit
novahiz-audit performs the end-of-session compliance audit. Category-aware, verifiable state only, no invented compliance logs. Triggers on "audit", "verify", end of session, compliance check, what we forgot.
novahiz-browser
novahiz-browser is the global Playwright MCP skill for OpenCode. Forces the dev server to start in an external terminal before any browser interaction. Triggers on playwright, browser, localhost, server, dev server, screenshot, web page.
novahiz-clarify
novahiz-clarify, step 2 of the Novahiz pipeline: resolve ambiguities before the plan locks. Two moves run together: a sweep of ten risk families, then batches of questions laid out along the dependency frontier, each one carrying a recommended option. Use when the request is vague, underspecified, contradictory, or when several readings would produce different work. Triggers on: "clarify", ambiguous, "not sure yet", fuzzy scope, missing requirements, "two possible readings", open questions.
novahiz-code-review
novahiz-code-review is a three-layer intelligent code review: deterministic analysis, contextual review, human verdict. Triggers on reviewing PRs, analyzing code quality, assessing change risk, generating review reports.
novahiz-converge
novahiz-converge, step 6 of the Novahiz pipeline: close the gap between intent and code. Build the intent inventory (request, plan, acceptance criteria, ledger steps, project principles), read the current code state, classify each element as satisfied, partial, or unsatisfied, then add the remainders as traced steps. Add-only: rewrite nothing, delete no step, touch no code. Use at the end of an implementation, before declaring work done. Triggers on: "is it done?", verify the feature, convergence, gap analysis, "what remains", closure.
novahiz-delta-review
novahiz-delta-review analyzes only the diff since the last commit with impact analysis. Token-efficient delta review with automatic blast-radius detection. Triggers on reviewing git diffs, assessing change impact, validating code changes before merge.
novahiz-docs
novahiz-docs manages the project documentation lifecycle: init creates the structure, update keeps it current, check reports drift. Use to set up project documentation or keep existing docs in sync with the codebase. Triggers on: "init docs", "documentation structure", "sync docs", "docs drift", "project documentation".
novahiz-gate
novahiz-gate vu côté agent : pourquoi une édition est refusée, quelles skills la débloquent, comment lire le message de blocage. Implémenté dans src/gate.ts, il combine catalog/rules.json et les étapes de roadmap de type skill non optionnelles dans catalog/categories.json. Use when an edit is refused, before a significant action, or to know which skill to load. Triggers on: "le gate bloque", "missing skill", requiredSkills, enforcement, novahiz_GATE, "pourquoi mon edition est refusee".
novahiz-implement
novahiz-implement, step 5 of the Novahiz pipeline: write code in increments that leave the system usable. The cycle runs implement, test, verify, commit, then the next slice, under rules of simplicity, scope discipline, safe defaults, and reversibility. Use when writing or changing code for an approved task. Triggers on: implement, code, write the code, add the endpoint, build the component, apply the change, make the test pass.
novahiz-init
novahiz-init bootstraps Novahiz inside a project: memory skeleton, novahiz-docs/, deep read of the codebase, documentation fill-in, and a reviewed cleanup list. Use when the user says "/novahiz init", "init novahiz", "initialize novahiz in this project", "set up project docs and memory", or wants a one-shot project onboarding.
novahiz-plan
novahiz-plan, step 1 of the Novahiz pipeline: settle the direction before any code moves. Read-only work that yields a plan: what "done" means, the scope, the approach chosen, dependency order, how the work splits, the risks, and where the checkpoints sit. Use when opening a feature, a refactor, a migration, or any change that touches several files or whose approach is not obvious. Triggers on: "plan this", "how to approach", "where to start", feature, architecture, migration, refactoring, multi-file change.
novahiz-planner
novahiz-planner, the Novahiz pipeline orchestrator. CATEGORY-AWARE and BLOCKING: no non-trivial work starts without a written plan. The pipeline runs six steps in order: plan, clarification, tasks, analysis, implementation, convergence, each one behind its own skill. Use at the START of any request with 3+ steps, several files, or an unclear scope. Triggers on: multi-step tasks, feature implementation, refactoring, debugging sessions, migrations, architecture work, "plan this", "break this down", "where do I start".
novahiz-postgres
novahiz-postgres covers Postgres schema design, performance, and production operations. Load BEFORE writing or changing anything that lives in a Postgres database: tables, columns, migrations, RLS policies, indexes, triggers, database functions, and query plans. Rules are grouped into 8 categories ordered by impact.
novahiz-security
novahiz-security : audit de sécurité complet avec OWASP Top 10, CWE Top 25, patterns dangereux, injection, XSS, auth bypass. Use when reviewing code for security vulnerabilities, hardening authentication, validating input handling, or generating security reports.
novahiz-supabase
novahiz-supabase for ANY task involving Supabase. Triggers: Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues; client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging on Supabase projects.
novahiz-task
novahiz-task, step 3 of the Novahiz pipeline: cut a plan into atomic, ordered, verifiable tasks. Every task carries an objective, testable acceptance criteria, proof, dependencies, the files it owns, and a size from XS to XL. Use when a plan has to become an ordered list, or when the work spans several sessions or several agents. Triggers on: "break down", task list, todo, subtasks, acceptance criteria, prioritization, "what do I start with".
novahiz-wcag-audit
novahiz-wcag-audit runs a WCAG 2.2 Level A/AA accessibility audit across source code, live pages, and structured reports. Use when auditing web accessibility, checking WCAG compliance, fixing contrast, keyboard, ARIA, or screen-reader issues, or producing an accessibility audit report.
novahiz-web-extract
novahiz-web-extract : extraction de contenu web propre, conversion HTML en Markdown, suppression du bruit, récupération du contenu principal. Use when fetching web pages, extracting article content, converting HTML to clean markdown, or scraping structured data.
prompt-rewriter
prompt-rewriter detects the source language of every prompt (AR, FR, ES, DE, PT, EN), translates it into optimized English before classification where term maps exist (Arabic, French), and forces the reply back into the user's language. No external dependencies. Built into the plugin adapter.
adversarial-reviewer
Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
clean-code
This skill embodies the principles of "Clean Code" by Robert C. Martin (Uncle Bob). Use it to transform "code that works" into "code that is clean."
design-taste-frontend
Use when building high-agency frontend interfaces with strict design taste, calibrated color, responsive layout, and motion rules.
gate
gate is the guardian of the Novahiz system. Mandatory check before and after task execution: call novahiz_gate, resolve any FAIL, never modify code until it passes.
novahiz-assess-define
novahiz-assess-define is step 3 of the assessment roadmap: define the specification. Specification draft covering user-facing behavior, constraints, and success criteria. Use after research, before shaping the solution concept. Triggers on: "define the spec", "write a specification", "spec draft", "requirements".
novahiz-assess-shape
novahiz-assess-shape is step 4 of the assessment roadmap: shape the solution concept. Solution concept covering architecture, experience, and differentiation. Use after the specification is defined, before the go / no-go decision. Triggers on: "shape the solution", "solution concept", "how should this work", "design the approach".
novahiz-memory
novahiz-memory is the dual-write context save: the project's MEMORY.md plus an Obsidian vault page. Destination comes only from the routing table _meta/routing.md. Mandatory frontmatter, wikilinks, merge rather than duplicate. Use when a complex task ends, when the user says "update memory" or "save", or when a decision, bug root cause, or next step must survive the session. Triggers on: "memory", "MEMORY.md", obsidian, vault, save, "note that", routing.
apple-ui-audit
Audit iOS/macOS/watchOS/visionOS interfaces against Apple HIG and Liquid Glass (iOS 26): navigation hierarchy, materials, controls, accessibility settings, screenshots vs binary. Use when reviewing an Apple-platform mockup or build for HIG compliance, contrast, tap targets, reduced transparency, or App Store UI review readiness.
browser-session
Drive a persistent Microsoft Edge browser session for research and verification: navigate, snapshot, click, fill, console and network inspection, keep login state across runs. Use when automating a web page, checking a UI in the real browser, or reusing an authenticated session.
code-standards
Pragmatic engineering standards for production code: deep modules over micro-functions, review bar that improves code health, ASVS-aligned security checks, naming and error handling, test strategy. Use when writing or reviewing application code, setting a team style, or checking a PR against a shared bar. Prefer trade-offs over Clean Code dogma.
design-token-pipeline
Design token architecture and pipeline: DTCG 2025.10 format ($value/$type/aliases), base/semantic/component layers, Style Dictionary v4 builds, Figma Variables round-trip, theming and governance. Use when creating or migrating token files, CSS custom properties from a system, multi-brand themes, or design-dev handoff of color/type/spacing.
llm-threat-review
Security review for LLM and agent features: OWASP LLM Top 10 2025, MITRE ATLAS technique mapping, prompt injection and excessive agency checks, tool least privilege, output handling, logging. Use when designing or reviewing chat, RAG, or agentic code paths, before ship or during threat modeling.
novahiz-humanizer
Remove AI writing patterns from text. Rewrite AI-sounding prose so it reads like the human writer: not-X-but-Y contrasts, forced triads, em dashes, chatbot residue, inflated significance, and statistical tells. Use novahiz-humanizer on frontend design tasks (R13); it is not required by the gate outside design.
openapi-mcp-server
Ship an MCP server from an OpenAPI contract: tool granularity, JSON Schema 2020-12, streamable HTTP, OAuth, annotations, search/fetch read pair, MCP Inspector. Use when exposing a REST API to agents, generating tools from openapi.yaml, or reviewing an MCP server before production.
package-risk-audit
Dependency and supply-chain risk audit: lockfiles, typosquat and dependency confusion checks, OSV/CVE triage, license exposure, SBOM generation, update policy. Use when adding a package, reviewing package.json/pnpm-lock/Cargo.lock/go.mod, investigating a CVE, or preparing a release BOM.
secrets-hygiene
Secret hygiene for repos and environments: detection gates (pre-commit, CI, history), rotate-first incident response, secret manager patterns, env var rules, inventory and rotation policy. Use when auditing .env and git history for leaked credentials, planning a rotation, responding to a leak, or standing up scanning.
skill-authoring
Write or rewrite an agent SKILL.md: frontmatter contract, description as routing (what + when + differentiator), progressive disclosure, lean body, references and scripts layout, ship checklist. Use when creating a skill, fixing under/over-triggering, or restructuring a long SKILL.md.
skill-eval-loop
Measure whether an agent skill actually helps: prompt sets with should/should-not trigger, with/without skill runs, deterministic checks, rubric grading, CI regressions. Use when hardening a SKILL.md, deciding if a rewrite improved quality, or adding a quality gate for skills.
ui-craft-rules
Constructive frontend design rules: palette roles capped at three hues, type pairing and modular scale, grid/flex layout under stress, purposeful motion, full component states, APCA/WCAG contrast. Use when building React/Next/Tailwind screens or reviewing visual quality after ui-slop-remover has stripped tells. Pair under R13 with ui-slop-remover.
ui-slop-remover
Strip generic AI-generated visual tells from UI before ship: default purple gradients, sparkle glyphs, centered pill heroes, identical card grids, fade-up motion, shadcn/Tailwind stock chrome. Use when building or reviewing any landing page, dashboard, or frontend component, or when the layout looks machine-assembled. Apply BEFORE every UI deliverable; pair with ui-craft-rules.
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
ad-creative
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.
ads
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' 'should I run ads,' 'ABM,' 'account-based marketing,' 'B2B ads,' 'lead quality,' 'negative keywords,' 'Performance Max,' 'thought leader ads,' or 'when should I kill an ad.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see cro.
ai-seo
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'llms-full.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' 'agent-readable site,' 'agent readiness,' 'is my site agent-ready,' 'WebMCP,' 'do listicles still work for AI,' 'ChatGPT stopped citing comparison pages,' or 'AI citation format shift.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.
analytics
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.
apple-hig-expert
Audits and designs iOS/macOS/watchOS/visionOS interfaces against the Apple Human Interface Guidelines, including the Liquid Glass design language (announced WWDC25, shipped with iOS 26/macOS Tahoe, Sept 2025). Use when reviewing an Apple-platform mockup or app for HIG compliance, checking contrast or tap-target sizes, or designing native-feeling Apple UI (e.g., 'audit my iOS app against the HIG', 'is this text readable on Liquid Glass?').
cold-email
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.
competitor-profiling
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
content-strategy
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.
copy-editing
When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. For writing new copy, see copywriting.
copywriting
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.
cro
When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'form abandonment,' 'nobody's converting,' 'low conversion rate,' or 'this page needs work.' Use this even if the user just shares a URL and asks for feedback. For signup/registration flows, see signup. For post-signup activation, see onboarding. For popups/modals, see popups.
customer-research
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.
dart-add-unit-test
Write and organize unit tests for functions, methods, and classes using `package:test`. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.
dart-build-cli-app
Entrypoint structure, exit codes, cross-platform scripts. Use when building command line utilities, scripts, or applications.
dart-collect-coverage
Collect coverage using the coverage packge and create an LCOV report
dart-fix-runtime-errors
Uses get_runtime_errors and lsp to fetch an active stack trace, locate the failing line, apply a fix, and verify resolution via hot_reload.
dart-generate-test-mocks
Define and generate mock objects for external dependencies using `package:mockito` and `build_runner`. Use when unit testing classes that depend on complex external services like APIs or databases.
dart-migrate-to-checks-package
Replace the usage of `expect` and similar functions from `package:matcher` to `package:checks` equivalents.
dart-resolve-package-conflicts
Workflow for fixing package version conflicts. Use this when `pub get` fails due to incompatible package versions.
dart-run-static-analysis
Execute `dart analyze` to identify warnings and errors, and use `dart fix --apply` to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.
dart-setup-ffi-assets
Guides agents in compiling and packaging C/C++ source code into dynamic or static libraries (Code Assets) using Dart's Native Assets hook system (via hook/build.dart and hook/link.dart utilizing package:hooks and package:native_toolchain_c). Use when a user asks to: 'setup native assets', 'compile C/C++ source code', 'bundle dynamic libraries', 'build native C code', 'link native assets', 'implement build.dart or link.dart hooks', or 'integrate C/C++ interop in Dart/Flutter'. Helps agents avoid manual toolchain orchestration and configures secure hash-validated binary downloads or advanced linker tree-shaking with package:record_use mapping.
dart-use-ffigen
Guide agents to use `package:ffigen` to automatically generate FFI bindings instead of writing them manually. Use this skill when a task involves writing new FFI bindings, extending C/Objective-C/Swift integrations, or replacing hand-crafted `dart:ffi` setups.
dart-use-pattern-matching
Use switch expressions and pattern matching where appropriate
dart-use-primary-constructors
Help users write syntactically and semantically correct primary constructors in Dart, and migrate/use the new constructor syntax, empty-body semicolon syntax, in-body initializer list syntax, and abbreviated concise constructor syntax.
memory
memory is the alias for novahiz-memory, the dual-write context save into MEMORY.md and the Obsidian vault.
build-graph
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
a11y-audit
Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
anti-ai-design
Use when building any UI, landing page, dashboard, or frontend component to eliminate generic AI-generated design patterns. Detects and fixes visual tells that make sites look machine-made: purple gradients, sparkle icons, centered heroes, identical cards, fade-in-up animations. Apply BEFORE every UI deliverable.
anti-pattern-detector
Detects and prevents common performance, concurrency, caching, monitoring, infrastructure, and build anti-patterns in code. Use when reviewing code for reliability issues, debugging race conditions or deadlocks, optimizing cache strategies, auditing monitoring coverage, validating infrastructure configs, or checking build/deploy safety. Triggers on: anti-pattern, race condition, deadlock, cache stampede, retry storm, circuit breaker, log flooding, SPOF, config drift, dependency hell, docker bloat, migration safety, fire-and-forget, TOCTOU, ABA problem, thundering herd, cold start.
api-design-reviewer
Comprehensive REST API design review with automated linting, breaking-change detection, and design scorecards. Catches inconsistent conventions, missing versioning, and design smells before APIs ship. Use when reviewing a PR that adds or changes API endpoints, auditing an existing API for v2 migration, or establishing API standards for a team.
claude-history-ingest
Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions their .claude folder, Claude projects, session data, past conversation logs, local-agent-mode sessions, or audit logs.
code-reviewer
Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C#, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter. Analyzes PRs for complexity and risk, checks code quality for SOLID violations and code smells, generates review reports. Use when reviewing pull requests, analyzing code quality, identifying issues, generating review checklists.
code-understand
Build a ranked, citation-backed focus map of a codebase — the files and symbols an architecture actually hangs on — using CodeGraph when available and a dependency-free builtin (regex AST extraction + `rg` cross-file references) otherwise. Use this any time you (the coding agent) need to orient in an unfamiliar or large codebase before making a change: the user says "help me understand this codebase", "what's load-bearing here", "what would break if I change X", "who calls this", "map out this project's architecture", or you're about to touch code you haven't read yet and want to know what matters before scanning everything by hand. This is the same extractor `wiki-update` Step 3b uses internally — this skill exposes it directly so any agent session can call it on demand, not just during a wiki sync.
codex-history-ingest
Ingest Codex CLI conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Codex sessions for knowledge, import their ~/.codex folder, extract insights from previous coding sessions, or says things like "process my Codex history", "add my Codex conversations to the wiki", or "what have I discussed in Codex before". Also triggers when the user mentions .codex sessions, rollout files, session_index.jsonl, or Codex transcript logs.
copilot-history-ingest
Ingest GitHub Copilot CLI session history into an Obsidian wiki as distilled knowledge pages. Use this skill when the user wants to capture their Copilot CLI sessions into a personal wiki — extracting architecture decisions, debug notes, and patterns into searchable Obsidian pages. Triggers on phrases like "ingest my copilot sessions into obsidian", "add my copilot history to my wiki", "pull my copilot session history into the vault", "capture what I've learned from copilot into obsidian", "just the new sessions since last time", or "mine patterns across my copilot sessions". Also triggers when the user mentions session-store.db, ~/.copilot/session-state, or VS Code copilot-chat transcripts in the context of building a wiki or knowledge base. Does NOT trigger for general copilot usage questions, searching sessions, or backing up history.
cross-linker
Scan the Obsidian wiki and automatically discover missing cross-references between pages. Use this skill when the user says "link my pages", "find missing links", "cross-reference", "connect my wiki", "add wikilinks", "what pages should be linked", or after any large ingestion to ensure new pages are woven into the existing knowledge graph. Also trigger when the user mentions "orphan pages" in the context of wanting to connect them, or says things like "my wiki feels disconnected" or "pages aren't linked well". This is a write-heavy skill — it actually modifies pages to add links, unlike wiki-lint which just reports issues.
daily-update
Run the daily wiki maintenance cycle: check all source freshness, update the index, and regenerate hot.md. Use this skill when the user says "/daily-update", "run the daily update", "update everything", "morning sync", "refresh the wiki index", or when triggered by the launchd cron at 9 AM. Also use to set up or verify the cron + terminal notification infrastructure for the first time ("set up the daily cron", "install the terminal notification", "how do I get the morning reminder?").
dart-use-doc-examples
How to inject external code examples into Dartdoc using the {@example} directive, and how to filter those files using #hide, #region, and #endregion tags.
dart-write-documentation
Rules and formatting guidelines for writing Dart /// API documentation and doc comments. Use when documenting Dart code, writing doc comments for any Dart declaration (libraries, classes, methods, variables, etc.), or when instructed to follow the Effective Dart documentation guidelines.
database-designer
Use when the user asks to design database schemas, plan data migrations, optimize queries, choose between SQL and NoSQL, or model data relationships.
dependency-auditor
Audit and manage dependencies across multi-language projects. Identifies vulnerabilities, license conflicts, transitive dependency risks, and safe-upgrade paths. Use when auditing third-party packages before release, investigating a CVE, planning a major version bump, or running a license-compliance review. Examples: 'audit our npm dependencies', 'do we have GPL contamination', 'plan the upgrade to React 19'.
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
android-emulator
Verify and debug native, React Native, Expo, or Flutter apps on an Android Emulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an Android virtual device.
computer-use
OS/window-level inspection and input in visible local app windows through `orca computer`: native apps, external browser windows (Chrome, Edge, Safari), and app webviews. Not for Orca's embedded browser (use `orca-cli`) or page-only automation (use Playwright or CDP).
debug-issue
Systematically debug issues using graph-powered code navigation
defuddle
Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page. Do NOT use for URLs ending in .md — those are already markdown, use WebFetch directly.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.