Managing third-party dependencies — version pinning, security auditing, license compliance, update workflows, lockfile management, supply chain security. Activate on "npm audit", "dependabot", "renovate", "pin versions", "dependency update", "supply chain", "license compliance", "lockfile", "security advisory", "typosquatting", "SBOM". NOT for internal monorepo package management (use monorepo-management) or publishing your own packages to npm/PyPI.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Aesthetic assessment and design scoring across 6 dimensions. Use for UI critique, design review, visual quality assessment, remix suggestions. Activate on "design critique", "aesthetic review", "UI assessment", "visual quality", "design score", "remix this design". NOT for implementation (use frontend-developer), accessibility-only audits (use color-contrast-auditor), or brand identity creation.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Expert in drone systems, computer vision, and autonomous navigation. Specializes in flight control, SLAM, object detection, sensor fusion, and path planning. Activate on "drone", "UAV", "SLAM", "visual odometry", "PID control", "MAVLink", "Pixhawk", "path planning", "A*", "RRT", "EKF", "sensor fusion", "optical flow", "ByteTrack". NOT for domain-specific inspection tasks like fire detection, roof damage assessment, or thermal analysis (use drone-inspection-specialist), GPU shader optimization (use metal-shader-expert), or general image classification without drone context (use clip-aware-embeddings).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
dbt Core/Cloud data transformations, testing, documentation, and CI/CD. Activate on: dbt, data transformation, analytics engineering, ref, source, staging model, mart, dbt test. NOT for: orchestration/scheduling (use airflow-dag-orchestrator), data warehouse tuning (use data-warehouse-optimizer).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Long-running design anthropologist that builds comprehensive visual databases from 500-1000 real-world examples, extracting color palettes, typography patterns, layout systems, and interaction design across any domain (portfolios, e-commerce, SaaS, adult content, technical showcases). This skill should be used when users need exhaustive design research, pattern recognition across large example sets, or systematic visual analysis for competitive positioning.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Apply recognition-primed decision making to agents operating under time pressure, uncertainty, and ambiguous cues. Use for situation assessment, RPD-style action selection, and decision-support design in operational settings. NOT for batch optimization, static planning with full information, or tasks where exhaustive search is cheap and harmless.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Multi-stage Docker build optimizer for minimal, secure production images. Activate on: Dockerfile optimization, multi-stage build, distroless image, container size reduction, Docker security scanning, BuildKit features. NOT for: container orchestration (use kubernetes-manifest-generator), CI/CD pipelines (use github-actions-pipeline-builder), runtime container config (use environment-config-manager).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Cloudflare Pages and Workers deployment checklist for wrangler deploys, secret audits, D1 migrations, Worker-compatible SDK checks, and browser-auth verification. Use when shipping Cloudflare changes to production. NOT for general CI/CD architecture, non-Cloudflare deployments, or post-launch UX QA.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Validates versioned permission requests against a grant scope and records comparison evidence. Activate on 'validate permissions', 'permission check', 'inheritance validation', 'permission matrix', 'security validation'. NOT for runtime enforcement (use dag-scope-enforcer) or isolation management (use dag-isolation-manager).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Matches natural language task descriptions to appropriate skills using semantic similarity. Handles fuzzy matching, intent extraction, and capability alignment. Activate on 'find skill', 'match task', 'semantic search', 'skill lookup', 'what skill for'. NOT for ranking matches (use dag-capability-ranker) or skill catalog (use dag-skill-registry).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Review of Cognitive Systems Engineering applications and current practice in safety-critical domains
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Operations, debugging, and optimization for DAG workflows. Performs root cause analysis on failures, profiles execution performance, aggregates results from parallel branches, bridges context between nodes, and learns patterns from execution history. Activate on "DAG failed", "why did it fail", "root cause", "performance profile", "aggregate results", "merge branches", "execution patterns", "optimize DAG". NOT for planning DAGs (use dag-planner), executing DAGs (use dag-runtime), or validating outputs (use dag-quality).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Use when applying Cloudflare D1 migrations, fighting Supabase migration history vs SQL execution, choosing direct psql over CLI, designing idempotent migrations, debugging schema drift between local and remote, or recovering after a half-applied migration. Triggers: supabase migration repair instructions appearing, table missing after "applied" status, "Tenant or user not found" when running psql, --remote vs --local D1 confusion, NOT NULL on a populated column, foreign key constraint failures, drift between staging and prod schemas. NOT for Mongo/document migrations, ORM-managed migrations specifically (Prisma/Drizzle have their own conventions), or pure data backfills.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Designs or reviews provenance-bound DAG attempt traces, coverage gaps, cancellation, and unknown-effect reconciliation. NOT for claiming execution completeness, deployment monitoring, or root-cause proof.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Records and evaluates event-specific probability forecasts for agent outputs. NOT for validation or automatic acceptance.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Generates comprehensive, context-aware code review checklists tailored to the specific codebase, programming language, and team standards. Analyzes PR diffs and suggests what reviewers should focus on.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Systematic framework for resurrecting and modernizing legacy codebases through archaeology, resurrection, and rejuvenation phases. Activate on "legacy code", "inherited codebase", "no documentation", "technical debt", "resurrect", "modernize". NOT for greenfield projects or well-documented active codebases.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations. Use when users need competitive analysis, market positioning strategy, differentiation tactics, or "how do I stand out?" guidance across any domain (portfolios, products, services). NOT for market size estimation or financial forecasting.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Apply Conway's homomorphism principle to multi-agent system design, recognizing that agent coordination structure predetermines system architecture and capability.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Epistemic logic for multi-agent perceptual systems — Kripke models, vision sets, public announcement as coordination primitive, and satisfiability-as-reconfiguration applied to agents with limited observability. From Charrier, Ouchet, Schwarzentruber's "Big Brother Logic" demonstration paper (ENS Rennes / IRISA).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Marketing and promotion specialist for Claude ecosystem technology - MCP servers, skills, plugins, and agents. Expert in community engagement, registry submissions, content marketing, and developer relations. Activate on 'promote MCP', 'share skill', 'market plugin', 'launch agent', 'developer marketing', 'MCP registry'. NOT for creating MCPs/skills (use agent-creator), general marketing (use content-marketer), or SEO optimization (use seo-visibility-expert).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Runs an iterative, conversational product-discovery process with a founder/stakeholder: structured interview, live low-fi wireframing, a linked feature/page node-graph built up as you go, a founder-confirmed lock-in checkpoint, then a generated PRD, a Mermaid-rendered sitemap, and a mockup with a full design system (palette, typography, dark mode). Use when building or operating an AI product-discovery chatbot, or when running founder/stakeholder discovery by hand and you need the structure (interview script, node-graph schema, PRD template, design-system handoff order). NOT for implementing the spec'd product once locked — hand off to feature-specific skills (ideal-web-app-builder, tailwind-v4-expert, color-theory-palette-harmony-expert, typography-expert, dark-mode-design-expert) for that. NOT for one-shot PRD generation without an interview loop — if the founder already has a written spec, this process is unnecessary overhead.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book. NOT for server-side rate limiting, bulkhead isolation, backpressure protocols, or database-specific retry.
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新
Use when designing a background-job system, choosing between BullMQ / Sidekiq / RQ / Temporal / SQS, deciding queue-vs-workflow, sizing concurrency vs rate limits, building dead-letter queues, or making handlers idempotent. Triggers: jobs running twice on retry, lost jobs after worker crash, DLQ filling up, Redis OOM from job backlog, exactly-once requested, "do we need Temporal?", visibility timeout / lockDuration confusion, exponential backoff vs jitter, fan-out fan-in workflows. NOT for outbound webhook publishing (different concerns), receiver-side webhook handling (different concerns), event-streaming/Kafka topology, or in-process async (event loop only).
日本語の概要は準備中です。原文の説明を表示しています。
curiositech/port-daddy☆ 22026年10月12日 更新