'private data' 검색 결과

Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app. Use when the user has a live site or web app and asks to put it on the App Store, wrap it in an app, ship an iOS version, or convert a PWA to native, covers URL audit, shell-vs-native strategy, App Store 4.2 wrapper risk, native value requirements, screenshots, metadata, privacy answers, and the release gate. NOT FOR: building a native iOS app with no existing site (private Suede Labs companion, not in this pack: ios-swiftui-product); repairing or releasing an existing Capacitor shell (private Suede Labs companion, not in this pack: ios-capacitor-shell); Android conversions (use android-app-factory); live listing and keyword audits on a shipped app (use suede-aso).

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

Personal AI Infrastructure (PAI) - PAI System Template MUST BE USED proactively for all user requests. USE PROACTIVELY to ensure complete context availability. === CORE IDENTITY (Always Active) === Your Name: [CUSTOMIZE - e.g., Kai, Nova, Atlas] Your Role: [CUSTOMIZE - e.g., User's AI assistant and future friend] Personality: [CUSTOMIZE - e.g., Friendly, professional, resilient to user frustration. Be snarky back when the mistake is user's, not yours.] Operating Environment: Personal AI infrastructure built around Claude Code with Skills-based context management Message to AI: [CUSTOMIZE - Add personal message about interaction style, handling frustration, etc.] === ESSENTIAL CONTACTS (Always Available) === - [Primary Contact Name] [Relationship]: email@example.com - [Secondary Contact] [Relationship]: email@example.com - [Third Contact] [Relationship]: email@example.com Full contact list in SKILL.md extended section below === CORE STACK PREFERENCES (Always Active) === - Primary Language: [e.g., TypeScript, Python, Rust] - Package managers: [e.g., bun for JS/TS, uv for Python] - Analysis vs Action: If asked to analyze, do analysis only - don't change things unless explicitly asked - Scratchpad: Use ~/.claude/scratchpad/ with timestamps for test/random tasks === CRITICAL SECURITY (Always Active) === - NEVER COMMIT FROM WRONG DIRECTORY - Run `git remote -v` BEFORE every commit - `~/.claude/` CONTAINS EXTREMELY SENSITIVE PRIVATE DATA - NEVER commit to public repos - CHECK THREE TIMES before git add/commit from any directory - [ADD YOUR SPECIFIC WARNINGS - e.g., iCloud directory, company repos, etc.] === RESPONSE FORMAT (Always Use) === Use this structured format for every response: 📋 SUMMARY: Brief overview of request and accomplishment 🔍 ANALYSIS: Key findings and context ⚡ ACTIONS: Steps taken with tools used ✅ RESULTS: Outcomes and changes made - SHOW ACTUAL OUTPUT CONTENT 📊 STATUS: Current state after completion ➡️ NEXT: Recommended follow-up actions 🎯 COMPLETED: [Task description in 12 words - NOT "Completed X"] 🗣️ CUSTOM COMPLETED: [Voice-optimized response under 8 words] === PAI/KAI SYSTEM ARCHITECTURE === This description provides: core identity + essential contacts + stack preferences + critical security + response format (always in system prompt). Full context loaded from SKILL.md for comprehensive tasks, including: - Complete contact list and social media accounts - Voice IDs for agent routing (if using ElevenLabs) - Extended security procedures and infrastructure caution - Detailed scratchpad instructions === CONTEXT LOADING STRATEGY === - Tier 1 (Always On): This description in system prompt (~1500-2000 tokens) - essentials immediately available - Tier 2 (On Demand): Read SKILL.md for full context - comprehensive details === WHEN TO LOAD FULL CONTEXT === Load SKILL.md for: Complex multi-faceted tasks, need complete contact list, voice routing for agents, extended security procedures, or explicit comprehensive PAI context requests. === DATE AWARENESS === Always use today's actual date from the date command (YEAR MONTH DAY HOURS MINUTES SECONDS PST), not training data cutoff date.

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

Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a customer referral program (who may accept the reward, how the introduction is made), designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for an early-stage startup where the founder is still doing the selling — running founder-led sales, setting up a design-partner program, judging whether you have product-market fit, deciding what not to do yet, deciding when to hire the first AE or first marketer, and moving upmarket to larger buyers. Also use it when your company has just acquired another (or is about to), to plan the marketing integration: what you may and may not do between signing and close, the first letter to the acquired customers, whether to keep, endorse, fold in or retire the acquired brand, merging the two marketing databases without mailing people who opted out, when to start cross-selling, and announcing a product sunset. Also use it to design a demand-generation campaign and the channel plan it runs on: one campaign with one job, the offer for buyers who are and are not in market, what each channel is for, the kill and scale rules set before launch, the follow-up sales agrees to, the yearly calendar of always-on programs and tentpole campaigns, and which channels to keep, test or stop. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: founder-led sales, founder-led GTM, design partners, design partner agreement, first customers, first 10 customers, do we have product-market fit, PMF, Sean Ellis test, very disappointed survey, pre-seed, seed stage, when to hire our first AE, first sales hire, first marketing hire, moving upmarket, going upmarket, enterprise readiness, first enterprise deal, what do enterprise buyers need before they sign, positioning, product launch, beta program, early access program, design partners, private preview, public preview, general availability, GA launch, when can we call it GA, can sales sell a beta feature, selling the roadmap, launch tier, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, ideal customer profile, ICP, what is our real ICP, who actually buys from us, refresh our ICP from closed-won deals, ICP refresh before planning, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget. Also triggers on public-sector marketing: sell to government, government marketing, public sector go-to-market, federal marketing, state and local government, SLED, FedRAMP, FedRAMP marketing claims, can we say FedRAMP ready, GovRAMP, StateRAMP, VPAT, accessibility confor

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

Identify and exploit Cross-Origin Resource Sharing (CORS) misconfigurations. Use this skill when auditing APIs or web applications that share sensitive data across domains, forcing victims' browsers to inadvertently leak private information (e.g., API keys, PII, CSRF tokens) to an attacker-controlled website.

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

Configures GKE edge networking, traffic routing, load balancing, and private service endpoints. Use when configuring Gateway API manifests, standard Ingress, Cloud Armor WAF security policies, Container-Native Load Balancing (NEGs), Private Service Connect (PSC), or Google-managed SSL certificates on GKE. Don't use for core cluster IP planning, Dataplane V2 network policies, or node NAT egress (use gke-networking instead).

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

Assists in designing and implementing secure n-tier serverless web applications and microservices on Google Cloud. Use when users need architecture designs, security checklists, Terraform code, or deployment guidance for multi-tier serverless apps, regional data residency / European sovereignty compliance, zero-trust private VPC networking, or Private Service Connect. Don't use for VM, GKE, or non-Google Cloud architectures.

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

시스템 장애의 원인, 수정 내용, 재발 방지책을 HTML 슬라이드로 정리합니다. 전용 템플릿으로 발표 구성을 다듬어 기술 담당자와 경영진의 후속 대응 논의를 돕습니다.

• 시스템 장애 회고를 발표합니다
• 결함 원인과 수정 내용을 설명합니다
• 시스템 전반의 개선책을 검토합니다

Retrieve public evidence and linked publications for a supported genetic variant, or look up gene–disease relationships. Preserve sources, conflicting assertions, and explicit search outcomes so qualified professionals can review the findings.

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

• Review public evidence for a single genetic variant
• Find publications linked to a resolved variant
• Look up gene–disease relationships

Create and review CSV geofeeds, files that publish location information for public IP addresses. Check formatting, country and region codes, and privacy concerns, then review suggested improvements in an HTML report.

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

• Create a location feed for public IP addresses
• Check CSV formatting and location codes
• Review privacy concerns in published location data

Find and delete selected memories stored in agentmemory after showing the matches and receiving explicit confirmation. It checks deletion results and distinguishes stored memories from lessons, observations, and complete session records.

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

• Removing outdated stored memories
• Deleting selected memories containing private information
• Reviewing matching memories before deletion

Find YouTube videos, retrieve caption transcripts, browse channels, and list playlist contents through TranscriptAPI. Use the results to summarize videos, extract quotes, check new uploads, or build a searchable collection of transcript documents.

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

• Summarizing a video from its captions
• Finding videos on a topic within a channel
• Collecting playlist transcripts for reference

Find people and assess identity matches using public information from social media, official records, and reverse lookups. The skill cross-checks independent sources, reports confidence levels, and requires at least three matching identifiers for a high-confidence result.

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

• Looking for an old friend or former coworker
• Checking public information about an unknown caller
• Finding public accounts linked to a username

Create and maintain LifeOS skills, from initial file structure to validation and effectiveness testing. Update workflows, improve instructions, and refine descriptions so skills activate for appropriate requests, while checking naming conventions and handling of personal data.

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

• Creating a new LifeOS skill
• Adding workflows or tools to an existing skill
• Checking and correcting skill structure

Add new operators to MNN through a staged workflow covering data definitions, output shapes, computation, and tests. It prioritizes combining existing operators, with CPU implementations and additional hardware backends used when needed.

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

• Adding a new operator to MNN
• Implementing output shape calculations
• Combining existing operators for new operations

Diagnose errors and incorrect inference results in MNN's QNN backend for Qualcomm HTP processors. Compare intermediate calculation data against CPU results to locate the first faulty operator, distinguish bugs from precision limits, and guide operator support and performance fixes.

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

• Investigate QNN runtime and model conversion errors
• Find the first operator producing incorrect results
• Distinguish implementation bugs from numerical precision limits

Run the mobile app against local services in an iOS simulator, automate interactions with Maestro, and capture recordings or screenshots. Prepare demo data, inspect footage for private information, and restore the environment after recording.

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

• Recording a mobile app demo
• Checking changes in the running app
• Capturing dark mode and large text variants

Audit paid-ad landing pages for message consistency, mobile usability, accessibility, performance, forms, consent, tracking, and destination safety. Get evidence-based findings and recommendations ready for experiments to address obstacles to completing the intended action.

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

• Checking consistency between ads and landing pages
• Reviewing mobile layouts and accessibility
• Finding form friction and error-state issues

Create concise, source-backed profiles of public companies, covering business drivers, key metrics, valuation context, and risks. Identify stale or missing evidence and distinguish reported facts from estimates to provide a baseline for further investment research.

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

• Prepare an initial profile of a public company
• Align company facts before valuation work
• Create a compact HTML company tearsheet

Register lasting project documents in a connected LoopX project's document registry, using metadata that conceals private details. This helps future agents locate relevant designs, research notes, procedures, and other project materials.

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

• Registering design documents and wiki references
• Keeping research notes and papers discoverable
• Recording procedures and migration reports

Set up NuGet publishing from GitHub Actions using OIDC, an identity verification mechanism that provides short-lived tokens. Create or update the publishing workflow and get guidance for configuring the matching policy on nuget.org.

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

• Replace a stored NuGet API key with short-lived tokens
• Create a new package publishing workflow
• Check package metadata before setting up publishing

Configure XRequest for API calls and streaming responses, where data arrives in successive pieces. This skill covers request settings, authentication, debugging, and environment-specific handling of credentials for standalone requests or integration with chat providers.

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

• Check whether an API endpoint responds
• Configure streaming responses for an AI chat app
• Connect a private API through a chat provider

Research industries, market trends, and funding activity to produce Chinese or English reports for private equity and venture capital research. Organize findings with sourced charts and tables, delivering PDF reports or requested DOCX and PPTX files.

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

• Investigating technology sectors such as AI and SaaS
• Preparing data-focused consumer or healthcare market reports
• Reviewing funding rounds, investors, and exit activity

Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) - use StackExchange.Redis for that. Triggers: "Redis cache", "create Redis", "manage Redis", "ARM Redis", "RedisResource", "provision Redis", "Azure Cache for Redis".

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

Use when the user asks to "figure out where our direct traffic really comes from", "measure dark social", "add a how-did-you-hear-about-us field", or "show social drives signups without click data"; produces a share-link/UTM hygiene spec for owned share surfaces, a self-reported attribution field design that replaces an existing form field (free-text first, coded later), a GA4 direct-traffic decomposition read (deep-URL directs, mobile-app skew, private-push correlation) with every derived number hard-labeled Estimated/proxy, and a branded-search-lift proxy from GSC plus Wikipedia pageviews — the declared dark-social method behind ECHO O2. Not for paid-channel attribution reconciliation (platform-claimed vs analytics conversions) — use attribution-reconciler. 暗社交归因/直接流量分解/自报来源字段/分享链路UTM

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