'redis' 검색 결과

Manage Linear issues and projects through natural-language requests. Review priorities, create and update tickets, inspect team workloads, and organize release plans using a workflow that reads existing information before making changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritize bugs by their impact on users
• Plan issues and assignments for the next sprint
• Review workloads and redistribute assignments

Deploy n8n on a Linux server using Docker Compose and Caddy for automatic HTTPS. Choose a single instance or queue workers, configure secrets and Python task runners, and follow procedures for updates, backups, and recovery.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploy n8n on a personal VPS with HTTPS
• Set up queue workers for parallel workflow execution
• Update, back up, or restore an n8n instance

Find the relevant architectural guidance for API design, security, cloud infrastructure, message queues, and caching. This skill acts as an index to specialized references and lists principles for structuring software, distributed systems, and access controls.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding guidance for API design
• Reviewing security architecture topics
• Exploring containers, K8s, and Serverless

Build chat bots for multiple platforms using shared TypeScript logic with Chat SDK. The skill guides message handling, interactive cards, webhook connections, streamed AI replies, and adapters that connect platforms or store conversation state.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a bot for Slack and Teams
• Respond to mentions and direct messages
• Add approval buttons to message cards

Create Vally evaluation specifications for skills, custom agents, and workflow packages. Design distinct test requests, prepare fixture files, define automated checks and outcome rubrics, and size comparisons to provide meaningful evidence without favoring the skill’s wording.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create an eval.yaml for a skill or custom agent
• Define outcome-based checks and judging rubrics
• Prepare fixture files that reproduce specific failures

Update application code so a developer’s mirrord session identifier travels across service calls, queues, and storage events. Reuse existing tracing tools where possible, then report which request flows carry the identifier and where it still disappears.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Route downstream requests to the same developer session
• Preserve session identifiers across queue consumers
• Carry session context through upload events

Investigate SSRF, where supplied URLs cause unintended server requests, in previews, imports, proxies, and PDF generation. Confirm outbound connections, identify the responsible input, and establish whether internal services or sensitive responses are accessible.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing link previews and URL import features
• Assessing network access from PDF and screenshot generators
• Checking access to cloud metadata and internal APIs

Plan how to divide your advertising budget across Google and Meta channels using recent results. Compare proposed allocations, expected conversions and revenue, and the return from additional spending in each channel.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Monthly or quarterly advertising budget reviews
• Redistributing spend after a total budget change
• Allocating budget to a newly added channel

Compare Google and Meta campaign results across countries, states, cities, or postal codes. Identify weak and strong regions, then get recommendations for bid changes, separate campaigns, and budget redistribution based on meaningful performance differences.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reallocating budgets across regions
• Reviewing results after entering new markets
• Checking quarterly shifts in regional performance

Compare login approaches and authentication providers, then use implementation examples and security checklists to plan or review an app’s login flow. Covers sessions, tokens, external login providers, passkeys, and common implementation mistakes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose a login approach for a new app
• Compare NextAuth / Auth.js, Clerk, and Supabase Auth
• Review token storage and refresh behavior

Coordinate changes across multiple GitHub repositories with teams of AI agents. Align package versions, synchronize documentation, standardize project structures, and organize integration tests and pull requests for updates that affect several projects.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Aligning dependency versions across repositories
• Synchronizing shared documentation
• Standardizing repository structures and CI workflows

Research technical, market, or academic topics through multiple available AI providers working in parallel. Combine their findings into a report that preserves disagreements, identifies gaps, attributes sources, and recommends next steps with priorities.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing libraries and implementation patterns
• Researching markets and competitors
• Synthesizing literature on a topic

Research technical or business questions through multiple available AI providers, each assigned a different perspective. Combine usable results into a report covering findings, disagreements, evidence gaps, priorities, and recommended next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compare libraries and technical approaches
• Research markets and competitor strategies
• Synthesize literature from multiple perspectives

Compare technical choices through structured discussions among available AI providers. Use independent reviews or rounds of cross-critique to examine risks and trade-offs, then receive a synthesis of agreement, disagreement, recommended decisions, and concrete next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing technology options before making a decision
• Reviewing authentication code for risks
• Examining database schema design from multiple perspectives

Backend and infra for a project via Cohesivity (cohesivity.ai). Provisions Postgres, hosting and deploys, auth and social login, realtime websockets, an agent-native email inbox, object and vector storage, Redis, cron, and AI model APIs (OpenAI, Anthropic, Deepgram, Exa) through one HTTP API. Use when a valid .cohesivity file exists, a Cohesivity MCP is available, the user names Cohesivity, or the project needs a backend or any of these services and no competing provider was chosen.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Species abundance estimation using Bracken with Kraken2 output. Redistributes reads from higher taxonomic levels to species for more accurate estimates. Use when accurate species-level abundances are needed from Kraken2 classification output.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Step-by-step process for merging a previously-standalone Grails plugin repository (e.g. grails-spring-security, grails-redis) into the grails-core monorepo as one or more Gradle subprojects, wiring it into the shared build, publishing, docs, and CI the same way the existing modules are.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Migrate workloads from Heroku to AWS. Triggers on: migrate from Heroku, Heroku to AWS, move off Heroku, migrate Heroku Postgres to RDS, migrate Heroku Redis to ElastiCache, migrate Heroku Kafka to MSK, migrate dynos to Elastic Beanstalk, migrate dynos to Fargate, migrate Heroku Private Space, Heroku to ECS, leave Heroku, what-if workshop, compare migration scenarios, workshop mode. Runs a 6-phase process: discover Heroku resources live via the authenticated Heroku CLI (read-only, consent-gated) and/or from Terraform, Procfile/app.json, and billing exports, then clarify, design, estimate costs, generate artifacts, and collect feedback. Clarify must finish before Design, Estimate, or Generate. An optional post-Estimate what-if workshop reprices region/HA/compute/Graviton scenarios. Do not use for: GCP migrations (see gcp-to-aws), Azure migrations (see azure-to-aws), AWS-to-Heroku reverse migration, general AWS architecture advice without migration intent, or Heroku-to-Heroku refactoring.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Unauthorized access playbook for common exposed services. Use when Redis, Rsync, PHP-FPM, AJP/Ghostcat, Hadoop YARN, H2 Console, or similar management interfaces are exposed without authentication.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Lightweight guidance for using the Redis Rate Limit TypeScript SDK, including setup steps, basic usage, and pointers to advanced algorithm, features, pricing, and traffic‑protection docs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set up monitoring", "show me the catalog", "what can I provision", "browse providers", "add an LLM provider", "configure model provider", "add email sending", "set up search", "add a message queue", "set up object storage", "add feature flags". Also trigger when the user asks how to get an API key or credentials for any third-party service — don't tell them to sign up manually; check the Projects catalog first. Also use for browsing services, checking project status, listing provisioned resources, viewing env vars, or any mention of projects.dev or adding/provisioning/connecting a cloud service.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Backend infrastructure for a project via Cohesivity (cohesivity.ai). Provisions Postgres, Redis, object storage, vector database, hosting, auth, realtime, email inbox, and AI model APIs through one HTTP API. No account or API keys required to start. Trigger phrases: cohesivity, provision backend, need a database, need hosting, need storage, deploy backend, on-the-fly infrastructure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Backend and infra for a project via Cohesivity (cohesivity.ai). Provisions Postgres, hosting and deploys, auth and social login, realtime websockets, an agent-native email inbox, object and vector storage, Redis, cron, and AI model APIs (OpenAI, Anthropic, Deepgram, Exa) through one HTTP API. Use when a valid `.cohesivity` file exists, a Cohesivity MCP is available, the user names Cohesivity, or the project needs a backend or any of these services and no competing provider was chosen.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.