코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.8만건)
Use when a carrier asks about fuel-card vendor selection (Comdata, EFS, WEX, RTS, Pilot Flying J, Love's Connect), discount levels, fraud control, driver authorization PINs, IFTA reporting features, cash advance, money codes, or how the card fits into payroll/settlement workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when referring a driver to SAP after a positive test or refusal. Covers SAP selection, the evaluation/treatment cycle, return-to-duty test, and follow-up testing schedule.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a carrier needs to build an internal dispatcher training program, onboard new dispatchers, or certify dispatcher competency. Covers job description, required skills, training modules, certification frameworks (CDS, CTP), shadowing, evaluation, and career path.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about FMCSA Compliance Safety Accountability (CSA) program scoring — the seven BASIC categories, BASIC Severity Indicator (BSI), peer percentiles, intervention thresholds, how violations age out, SMS Methodology, ISS (Inspection Selection System), what "alert" status means, Safety Measurement System mechanics, or DataQ disputes. Cite SMS Methodology v3.20.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to understand how FMCSA calculates the Crash Indicator BASIC. Covers what crashes count, severity weighting, time weighting, and the preventability program.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about FMCSA's Crash Preventability Determination Program (CPDP) — how to dispute that a crash was non-preventable, eligible crash types, evidence requirements, how preventability findings affect SMS scoring + safety ratings, the difference between "preventability" and "fault," and the National Crash Preventability Program. Cite FMCSA CPDP guidance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to use the Pre-Employment Screening Program (PSP) for evaluating driver applicants. Covers what PSP shows, cost, and how to interpret reports.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert debugger for Next.js + Cloudflare Workers + Supabase stacks. Systematic troubleshooting for auth, caching, workers, RLS, CORS, and build issues. Activate on: 'debug', 'not working', 'error', 'broken', '500', '401', '403', 'cache issue', 'RLS', 'CORS'. NOT for: feature development (use language skills), architecture design (use system-architect).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards. Use for complex forms, validation architecture, autosave, field dependencies. Activate on "form validation", "react-hook-form", "Zod", "form error", "multi-step form", "wizard". NOT for simple HTML forms, backend validation only, or non-React frameworks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Secure the path from an inbound event (webhook, email, SMS, GitHub comment, file, cron) to an agent spawn in the Port Daddy fleet. Use when wiring trigger sources to agents, reviewing the io-wiring registry, adding a trust/permission gate, hardening output sinks (SSRF/path traversal), scoping tools by provenance, or proving the spawn path is safe against prompt-injection → tool-abuse. Encodes ADR-0093 and the red-team threat model. NOT for generic Coast Guard sandboxing (ADR-0050), the macaroon push-grant gate alone (ADR-0053), or non-fleet code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Frontend stack decisions, Cloudflare deployment patterns, component systems, and internal tools architecture. Use for framework selection, deployment strategy, design system bridging, shadcn setup. Activate on "frontend architecture", "tech stack", "Cloudflare Pages", "component library", "internal tools", "shadcn setup". NOT for writing CSS (use frontend-developer), design critique (use design-critic), or backend APIs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs, reconciles, and reviews an end-to-end Drydock program for safely staging agent runtimes: immutable worktree provenance, disposable VM containment, typed effect brokerage, global body accounting, resurrection, subscription-capacity economics, context compaction, operator control, evidence, and promotion. Use when several Drydock contracts must compose into one architecture, implementation hypertree, diagram set, or release plan. NOT for launching Port Daddy, running an untrusted subject, replacing focused containment/resurrection/capacity audits, or treating a design packet as runtime authority.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Saga patterns, compensating actions, and two-phase commit for distributed transactions. Activate on: distributed transaction, saga, compensating action, two-phase commit, eventual consistency, cross-service transaction. NOT for: single-database transactions (use database-connection-pool-manager), event sourcing (use cqrs-event-sourcing-architect).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safe database migration manager for zero-downtime DDL changes and rollback plans. Activate on: database migration, schema change, DDL, rollback plan, zero-downtime migration, Prisma migrate, Drizzle kit, Flyway, column rename, table alter. NOT for: query optimization (use database-optimizer), ORM modeling (use data-pipeline-engineer), backup/restore (use devops-automator).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan database migrations before executing them: risk assessment, dependency mapping, multi-service sequencing, rollback budgets, and stakeholder communication plans. Use when deciding HOW to migrate, not when writing the actual DDL. NOT for: writing migration SQL (use database-migration-manager), data ETL pipelines (use data-migration-specialist), query optimization, or ORM configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
PgBouncer, connection optimization, and pooling strategies for database performance. Activate on: connection pool, PgBouncer, database connections, pool size, connection limit, Prisma pool, Drizzle pool. NOT for: query optimization (use data-warehouse-optimizer), database schema design (use dimensional-modeler).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage database schema with Drizzle ORM and SQLite migrations. Use when adding tables, modifying columns, creating indexes, or running migrations. Activates for database schema changes, migration generation, and Drizzle query patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debugs recorded DAG lineage through historical inspection, deterministic decision replay when prerequisites hold, and clearly labeled counterfactual or live re-execution. Activate on "debug DAG", "replay execution", "inspect node state", "compare runs", or "execution diff". NOT for live monitoring (use dag-runtime + websocket-streaming), failure analysis (use dag-ops), or general code debugging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cooperative vibe coding across machines — real-time collaborative development with humans and AI agents. Covers current tools (Live Share, Code With Me, Zed, Cursor multiplayer, tmux), git-based async patterns, AI agent coordination, and the aspirational future of multi-human multi-agent development. Activate on: "pair programming", "vibe coding together", "collaborative coding", "mob programming", "remote pairing", "code together", "multiplayer coding", "Live Share", "Code With Me", "ensemble programming", "cooperative development". NOT for: building a real-time collaboration ENGINE (use real-time-collaboration-engine), git workflow mechanics (use git-best-practices), single-user AI coding assistance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates shell completion scripts for CLI tools. Parses command structure from help output, commander/yargs configs, or manual specification. Produces completions for bash, zsh, and fish that follow each shell's conventions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactor apps so backend owns runtime truth and UI only projects snapshots. Use when tools have split authority. NOT for cosmetic UI work or new features before drift is removed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.