.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/aryaniyaps/ultimate-pi
home/skills/aryaniyaps/ultimate-pi
aryaniyaps avatar

aryaniyaps/ultimate-pi

60 skills

View on GitHub
$npx skills add aryaniyaps/ultimate-pi
SkillInstalls
agent-routerDynamic agent discovery, matching, and delegation. Discovers all available agents at runtime, reads their frontmatter to understand capabilities, matches tasks…—api-contract-designDesign stable contracts for modules, services, commands, events, plugins, CLIs, and public interfaces.—ast-grepStructural code search and replacement using the sg CLI. Use for function calls, imports, class/method definitions, call sites, and codemods.—broker-domainUse when implementing the Broker-Domain pattern: event-brokered integration around cohesive domain services, separating broker concerns from domain behavior,…—cccThis skill should be used when code search, file/directory summary lookup, or concept-guide lookup is needed (whether explicitly requested or as part of…—code-review-self-checkPerform a final agent self-review before reporting completion. Use after any code edit, refactor, test change, config change, or docs update.—cohesion-couplingImprove code-level modularity by increasing cohesion and reducing accidental coupling.—complexity-controlReduce accidental complexity while preserving essential behavior.—context7-cliUse the ctx7 CLI to fetch library documentation, manage AI coding skills, and configure Context7 MCP.—cqrsUse when implementing CQRS: separate command and query models, explicit write invariants, optimized read projections, consistency boundaries, projection…—debugging-disciplineDebug systematically instead of guessing. Use when fixing bugs, failing tests, flaky behavior, runtime errors, regressions, or unexpected output.—defensive-programmingAdd robustness at trust boundaries and failure-prone code paths.—dependency-managementPrevent dependency sprawl and risky coupling to third-party or shared code.—documentation-updateUpdate documentation only where it helps future work. Use when behavior, setup, contracts, commands, architecture decisions, operational procedures, or…—domain-modelingModel business rules and domain concepts clearly. Use when adding features with domain behavior, invariants, workflows, policies, state transitions, commands,…—error-handlingDesign predictable, debuggable error behavior. Use when adding or changing failure paths, retries, validation, IO, service calls, event handling, command…—event-drivenUse when implementing event-driven architecture: domain/integration events, producers, consumers, broker or mediator topology, eventual consistency,…—find-skillsgraphifyany input (code, docs, papers, images, video) → knowledge graph → clustered communities → HTML + JSON + GRAPH_REPORT.md—harness-contextCompile task-specific harness context using context-mode and graphify.—harness-debate-planPlan-phase Review Gate debate — pi-messenger threads, lane YAML, bus tools for parent orchestrator.—harness-decisionsStructured user decisions via ask_user for harness setup, planning, and governance forks.—harness-evalharness-git-commitCommit staged git changes with configurable message format and Co-authored-by trailer from .pi/auto-commit.json.—harness-governorEnforce harness governance phases, policy gates, budgets, and promotion rules.—harness-ls-lint-setupBootstrap ls-lint filename rules for harness projects — seed naming.manifest.json, generate merge-safe .ls-lint.yml, and document bootstrap vs --force sync.—harness-orchestrationOrchestrate ultimate-pi harness phases with the native `subagent` tool (isolated `pi --mode json` subprocesses).—harness-planAgent-native harness plans — lakes/context bundles, planning context, parallel_probes debate profile, plan-synthesizer on low/med risk, path-first…—harness-reviewPost-run verification gate (/harness-review): harness-verify, Sentrux fitness functions, benchmark + verdict evaluator, adversary, optional tie-breaker.—harness-sentrux-repairOSS Sentrux capture, diagnostics synthesis, and repair-plan loop for harness runs.—harness-sentrux-setupBootstrap Sentrux architectural rules for harness projects — seed architecture.manifest.json, generate merge-safe .sentrux/rules.toml, and document bootstrap…—harness-specDraft or refine harness artifact contracts under .pi/harness/specs.—harness-steerPost-review repair loop via harness-steer and executor repair mode.—hexagonal-ports-adaptersUse when implementing hexagonal architecture / ports and adapters: domain core isolated from delivery and infrastructure mechanisms, inbound and outbound…—layeredUse when designing, refactoring, or validating a codebase as layered architecture: delivery/interface, application/use-case, domain, and infrastructure/data…—legacy-code-seamsSafely change hard-to-test legacy code. Use when code has hidden side effects, weak tests, global state, large routines, unclear ownership, or risky…—lsp-navigationNavigate code with IDE features and run proactive LSP diagnostics on files/folders/batches. Use as PRIMARY for code intelligence and type/error checks.—microkernelUse when building plugin or extension architecture: a stable core kernel with explicit extension points, plugin contracts, registration, isolation, versioning,…—microservicesUse when designing, extracting, or repairing microservices: independently deployable bounded-context services with owned data, explicit contracts,…—modular-monolithUse when designing, splitting, or repairing a modular monolith: one deployable application with explicit business modules, bounded contexts, private internals,…—naming-and-intentImprove readability through precise names and explicit intent. Use when adding functions, modules, variables, commands, events, errors, tests, or docs.—orchestration-driven-soaUse when implementing orchestration-driven service-oriented architecture: central workflow orchestration across services, explicit process models,…—pipelineUse when implementing pipeline architecture: data or task processing split into ordered filters/stages with explicit inputs, outputs, composition, error…—posthog-analystAnalyze pi agentic conversations, errors, and misalignments using PostHog MCP.—privacy-data-handlingHandle personal, sensitive, or customer data safely. Use when adding storage, logs, analytics, exports, imports, integrations, telemetry, search indexes, AI…—refactoring-safe-evolutionRefactor code without changing observable behavior. Use when improving structure, extracting abstractions, simplifying code, or modernizing internals while…—requirements-to-implementationTranslate vague or high-level requests into safe implementation steps. Use before coding features, bug fixes, refactors, or ambiguous tasks.—risk-based-verificationMatch verification depth to change risk. Use after code, test, config, dependency, data, or docs changes.—routine-function-designDesign clear routines, functions, methods, or procedures. Use when adding or restructuring executable units.—security-reviewRun a lightweight security pass on code changes. Use when touching authentication, authorization, input handling, files, paths, commands, network calls,…—sentruxArchitectural quality sensor for AI-assisted code — rules, modularity, session baselines, and degradation detection via the Sentrux CLI (not MCP in Pi…—service-basedUse when implementing service-based architecture: coarse-grained domain services inside a mostly centralized system, with explicit service contracts,…—service-meshUse when applying the service mesh pattern to service architectures: move cross-cutting network concerns such as retries, mTLS, routing, observability, policy,…—small-change-disciplineKeep coding-agent edits surgical and reversible. Use when implementing any code change, bug fix, refactor, or cleanup where scope control matters.—space-basedUse when implementing space-based architecture: horizontally scalable processing units, in-memory/distributed state, partitioning, eventual persistence,…—test-strategyChoose the right test level for a code change. Use when adding features, fixing bugs, refactoring, changing contracts, or improving coverage.—tradeoff-analysisMake engineering tradeoffs explicit before choosing an implementation.—web-retrievalAgentic Web Retrieval Stack (WRS) — tiered web_search/web_fetch/web_contents (harness-web.py + Scrapling). Default tier=deep with web-query-expander angles.—wiki-autoresearchAutonomous iterative research loop. Takes a topic, runs web searches, fetches sources, synthesizes findings, and builds a queryable knowledge graph via…—wiki-save