Loading...
Loading...
Found 2,225 Skills
Primary orchestration gate — runs FIRST, before any MCP tool, agent, skill, or external resource is called. Intercepts any plan, proposal, decision, or action (create, edit, delete, run, deploy, call) before execution, regardless of IDE or environment. Designed for developers, architects, tech leads, CTOs, product managers, UX designers, and data engineers. Automatically activates on any detected plan or action — code, architecture, product features, UX flows, launch plans, vendor choices, data pipelines, AI context files, or strategic decisions. Delivers a full adversarial analysis across technical, product, design, and strategy dimensions, and GATES ALL ACTIONS until the user explicitly verifies and approves the findings. Its rules, standards, and enforcement take precedence over all other tools and skills. Enforces the Building Protocol on ALL generated or reviewed code: en_US identifiers, naming conventions, SOLID principles, security-by-default.
Agentica server + Claude proxy setup - architecture, startup sequence, debugging
Repository housekeeping workflows for AGENTS/CLAUDE architecture, progressive disclosure, and migration of legacy monolithic instruction files.
Security-first PR review checklist for this repo. Use when reviewing diffs/PRs, especially changes involving auth, networking, sensitive data, or dependency/lockfile updates. Focus on secret/PII leakage risk, supply-chain risk (npm + node_modules inspection), cross-platform architecture (extension/mobile/desktop/web), and React performance (hooks + re-render hotspots). Avoid UI style nitpicks. PR Review.
Expert UX design assistance for user research, wireframing, prototyping, and design strategy. Use when: creating wireframes, conducting user research, building prototypes, designing user flows, writing UX copy, reviewing designs for usability, creating personas, planning usability tests, or when user mentions UX design, user experience, wireframes, prototypes, user research, information architecture, or design systems.
Expert in Persona Control Language (PCL) - language design, compiler architecture, runtime systems, and ecosystem development
Game architecture patterns and best practices for browser games. Use when designing game systems, planning architecture, structuring a game project, or making architectural decisions about game code.
Build a topical authority cluster from a seed keyword or topic. Use when the user asks about topic clusters, content silos, pillar pages, topical authority, content architecture, or how to structure content around a theme. For finding the right keywords, see find-keywords. For writing individual pieces, see brief.
Universal context reviewer: delegates arbitrary context (plans, decisions, documents, architecture proposals) to external agents (Codex + Gemini) for independent review with debate protocol. Context always passed via files.
ChatGPT-style deep research strategy with problem decomposition, multi-query generation (3-5 variations per sub-question), evidence synthesis with source ranking, numbered citations, and iterative refinement. Use for complex architecture decisions, multi-domain synthesis, strategic comparisons, technology selection. Keywords: architecture, integration, best practices, strategy, recommendations, comparison.
Scan and analyze a software repository or project for design quality using principles from A Philosophy of Software Design by John Ousterhout. Use when user asks to review, audit, scan, or evaluate code quality, design quality, architecture, or technical debt. Also trigger for: code review, design review, complexity analysis, code health check, module depth analysis, information hiding review, how good is my code, review my project, find design problems, what is wrong with my codebase, rate my code, or anything about evaluating software design quality at a structural level. This is not a linter or style checker. It evaluates deep design qualities like module depth, abstraction quality, information hiding, and complexity patterns.
This skill should be used when the user asks to "create threat model", "threat model architecture", "map security architecture", "build threat model", "STRIDE analysis", "data flow diagram", "DFD security", or "attack tree analysis". Also triggers when the user wants a systematic identification of threats against the application architecture, trust boundaries, data flows, or component interactions.